Doug Mealing runs every commercial engagement personally. Tell us what you're building and we'll tell you, honestly, whether MetaObjects is the right fit.
Concrete project context — what you're building, what stack you're on, what the integration surface looks like, what the team and timeline look like. The more concrete the better.
You don't need a buying signal. Architecture reviews, second opinions, and "is MetaObjects the right shape for this?" questions are welcome.
It isn't a low-code platform or a no-code app builder. It isn't a vendor-lock-in runtime — the generated code is yours, in idiomatic form, in your repo. It isn't a replacement for your engineering team's judgement.
It is a metadata spine for teams who already know they need consistency across languages, services, and the AI-generated code in the middle.
Doug Mealing created MetaObjects in 2001 and used it quietly as the metadata foundation for his own consulting engagements and customer projects for over two decades — pharma regulatory, patented content platforms at Cengage, secure messaging, financial transaction processing, online gaming. The platform never went to market externally; it was the unfair advantage Doug kept to himself.
AI changed the calculus. The same drift problems metadata-driven development quietly solved for two decades are now everyone's problem at industry scale. MetaObjects is being rebuilt TypeScript-first and brought to market under the Draagon umbrella — open source for developers at metaobjects.dev, commercial engagements through this site.