Local
The light npx runtime or the full Docker container, on your own machine. Your laptop, your disk — the fastest way to build, demo, and evaluate a workflow app.
✓ Available today — Run it locally →
Open architecture · Your infrastructure
Deploy anywhere. Own everything.
One engine, run where you need it — on a laptop, in your own cloud account, or fully air-gapped inside your network. Your data never has to leave your control. Nothing calls home, and nothing locks you in.
One engine, your choice of where it runs
FastYoke is a single Rust engine with one wire contract. The same schemas, the same SDK, and the same finite-state-machine core run in every deployment mode — so where your data lives is a deployment decision, not a rewrite.
There is no proprietary cloud dependency to opt into and no lock-in to design around: the interfaces are standard REST and WebSocket, the workflow rules are portable JSON, and the core primitives are open source. Move an app from a laptop to an air-gapped server and it runs unchanged.
The spectrum
Four ways to run it — you own three of them today
Pick the deployment that matches your compliance posture. Local, self-hosted in your own cloud, and fully air-gapped are available today; turnkey AWS and GCP provisioning is on the roadmap.
Self-hosted cloud
The FastYoke container on a VM in your own cloud account — AWS, GCP, Azure, or anywhere you run Linux. Your account, your keys, your network.
✓ Available today — Self-hosting guide →
Air-gapped on-prem
A single self-contained binary inside your network with zero outbound traffic. Tenant databases never leave your hardware — you can cut the network cable after deployment.
✓ Available today — See On-Prem →
Native AWS & GCP
Turnkey provisioning for the major clouds — cloud-marketplace listings, Terraform and Helm, and a managed control plane — so a first-class cloud deployment is one step, not a manual setup.
◷ On the roadmap — Tell us your target →
Prefer not to self-host at all? FastYoke Managed Cloud → runs the full engine for you, multi-tenant and hosted.
Why it's open
No lock-in, by construction
Openness here is not a slogan — it is four concrete properties of the architecture.
Your data, your files
Each tenant is a discrete database file, never commingled in a shared multi-tenant table. In a self-hosted or air-gapped deployment, that data sits on your hardware and never leaves your network.
One wire contract
Every mode speaks the same REST and WebSocket API and shares the FSM engine, schemas, and SDK. An app moves between local, self-hosted, and air-gapped unchanged — leaving is never a migration project.
Open-source core
The engine is built on public Rust crates — the guard evaluator, the tenant-scoping layer, the hardened SQLite pool, and more. The core is inspectable, not a black box you take on faith.
Self-contained binary
No sidecar services, no phone-home, no outbound calls required to run. Air-gap compatibility is a property of the binary itself, not a hardened configuration you assemble.
Compliance & sovereignty
Deployment is a compliance control
For regulated teams, where the software runs is part of the audit, not a footnote. Air-gapped and self-hosted deployments keep data pinned to a specific jurisdiction and inside your own boundary — data residency and sovereignty become facts about your infrastructure rather than contractual promises about someone else's.
The full set of regulated-sector profiles — healthcare, financial services, critical infrastructure, and international data-localisation — lives on the On-Prem page, alongside our security and trust posture.
What's next
Native AWS & GCP
Today you can already run FastYoke on a VM in your own AWS or GCP account. What's on the roadmap is making that turnkey: cloud-marketplace listings, Terraform and Helm modules, and a managed control plane, so a production-grade cloud deployment is a single step rather than a manual setup.
We prioritise this work around the clouds our enterprise customers ask for first. If you have a target in mind, tell us — it helps us sequence.
Run it where you need it
Start locally in seconds, self-host in your own cloud, or deploy fully air-gapped — the same engine, wherever your compliance posture points.