Skip to content
4 deployment patterns · 1 runtime · same primitives

Same runtime. Different deployment.

The Sumeru runtime is one platform — but how you deploy it depends on what you operate. Brands get one set of patterns. Agencies running 50 client shops get another. Headless teams plug in via API. B2B accounts get account-level rollup. Pick the path that matches your shape.

By the deployment

Four shapes. One underlying platform.

4
Deployment patterns
9
Engines included
1
Shared runtime
1
Audit log
1
Contract
1
Bill
01 Deployment patterns

Four canonical shapes.

Each has its own sales-call structure, tier recommendation, and onboarding playbook.

02 What stays the same

One platform. One bill. One audit log.

The runtime, the data plane, the security primitives — identical across all four deployment patterns. What differs is the configuration, the tier, and the playbook.

The runtime

Same event bus + workers

5-stage pipeline (ingest → resolve → attribute → action → audit) — identical across all four shapes.

The data plane

Per-shop schema isolation

Schema-level tenancy enforced on every Prisma query. CI lint rule rejects cross-shop reads. Same model, every deployment.

The security primitives

Audit · undo · dry-run

Every autonomous action is snapshot-and-undo, dry-run-gated, and audit-logged. Same in Shopify Plus as in B2B.

Don't see your shape?

Tell us what you operate.

We're working on solution patterns for marketplace operators, multi-region brands, subscription commerce, and creator-led DTC. If yours is different — describe it and we'll prioritise the deployment pattern that fits.