
Trust Runtime is just a server. It turns business intent into running applications through files, events, and recipes. We partner with the people who put it to work.
Every collaboration starts with your domain. We map it to Trust Recipes, run it on Trust Runtime, persist it through Trust Fabric, and evolve it inside Trust Factory.

"If you have built castles in the air, your work need not be lost; that is where they should be. Now put the foundations under them."
Each partner brings different demands. Here is how Trust Runtime, Fabric, Recipes, and Factory show up for each of them.
You craft the experience. Trust Runtime executes beneath it.
Your clients expect pixel-perfect interfaces. They also expect a backend that just runs. Trust Runtime is just a server: it executes the recipes that describe your client's business, so you can stay focused on the experience.
Your advantage
Every client project ships with Trust Runtime and Trust Fabric from day one. No backend hiring, no infrastructure debates. You point at a set of Trust Recipes and the runtime takes care of execution, events, and persistence.
Best fit: Teams delivering React, Next.js, or custom UI who want Trust Runtime as their default backend partner.
Your idea deserves an engine that executes your intent.
Not every product fits a standard SaaS template. With Trust Recipes you describe commands, events, and policies as files. Trust Runtime turns that business intent into a running application, with Trust Factory helping you author it.
Your advantage
Skip months of backend and DevOps work. Launch on Trust Runtime with recipes tailored to your domain, and evolve by editing files instead of rewriting services.
Best fit: Founders building products that outgrow standard SaaS, with event-driven or AI-native requirements.
When your MVP becomes real, your runtime needs to become real too.
You proved product-market fit. Now the system behind it needs to scale without accumulating debt. Trust Fabric handles event processing and persistence; Trust Runtime executes the recipes that encode how your business actually works.
Your advantage
Stop hiring engineers to babysit a hand-rolled stack. Move to a documented runtime where recipes capture behavior, the fabric captures history, and the factory keeps both moving.
Best fit: Series A/B startups replacing their first backend with Trust Runtime for the next 10x of growth.
Innovation inside structure.
Large organizations struggle to move fast without breaking what works. Trust Runtime is just a server: it runs next to your current stack and executes new recipes without forcing a migration.
Your advantage
No more 18-month rewrites. Introduce Trust Runtime incrementally, one recipe at a time, while your existing systems keep serving production traffic.
Best fit: Internal product teams adding AI features or modernizing data processing on top of legacy systems.
AI is not a feature. It is a design principle.
If AI is core to your product, your backend has to be designed for it. Trust Fabric provides event sourcing and CQRS by default; Trust Factory uses AI to help you author the recipes Trust Runtime executes.
Your advantage
An execution engine that mirrors how AI actually works: declarative, event-driven, with full history. No bolted-on AI integrations, just recipes and events the models can reason about.
Best fit: Teams building recommendation engines, intelligent automation, or AI-powered platforms on Trust Runtime.
Build something meaningful. Keep full control.
Not every builder wants hyperscaler lock-in. Trust Runtime is just a server you can run anywhere, executing recipes you own. No framework lock-in, no opaque platform between you and your code.
Your advantage
Enterprise-grade execution without enterprise overhead. Recipes as files, events in your own fabric, runtime on your own hardware. Fully transparent, fully yours.
Best fit: Indie hackers, solo founders, and small teams who want Trust Runtime on their own infrastructure.
No framework lock-in. No hidden platform. Just a server that executes the recipes you own.
Run the engine on your own infrastructure, in the EU, or on-premise. It is just a server: no hyperscaler dependency, full sovereignty over your data.
Business intent lives in declarative files: commands, events, and policies. The runtime stays the same as people come and go.
Event processing and persistence under the hood, AI-powered authoring on top. Your domain evolves without rewriting the engine.
Bob and David do not just build Trust Runtime, they build on it. These are the companies and products they founded, each one a live proof of the same principles at commercial scale.
Financial truth infrastructure
Financial infrastructure for high-volume digital companies. Actuals establishes financial truth across the stack before numbers reach the ERP, running for customers like Just Eat, Wolt, Recharge, and EasyPark at tens of thousands to millions of transactions per day.
Privacy-compliant data orchestration
A low-code platform for privacy-compliant data orchestration and AI. Configure client- and server-side data collection, distribution, and access as declarative services, used by NPO, Vodafone, and Consumentenbond among others.
The AI-native operating layer
Every order, payment, and decision is a business message. DataInbox turns those continuous messages into governed, contextual, accountable operations across humans, systems, and AI agents. Deterministic rules, full context, sovereign infrastructure.
Deprescribing sleep medication
Ready-to-use materials, project support, and a fall-prevention programme for pharmacies, GPs, and regions that want to help patients taper sleep medication. 37% fewer chronic users after 1.5 years, a domain proposition on the runtime.
Trust is a long-term commitment. These are the practitioners whose thinking, craft, and judgement have shaped how Trust Runtime shows up in the world.
Software architect and connector, former CIO of AFAS Software
As CIO at AFAS, Rolf led the shift from hand-written code to model-driven engineering, a 200 man-year investment to decouple technology from functionality in the Profit ERP. That same conviction, that software should be described declaratively and outlive the frameworks it runs on, is what makes his voice a reference point for Trust Runtime.
Founder of Benzomoe, healthcare and deprescribing lead
Klaas Jan brings principled architecture into a domain where it has to actually change lives: pharmacies, GPs, and regional programmes that help patients taper sleep medication. Benzomoe is that work made concrete, and a live example of a domain proposition running on Trust Runtime.
"Actuals proved the pattern: event-driven, privacy-by-design, built on the same runtime we ship today."
