A selection of production systems built on MetaObjects — my own consulting engagements, the Draagon AI products I build on it, and the earlier work that came out of two decades of metadata-driven development.
TypeScript / React / MetaObjects
A live AI wizard-council app built to be read: one metadata spine drives the database schema, API types, LLM prompts, and SSE streaming protocol — rename one field and all of them fail in CI. Apache-2.0, clone-and-read.
Python / TypeScript / React / MetaObjects
From 17 runtime schema patches to zero: one ~7,000-line YAML spine generates more than 20,000 lines of drift-checked Python and TypeScript — 44 entities and more than 100 LLM prompts declared once, on the published MetaObjects packages.
Python / Postgres / MetaObjects
Not every adoption is a rewrite. An existing Python voice assistant took exactly two of the six pillars — prompts rendered from typed payloads at runtime, and Postgres schema owned by the CLI — in about seventy lines of metadata, and left the rest of its codebase alone.
Java / Kotlin / TypeScript / MetaObjects
288 hand-written schema migrations collapsed to one generated baseline, ~1,900 lines of hand-built LLM prompts became typed contracts, and the model made deleting dead schema mechanical — 29 tables and 49 columns removed in nine days, each proven safe by a recompile.
TypeScript / Bun / MetaObjects
A 377-line bash system monitor rewritten into a typed, metadata-driven TypeScript project. Probes, verdicts, alert payloads, email templates, and notify adapters are declared as MetaObjects metadata; the registry, type unions, config checks, and docs are generated from it. Honest before/after — including what wasn't clean.
Java 8 / TypeScript (Bun) / Python / MetaObjects
Built rapidly on MetaObjects in the early 2000s; the engine survived two decades and now runs FeltBots, where language models play for measurement rather than money. Its 155-message wire protocol — undocumented for most of that time — is now declared once as metadata, and the TypeScript bridge, the Python bots and the protocol docs are generated from that declaration.
TypeScript / React 19 / Fastify / Drizzle / MetaObjects
The first reference project for the new TypeScript MetaObjects. A modern training and subscription platform at officialmichaelfrank.com — React 19 + Fastify monorepo with subscription management, all driven by MetaObjects schema.
Java / MetaObjects
Customizations per pharmaceutical customer with zero code changes — accomplished by overlaying customer-specific metadata on the base model. Model extensions, UI behaviors, grid layouts, access controls, and validations all reconfigured per tenant by metadata alone.
Java / Salesforce / MetaObjects
Secure messaging and digital contract platform, integrated with Salesforce. Built rapidly on MetaObjects — multiple teams shipped in parallel against the same metadata patterns. Dynamic forms, e-signatures, and confidential data exchange, RESTful integration suite throughout.
Java / MetaObjects
Content deployment pipeline treating content like source code: advanced merging, real-time preview, regenerated derivative artifacts. The first implementation leveraged MetaObjects.
Java / MetaObjects
Production payment-processing gateway built rapidly on MetaObjects — same rapid-development pattern as the poker platform and Sendside. Metadata-driven transaction routing, validation, and audit.
One metadata approach — from a two-day open-source tool to a two-decade production engine.
Every figure is verified per project — see each case study for its sources. The nine projects above are all maintainer-owned. That is stronger evidence than a test suite and weaker than independent adoption.
NIX Solutions can review your architecture, run a pilot or help with migration.
Contract with NIX ↗