Decisions review

Decisions is a business process automation and orchestration platform: a coordination layer for workflows, systems, business rules, people and AI. It is designed to sit around existing core technology, handling routine work and complex processes that cross systems rather than replacing those systems.

Its unified control plane covers long-running processes, business logic and governed AI. Visual tools support the design and management of first- and third-party agents, while a rules engine handles decision logic. Process intelligence is intended to make operations and AI-driven outcomes more visible. The vendor also describes enterprise integrations and support for modern and legacy environments.

The product is not presented as a standalone library, CLI or self-hosted server. Its public materials do not establish whether deployments are hosted, self-managed or both, so confirm the architecture, runtime and network requirements with Decisions before designing an integration. Think of it as an orchestration platform to evaluate alongside the applications and systems it will coordinate.

The vendor describes visual tools for building agent actions and business rules, plus process automation across systems through enterprise integrations. It also presents Decisions as an option for adding workflow capability to an existing .NET application; a customer quote calls the platform approachable for .NET developers. That is not the same as a documented .NET SDK or a guarantee about the integration method.

The homepage links to product documentation, but does not name an API style, SDK, language support beyond that customer reference, CLI, webhook protocol or integration catalog. If your codebase needs a REST API, webhooks, plugins or a specific SDK, confirm support and versioning in the vendor's docs before committing. Ask for a concrete example of authentication, deployment, error handling and how an application passes data into a process. The visual design model may suit teams that want business-owned rules; teams expecting a code-first workflow library should verify how much logic can be maintained and tested in code.

The pricing page lists no free plan or free trial. Foundation / Mid-Market (Standard) starts at $4,000 per month, billed annually, and includes unlimited users, unlimited processes, 1,000 cases per month and two environments: Development and Production. That gives a published usage boundary, but the vendor does not publish the cost of exceeding 1,000 cases.

Growth and Enterprise require custom quotes. Their usage limits are not published, and the vendor says platform pricing does not charge per user. Monthly billing prices are not listed. AI workflow builder, business rules automation, Intelligent Document Processing and process mining are mentioned as additional plans or options, but their prices are not published. The practical cost model therefore depends on case volume, environment needs and which optional capabilities a production deployment requires. Get written prices for overages and add-ons, and clarify whether your process volume is counted as cases, executions or another unit, before estimating annual spend.

The vendor does not publish an open-source license or describe Decisions as an open-source project. Its public materials also do not establish whether self-hosting is available, or explain data export and migration procedures. Do not assume that a visual process definition or ruleset can be moved to another platform without conversion work.

Before adoption, ask Decisions about deployment options, ownership and export formats for process definitions, business rules, case data and AI-agent configurations. Confirm what happens to data when a contract ends, whether exported artifacts remain usable, and whether your team can keep integrations working without the platform. Lock-in risk is likely to depend on how much operational logic, state and system coordination you place in Decisions; get an exit plan in writing before migrating business-critical processes.

Foundation’s listed allowance of 1,000 cases per month is the clearest published production limit. The vendor does not publish overage costs, and Growth and Enterprise usage limits are not stated, so teams with variable or seasonal volume should get thresholds and billing behavior in writing. Foundation includes Development and Production environments; confirm how additional environments are priced if your release process needs them.

The platform is positioned for long-running, cross-system processes and governed AI, but the public product information does not establish availability targets, rate limits, recovery objectives or scaling guarantees. Before relying on it for high-stakes operations, ask for service-level commitments, backup and restore procedures, incident escalation terms and capacity guidance. Also review security and compliance documentation for your data types, agent permissions and audit requirements. Validate how failures, retries, version changes and manual exceptions are handled across connected systems; those are the points where orchestration decisions affect production behavior.