Komposia — why it exists

Since AI exploded, I keep hearing: "why bother, I ask Claude and I have running code in 10 minutes." I see the power of that every day. That's actually why I built Komposia with AI — and I'll go further: I built it for AI.

JSON is its native language. An entire app as pure configuration — readable, patchable, versionable by an agent without ambiguity. No code to interpret, no context to reconstruct. A contract.

The debate isn't AI vs no AI. The debate is: what happens after the first prompt?

After the prototype, you have to manage multiple clients, multiple apps, each with its own auth, i18n, multi-tenancy, providers — Vercel, Atlas, Railway, Resend, Anthropic, storage. You need to govern data, make apps communicate for a single client, monitor consumption, handle billing, manage errors. Classic agentic dev doesn't solve that. No low-code solves that. Those are building tools. Komposia is an operations platform.

I made a choice that's open to debate: in the JS world I grew up in, everything ends up as JSON. So I pushed that to the limit — an entire app as pure configuration, storable, versionable, and natively readable by AI.

From that, two engines were born: one to define, one to render. And to avoid the classic black box — where you spend your time bending the tool to do something that should be simple — I chose the IDE. Nothing beats a good IDE.

The real challenge was the pipeline engine and the DSL. How to execute code without a broken sandbox, without new Function, without eval(). The answer came from MongoDB and its MQL. This engine lets us code everything in JSON today — yes it's verbose, but that's where AI absorbs the verbosity.

Classic agentic dev has a blind spot: AI generates in a vacuum. Every run is a reinterpretation. Nothing is guaranteed, nothing is auditable, drift is structural.

With Komposia, agents operate on defined contracts. The DSL is a bounded space that AI understands natively — it doesn't guess, it reads, patches, extends. Reproducible. Versionable. Portable. The moment I saw specialized agents adding their own tools based on the pipeline engine, I knew the paradigm held.

Studio + rendering engine. Customer management and their apps. Data governance scoped by cluster, customer, site. Inter-app communication for a single customer. Monitoring, consumption, errors. Billing.

All your work is exportable as JSON. You can build your own engine on top if you want.

A production tool without a community is a solo tool.

What you build — a pipeline, a component library, a full app — you can package it, publish it, monetize it. Others import it in one click, fork it, adapt it. All in JSON, zero black magic.

Komposia can become a revenue stream in its own right. You produce once, you distribute at scale.

Long term: the best multi-tenant auth pipeline or the best content generation agent shouldn't be reinvented by every dev who starts out. They're in the marketplace. You pick, you adapt, you move forward.

This is a beta. Breaking changes are possible based on your feedback, so not for client production yet. Free during this period. The only external dependency: your Anthropic key. After months of testing, Sonnet and Haiku are the best performers — but that's temporary.

If you test it, the only thing I ask: tell me which of the three proposed plans you would have chosen. It's for investors. 😅