MetaObjects has been the metadata spine for regulated, multi-tenant, multi-team production systems for two decades. The standard and all five ports are open source under Apache 2.0; the enterprise programme adds the support, governance overlays, and roadmap influence that large engineering organizations need.
Customer-specific behavior without forking the codebase: overlay files sharing a package and object name are merged by the loader, so a tenant layer extends the base model instead of forking it. The deepest production use of this is from the Java lineage — Liquent at PAREXEL ran per-customer pharma customizations through metadata overlays: model extensions, UI behaviors, access controls.
A platform team publishes the shared part of its model — customers, an audited base, common enums — and product teams build on it as a versioned, hash-locked dependency instead of a copy. When the shared model moves, each team's drift check reports it rather than two copies quietly disagreeing. Today the TypeScript toolchain publishes, and TypeScript and Python projects consume it from a checked-out repository path; Java, Kotlin and C# follow in a later phase.
One model produces idiomatic TypeScript, Java, Kotlin, C#.NET, and Python. Generated code is yours to own — no proprietary runtime, no vendor lock-in.
The same model is live at runtime, not just at build time — CRUD, validation rules, relationships, and dynamic admin UIs follow the metadata rather than hand-written plumbing, so a validation or a display rule changes where it is declared. Structural change is still a migration: adding a column means meta migrate and a deploy, and MetaObjects ships no workflow engine.
The same fixtures validate every generated artifact across every language. When you ship a polyglot stack, the conformance corpora guarantee the language implementations stay in lock-step.
Every artifact is verifiable against the metadata — including code from AI assistants. Detect divergence between human and machine output before it reaches production.
Production deployments in pharma regulatory (HIPAA, 21 CFR Part 11), patented content systems, financial transaction processing, and secure messaging — built for environments where consistency is non-negotiable.
The open-source standard is what ships today, at 1.0 across npm, PyPI, NuGet and Maven Central. Everything in this section is intent, not product — it is listed so you can tell the two apart, and so an enterprise evaluation can say what it would need. If one of these is what would decide your adoption, that is worth a conversation now rather than after it is built.
Metadata change history, approval workflows, and audit reporting wired into the toolchain — built for compliance and security reviews.
Role-based access to metadata editing and generator runs, integrated with the identity stack you already have.
LTS branches with security backports and migration assistance — for the enterprise procurement cycles that need them.
The enterprise programme is designed to carry direct input into generator priorities, language support, and compliance instrumentation. Stated plainly: MetaObjects has no independent adopters yet — every project on the case-studies page is maintainer-owned — so an early engagement shapes this rather than joining it.
Doug Mealing — the creator of MetaObjects and an issued US patent holder for the underlying content-deployment system — works directly with enterprise teams evaluating or adopting MetaObjects. The engagements are scoped, time-boxed, and focused on getting a real production system live on MetaObjects.
Typical engagements: