Reactive core
Fully non-blocking backend; SQL for typed values and filtering, document store for full objects, search index, cache. Fast on large datasets — bring one and see.
Platform · for the technical visitor
One engine. Every application. The model is the application.
Mosterd is a multi-tenant platform: applications are defined as a declarative model — JSON class files in a Git repository — and generated at runtime. Fields, relations, formulas, layouts, views, scripts. No build step, no deployment pipeline, no framework upgrades.
Write-time computation
Formulas and templates materialise at write; temporal functions (inPast(endDate)) self-schedule re-evaluation at the exact moment their value flips; a dependency graph re-evaluates only what a change affects.
A real business tier
JavaScript at every decisive point of the data flow: create, update, delete, manual actions, data sources. Preconditions as formulas. This is why the “low-code wall” hasn’t appeared: bring your hardest flow and try.
Relations that answer hard questions
Recursive hierarchy traversal in a single model property; filter on Europe, find everything beneath it.
AI in the pipeline
Document triage, extraction, invoice parsing, register enrichment (KvK, Companies House, OpenCorporates); declarative multi-phase AI pipelines with per-call cost tracking.
Your front end, if you want one
The generated UI is built from our published web-component library — forms, tables, dashboards; framework-agnostic, on npm. Build your own app on the same API with the same components.
Authorization you declare, not implement In production
Access rules written over your model’s own relations, materialised at write time so a read stays a single set intersection. Multi-hop propagation, per-user anchored paths, and conditions evaluated against a write’s resulting state; enforced on reads, searches, creates, re-parenting and deletes; published as capabilities so the UI and the server never disagree; with provenance for audit.
Git as source of truth
Branches for DTAP, one repo serving many tenants, modules per tenant, webhook-triggered reload. A tenant costs almost nothing to create, which is what makes disposable environments for verifying a model practical In development
A versioned model format In production
So the platform can move without you. Each file declares its format version and is converted on load; a format change hands back your repository rewritten, with a report. An invalid model is refused with every error at once and the previous one keeps serving. Removed features get twelve months of warnings.
Full documentation for engineers.
Model reference, access control, versioning and the API — at develop.mosterd.com.