Reference architectures. Real deployment patterns.
Some deployment patterns put an entire supply chain on Createrun. Others cover a single internal tool. Both are right answers — the platform is architected to scale either way. The reference scenarios below show how.
Presented as anonymised reference scenarios — architectural patterns drawn from production experience with the underlying framework, showing how Createrun deployments are designed in practice.
A nationwide grocery retailer — thousands of locations, multiple countries.
Reference architecture — not a named Createrun customer case study.
The business problem: when a product recall hits, tracing a batch back through recipes and suppliers has to take minutes, not days. This scenario models a discount retail chain running its food production tracking on Createrun — recipe versioning, supplier audits, batch traceability, and compliant data retention — with the expectation that a full chain-of-custody answer is always one query away.
The same vertical translates naturally into a partner-built app: package the food-production tracker once, and other retail/grocery companies deploy it on their own Createrun instance via the Marketplace.
What this deployment ships
- Recipe versioning across thousands of private-label products
- Multi-stage supplier audit BPM (RFP → site visit → approval → renewal)
- Batch traceability with full chain-of-custody for product recalls
- Weekly catalog approval workflow — category-manager sign-off
Why Createrun
- On-prem deployment — supplier data never leaves their network
- Per-tenant isolation between buying teams
- Custom forms for each food category without rebuilding the runtime
- Reports authored by category managers, not engineers
At a glance
- Industry: Discount retail / grocery
- Users: Buying + production teams
- Deployment: On-prem
- Data residency: In-country
- Compliance: KVKK
The food production tracker doubles as a Marketplace app for other retail/grocery deployments — vertical knowledge captured once, distributed everywhere.
At a glance
- Industry: European logistics / transport
- Users: Dispatch ops + dock supervisors
- Deployment: Hybrid (cloud authoring · on-prem runtime)
- Data residency: EU
- Compliance: GDPR + customs export controls
Designed to replace a multi-system patchwork of spreadsheets, a custom .NET intranet, and a third-party TMS with one Createrun workflow surface.
A European logistics provider — three depots, one workflow surface.
Reference architecture — not a named Createrun customer case study.
The business problem: shipment data lives in three disconnected systems — dispatch board, dock manifests, driver compliance — and every process change waits on an IT ticket. This scenario models a mid-size road-freight operator running cross-border EU deliveries that consolidates all three into a single workflow surface its own ops team can change same-day.
A staged shipment workflow drives every delivery, and configurable screen components let dispatch supervisors add fields per route (e.g. dangerous-goods class, customs document links) without touching code.
What this deployment ships
- 7-stage shipment workflow with parallel customs + driver compliance branches
- Dock-arrival forms running on rugged tablets at high scan volumes
- Three depots, three instances — licensed and updated from one Marketplace
- Audit-ready telemetry feeding the team's existing monitoring stack
Design goals
- Cut per-shipment manual data entry by replacing re-keying with structured forms
- Let operations change workflow stages same-day, with no deploy gate
- Consolidate the system of record — retire the legacy patchwork
A mid-size hospital system — clinical operations on-prem.
Reference architecture — not a named Createrun customer case study.
The business problem: patient data cannot leave the network, yet clinical and administrative teams keep needing new internal tools. This scenario models a private hospital group that builds them — clinical workflow, admissions, materials management — without ever sending data outside its own walls.
Createrun deploys fully on-prem behind the hospital firewall. No cloud telemetry. The Createrun Agent runs against a self-hosted model. The expected outcome: compliance review stays short, because the entire dependency tree is auditable to source.
What this deployment ships
- Admissions intake forms with conditional fields per department
- Materials management with par-level alerts + supplier portal
- Clinical incident reporting with multi-stage review BPM
- Identity federation with their existing AD + MFA stack
Why Createrun
- Air-gapped install path — offline installer flow
- Source ownership — compliance auditor can read every line
- No mandatory cloud telemetry — observability stack is opt-in, fully local
- Their own AD as IdP — no parallel user directory to maintain
At a glance
- Industry: Private healthcare
- Scale: Mid-size hospital system
- Users: Clinical + admissions + materials
- Deployment: Air-gapped on-prem
- Identity: Federated to existing AD + MFA
Designed so compliance review is ordinary work, not investigation — full app-source export puts every line in front of the auditor.
More reference architectures are in progress. If you'd like to explore how one of these patterns maps to your organisation, get in touch — we'll walk through it together.
In progress · Manufacturing
A mid-market manufacturer pattern: shop-floor data collection + supplier portal on Createrun.
Field-data forms run on warehouse tablets; back-end queries roll up to executive dashboards.
In progress · Financial services
A mid-tier bank pattern: internal compliance reporting + KYC review on Createrun.
Multi-stage approval BPM + audit-grade query stack + encrypted secret store.
In progress · Public utility
A regional utility pattern: customer-billing exception workflows on Createrun.
Worker-driven case management surface with role-based visibility + GDPR data minimisation defaults.
Your scenario?
Don't see your industry here?
Talk to us — we'll map a reference architecture to your use case and walk you through it.
Get in touch →See what's possible — book a demo.
Show us your use case, we'll show you a real Createrun instance solving something similar. 30-minute call, no slide deck.
Book demo