Frequently asked questions

When a new sign-up enters onboarding, the first decision is prepared from the policy you provide. The dashboard offers an AI-built decision flow, a hand-built decision flow, or a rule set. Its AI Decision Assistant then asks, “What do you want to decide?” and accepts a description, a document with your business rules, or both.

For an instant decision, onboarding produces a decision flow, test data and an endpoint. It also produces the endpoint binding, release and deployment. When the policy describes work people do, the build produces a case design, case board and execution node, followed by a release and deployment.

On each decision flow, the AI Assistant sits beside a live preview, and the same assistant is available in the case studio. You describe the change you want; it shows a plan for that change, then you approve or skip each proposed part before generation and application. The preview marks additions in green, modifications in orange and removals in red, so you decide what enters the design before anything is saved.

In Data destinations, the decision can write its execution records to a PostgreSQL database. You can paste a connection string such as postgresql://user:password@host:port/dbname and select Parse, or enter the host, port, database, username, password and SSL mode separately. Test connection checks the setup before the database becomes the destination for the records you choose to keep.

The decision archive is written after the response is sent. If that write fails, it is queued and retried, so the decision itself does not fail because the archive write failed. Case data stays in your database, and Decisimo creates its own tables for these records; your existing tables remain unchanged.

You can connect a data source to a public REST API or SOAP service that returns JSON or XML, so a decision flow or case task can use information held outside your system. Supported authentication includes HTTP Basic and OAuth2, and the source has a 15-second timeout. You can configure the source from its own screen or ask the AI Assistant to configure the connection.

The assistant can configure REST, SOAP or webhook connections and check the method, authentication and credentials. You enter credentials into a credential box; they go to the vault, and the chat carries only a reference. If you paste a credential into the chat by mistake, it is redacted before it reaches the AI.

Analysis draws on the Decision archive in your database; questions about outcomes also use Outcome history. Once those records exist, you can run a release over recorded production decisions to see which decisions would change beside what actually happened.

From there you go from backtest to mining to a proposed new revision. That proposal queues its own backtest, so you see how the new revision would have decided the same recorded decisions before you release it.

No, the building of decision flows is done online within a browser, so no additional software is required. For execution, the endpoint needs to be integrated with the core system that sends data for evaluation. This integration can be done using a simple REST API, and our team can assist with the setup process. Once integrated, Decisimo can execute the decision flows and decision logic built by the user in real-time.

As a SaaS (Software as a Service) provider, Decisimo offers continuous upgrades and updates to our users at no additional charge. Our pricing is based on usage, so you will only pay for the services you use, not for any upgrades or updates.

A decision is one execution of a decision flow through an endpoint. That is the only thing we meter. Whether the flow calls three external data sources or thirty, evaluates five rules or five hundred, scores two models or none, it counts once.

Everything else is unlimited on paid plans: rules, decision flows, AI models, API endpoints, environments, versions and users. Adding an analyst to your team never changes your bill. Versioning, role-based access control and full export of your decision logic are included on every plan - they are not an upsell.

Yes. You can sign up and build your use case without a credit card. The trial gives you a working environment to validate your decision logic before you commit.

No. Users, roles and seats are unlimited on every paid plan. Our pricing is based on decisions executed in production, so your whole risk team can build and review decision logic.

Classic is monthly. Enterprise is an annual agreement billed quarterly. We are open to discussing terms that fit your budgeting cycle.

When you need something shared infrastructure cannot give you: dedicated endpoints, data residency in a specific region, private or on-prem deployment, an SLA in the contract, an ISO 27001 evidence pack for your security review, or a negotiated DPA. If none of those apply, Classic is the right plan.

No. Execution runs on zero data retention: the data passes through to make the decision and is not kept here. We retain the execution logic with its revision history, and the platform audit log of actions taken in the portal - not your customer data. Execution traces are written to infrastructure you control, and decision results can stream continuously into a Postgres database you own.

No. Your data is not used to train models, ours or anyone else’s.

Yes. Execution endpoints are regional and you choose the region. If that is not enough, an execution node can run inside your own environment on request.

No. SSO, two-factor authentication and IP restrictions are on every plan. Charging extra for the controls that keep an account safe is a practice we would rather not copy.

Access is role-based, and every view is written to the audit log with actor, IP and correlation id. That log is available to you, so the question is answerable with evidence.

Your decision results are already in your own database if you configured the sink, and your decision logic exports as a Markdown file. There is no extraction project to negotiate at the point you have decided to leave.