One platform for your cases, priced by what it uses

No. Anyone who takes part in your case through a role does so free, without a platform of their own. If a partner wants to manage its side, it can request a free organisation platform.

Every organisation with its own place makes the network more useful for the next one. It runs no caseflows of its own, so it costs us little. It still has limits, so one platform cannot slow down the rest.

Running work never stops because of a plan limit. A case that is under way continues, whatever the meter says. When you reach a limit, we contact you to move to a larger plan; nothing is switched off. Development rounds above the limit wait for the next month or a larger plan. Cases never wait.

This is a promise about your plan, not about uptime: outages and security incidents are handled by support. Above Enterprise, we agree a Custom plan with you.

They are your work, not our cost. A busy month is a good month, and whether one process becomes two should be a design choice, not a price question. Your employees and the people outside your organisation who take part in a case never count, so you never design anyone out of your process.

A developer is someone who asks the code assistant to build. Every change they ask for is a development round, and rounds are where building capacity and review go. Someone who only works in cases costs us nothing extra.

One change you ask the code assistant to build, ready for you to try out in your development environment. For example: “add a step where the manager approves orders above €5,000”, “add a field for the customer’s VAT number”, or “the reminder goes out a day too early”. If you then ask to adjust that change, that is a new round.

Twenty rounds a month is about five changes a week, enough to keep improving one process steadily. Above the limit, new changes wait for the next month or a larger plan; nothing that runs stops. A round runs on your own AI key, but every round takes building capacity and review on our side, which is why it counts. Tasks the assistant carries out in production are counted separately.

It only works on data, never on how your process is built: a task a person may do there themselves, carried out on their behalf and with their rights. If they may not do it, the assistant refuses. Changes to the process itself are always built in development first. It is part of Standard and Enterprise.

Agents that hold a role in your cases are something else: they run on your AI key in every plan, and they do not count.

You do, directly. Your platform runs on your own AI key, so your provider bills you and our price does not move with theirs.

Running your platform costs us little, and the AI runs on your key, so there is no hourly limit. If one platform's use starts to slow down others, we contact you first and look at it together.

Coming You will be able to clean up your development environment, so test cases stop counting. The audit trail in production stays, because that is what it is for.

Yes. Your specifications are open files you can read and take without CaseFlows, and on request we hand over your cases and data in an open format. See our manifesto for where we stand on each of these.

A specification that several organisations maintain together, as a commons, can run at cost or free. Talk to us about it.