Most teams start with a pilot and move to a retainer once it is running. You can start with either.
We embed with your engineers and put one real process into production. You keep the code, the diagrams, and the working knowledge.
A standing agreement for priority access to the maintainers, plus a reserved block of engineering time each month.
Book a free consultation. We will look at the process with you and say which shape fits.
We pick one process that matters and is small enough to finish. Then we build it with your team, in your environment, on your infrastructure.
We scope one process end to end and fix the price. If it is bigger than it looked, we say so before starting.
Your analysts and ours model the process in BPMN. They learn the notation on their own work, not on an example.
We wire the diagram to your services, databases, and identity provider. It runs where your other systems run.
We document what we built and walk your engineers through it. The repository stays with your team.
A retainer is a fixed monthly fee for a reserved block of engineering time from core contributors to our software stack.
One person on the core team who knows your processes, your integrations, and how you deploy.
Your questions skip the queue and go to the engineers who maintain the code.
Bugs you hit get fixed in SpiffWorkflow itself and released to everyone, not patched in a private fork.
We test each upgrade against your processes and plan the move before you run it.
Regular sessions on scaling, modeling patterns, and process design as your usage grows.
Hours you do not spend on support go to new work: connectors, features, migrations, whatever ranks highest.
We have done this before and we know where the semantics differ.
Running the SpiffWorkflow Python library inside your own application, with your own interface on top.
Wiring the engine to the systems you already run, from internal APIs to the vendor software you cannot replace.
Kubernetes, high-throughput configuration, and the operational work of running the engine in production.
Modeling patterns that survive contact with production, and a second opinion on the ones you have already built.
BPMN and SpiffWorks taught to your analysts and engineers, on your processes rather than on demo data.
We measure an engagement by what your team can do without us. Stop paying us and the workflows keep running, because the engine is open source and your code is already in your hands.
We spend a call or two scoping one process and learning about your existing systems, then create a fix-price proposal before we sign the consulting agreement.
We do not replace anyone. A pilot where your engineers never touch the code is a pilot that dies the day we leave.
No. The engine is open source under the LGPL and we support self-hosted deployments. The Visual Design Studio and Analytics need a subscription.
You run it. Some teams take it from there, others move to a retainer so they can reach us when something changes.
Yes. We work behind firewalls, in air-gapped environments, and under your security review. Tell us the constraints in the first call.
It depends on the block of time you reserve. We quote one monthly figure and it holds for the term.
We will tell you whether a pilot is the right shape for it, and what it would take.