We open-sourced
the interpreter.
The architecture every Flutter code-push tool runs on is public. Full reference implementation. Production-grade. On GitHub under MIT — free to use, fork, and ship on infrastructure you control.
We said we'd open-source it.
On August 9, we did.
Promises are easy. Shipping the floor of a category under MIT is not. This is the line we said we'd cross — and we crossed it.
Flutter compiles AOT. True over-the-air Dart updates need an interpreter — especially on iOS. That architecture is the floor of every serious code-push tool. It was sold at a premium. It isn't anymore.
Own the baseline. Run it on your cloud. Audit it. Fork it. No vendor between your patch pipeline and your users.
The foundation is public. Build above it — don't rent it.
Everything the category charges for.
Yours now.
Six pieces. Nothing held back. Same bar we hold commercial releases to — on GitHub today.
The complete interpreter — the pattern every code-push tool in the category runs on. Documented end to end.
Full patch loader and apply pipeline — from fetch to running code. Nothing held back.
The wire format, fully specified. Read it, implement it, extend it.
Full documentation and a rigorous test suite. Your CI can trust it from day one.
Deploy-ready setup for your infrastructure. Spin it up anytime. Answer to no vendor.
MIT. Use it, sell it, ship it. The license means what it says.
Every Flutter code-push tool on the market runs on some flavor of the same interpreter architecture. It's the baseline of the category — well understood, well hardened, and still sold at a premium.
Ejenix moved past it. We integrate at the engine layer — native speed, review by design, every operation cryptographically signed. The interpreter tier is no longer where our value lives.
So we released the reference implementation as infrastructure, not as a gesture. Use it. Build on it. Fork it. Sell it, even.
Open-sourcing something this foundational isn't small. We're proud it's out in the world.
Clone it. Deploy it.
It's yours.
Containers and templates for the major clouds, or your own metal. No signup. No key exchange with us. From clone to a running service in one sitting.
Production code.
Public license.
It cleared the same production review and test suite as our commercial releases — documented by engineers whose work has to survive customer audits.
There is no separate track for public code. One bar. This codebase was held to it.
The code was ready. On August 9 the calendar caught up — and we shipped.
Asked candidly.
Answered candidly.
The questions everyone asks when something this large goes public.
Yes. Full repo on GitHub, MIT, as of August 9, 2026. No waitlist. No form. Clone it.
There isn't one. We don't monetize the interpreter tier. Giving it away doesn't cost us the business — it raises the floor for everyone.
Yes. V1 is out. Next versions ship the same way our commercial releases do — versioned, signed, and public.
Yes. Use it, build on it, fork it — sell it, even. MIT means what it says.
The baseline just changed.
Go build.
What you ship on top of it is yours. We're here for what comes next.
Fork it. Deploy it. Break it and send a patch. The floor of Flutter code-push is public now — the work above it is the part that matters.