01 · Build
Model in the browser
A BPMN modeler lives in your workspace. Draft with autosave, validate as you draw, and freeze numbered versions with notes — plus an audit trail of who changed what.
Sheptra Cloud · beta not open yet Complex processes.
Complex processes.
Calm execution.
Sheptra Cloud is the end-to-end platform for your process definitions — model BPMN in the browser, ship immutable versions with one click, and run them on Greyson, a fast .NET engine we operate for you. Your workers stay in your services. Every instance stays on the record: where it is, and how it got there.
Beta not open yetComing soon
order-fulfillment.bpmn v14
4 instances active
Before the beta
The engine runs real BPMN today, and the platform around it is still being built. We'll open the beta once it's ready. Until then, this page is an account of where things stand — what works now, and what's still ahead.
One platform
From first sketch to millionth instance
Everything your process definitions need lives in one cloud workspace — no modeler licenses, no engine clusters, no glue code between them.
02 · Deploy
Ship an immutable version
One click from the modeler, or one call from your pipeline, snapshots a version and hands it to the engine. Versions are immutable, and restoring an older one is a click.
03 · Run
Let the cloud take it
The managed engine executes every instance with nothing to provision — durable jobs with retries and leases, timers, and live token positions you can watch.
The Greyson engine
A fast BPMN engine for .NET, run for you
At the heart of Sheptra is Greyson — lightweight, efficient execution of BPMN process models, on infrastructure we operate. There is exactly one version in production, and it is always the current one.
Fast
A lightweight core that executes BPMN models with almost no overhead — 1,035 process instances a second in our load harness, engine and database on one host. Measured, not modelled, and an upper bound rather than a deployment promise.
Your workers, your code
Service tasks park as durable jobs your own services pick up — ordinary C# against your own data, while the engine stays managed. Workers speak the REST job API today; a typed .NET SDK is in progress.
Pragmatic
Simple APIs for starting, running, and observing workflows. No ceremony between you and a running process.
Native BPMN 2.0
Run the diagram itself — no translation layer. Exclusive and parallel gateways, timers, message events, user tasks, and error boundary events execute today; the rest of the spec is still being worked through.
No runtime surprises
A diagram using an element the engine does not support yet is rejected at deploy time, naming the offending element — never discovered halfway through a production instance at 3 a.m.
On the record
Every transition emits an immutable execution step, so the history you read back is the engine’s own record rather than a reconstruction. Live token positions, incidents grouped by error, and a jobs panel for triage — OpenTelemetry traces are still ahead of us.
Deploy your way
One click from the modeler, or one command from CI
Publish straight from the browser, or point your pipeline at a .bpmn file in your pipeline. Either way, Sheptra Cloud parses it, validates it, versions it, and runs it.
The diagram is the artifact
No codegen, no DSL drift. The file you deploy is the file your analysts see.
Zero-downtime versioning
New instances start on the new version; instances already running finish on the one they started with.
One version in production
There is no release matrix to reason about. Every fix reaches every customer at once, because we run the only copy there is.
Program.cs
using var http = new HttpClient { BaseAddress = cluster };
// ship the diagram, exactly as modeled
var id = await http.PostBpmnAsync(
"/v1/definitions",
"order-fulfillment.bpmn");
// start an instance — the cloud takes it
var variables = new { orderId = "ord_2481" };
await http.PostAsJsonAsync("/v1/instances",
new { definitionId = id, variables });
// service tasks: your worker, your code
var jobs = await http.PostAsJsonAsync(
"/v1/jobs/activate",
new { type = "charge-card" });Plain HTTP is the contract today — the typed .NET worker SDK is in progress, not shipped.
1,035/sprocess instancesstart → complete, one host, no network hop
14.9msend-to-end, p50same run · p95 18.5ms · p99 28.3ms
Betano SLA yettargets get published when we can back them
0servers to managewe run the engine, you run the business
Enterprise
The answer to a security review isn't a download
Sheptra runs in our cloud, and only in our cloud. Isolation is meant to be a dial rather than a binary — but only the first rung exists today, so here is the ladder with the honest labels on it.
01 · Rung
Shared plane
TodayLogical isolation per workspace, encrypted at rest and in transit, with a retention window you set. What every beta workspace runs on.
02 · Rung
Dedicated database
PlannedYour data in its own Postgres instance, in the region you pick. The rung most security reviews actually ask for.
03 · Rung
Dedicated compute
PlannedYour own engine nodes, not just your own tables — no shared runtime for the workloads that cannot share one.
04 · Rung
Private link + your key
PlannedA private endpoint that never crosses the public internet, and encryption under a customer-managed key you can revoke.
Rung 01 is what every workspace runs on today. Rungs 02 and up are the roadmap, not a menu you can order from yet — if your security review needs one, talk to us and we'll tell you plainly where it stands.
Trust & compliance
Encryption at rest & in transit
SSO with role-based permissions
Configurable retention & archive
Audit trail of workspace changes
SCIM directory sync
SOC 2 Type II
Independent penetration test
DPA & subprocessor list
Live today Planned
Pricing
Priced by what actually costs something
Running one more process instance costs us close to nothing, so we don't meter you into a corner. What costs real money is the availability we promise and the isolation we provision — so that's what the tiers are built from.
Developer
Free in betaA sandbox to think in.
- 1 sandbox cluster
- 5,000 instances / month
- 3 modeler seats
- 7-day history
- Community support
Team
Coming soonOne process, in production.
- 1 production cluster
- 10 modeler seats
- 30-day history
- Email support
Business
Coming soonA pipeline, not a project.
- Dev, staging & production clusters
- 25 modeler seats
- 90-day history + archive
- SSO, engine audit log
- Business-hours support
Enterprise
Coming soonIsolation on your terms.
- Dedicated database & compute (roadmap)
- Private networking, customer-managed keys (roadmap)
- Region of your choice, custom retention
- Unlimited seats within quota
- Uptime and support terms agreed per contract
No prices yet, and nothing here is for sale — we're not going to invent a number, or take a signup, while the platform is still being built. The tiers above are the shape we're aiming at, published early so you can tell us where it's wrong.
Why the engine is called “Greyson”
Named for a very good shepherd
Greyson was a miniature blue merle Australian shepherd — one blue eye, one brown — who shepherded our family for thirteen years.
The engine behind Sheptra carries his name. It moves every token with the same calm, reliable presence he gave us every day — always watching, always steady, quietly keeping the flock together. That is where “calm execution” comes from. It described him first.
Your process is already drawn.
Now run it in the cloud.
Not yet — the beta isn't open. When it is, it starts with a free sandbox cluster: bring a diagram and a real process, and we'll tell you straight which parts aren't finished.
Beta not open yetComing soon