Loading...
Full access to the visual canvas, the AI assistant, and a development endpoint for seven days. You also get a pool of AI credits, enough to draft real rules and see how the assistant handles them before you commit.
No. Start the trial with an email address and build something real. We only ask for payment details when you choose a plan.
Your workflows stay exactly as you left them. Endpoints stop serving until you pick a plan, and once you do, everything is back the way it was.
A workflow rule is one published decision: a single rule tree with its own endpoint. Versions, branches, and expressions inside that tree do not count separately.
Nothing breaks. Existing workflows keep running, and we will ask you to move up a plan before you add another user or rule.
Yes. Change plans at any time and the difference is prorated. Cancel whenever you like and access continues to the end of the billing period.
One credit covers one assistant request, whether that is drafting an expression, explaining it, or suggesting outputs. Editing logic by hand never uses credits.
When you need more users or rules than the Scale plan allows, or when you have particular requirements around onboarding, support, or how the platform fits your infrastructure. Get in touch and we will build the plan around it.
No. You build rules by arranging conditions and branches on a canvas, and the AI assistant writes the underlying expressions from a plain English description. The expression editor is there when you want finer control, but you can ignore it.
Deployed workflows are called over HTTPS. Send your data as JSON, and the response contains the outcome the rule tree reached.
They are separate addresses backed by separate deployments. Development is where you try things out. Production serves your live traffic and only changes when you deliberately deploy to it.
No. Tagging locks a version so it cannot be edited. If you need changes, branch a new version off it and the original stays exactly as it was.
Deploy an earlier tagged version to production. Traffic follows immediately, and nothing about the newer version is lost.
Admins manage members and roles and deploy to production. Editors build and test workflows. Viewers can read any workflow without changing it.
Yes. Workflows can be exported, which is useful for backups or for moving a rule between environments.
In a database dedicated to your organization, never pooled with another customer. Sensitive data is encrypted at rest.