Liria

Open source · Community

No tiers.
No seats. OPEN.

Liria is open source, dual-licensed MIT OR Apache-2.0. There is no pricing table on this page because there is nothing to price: the runtime, the compiler, and the IR spec are free, forever. You verify the claims by running the code, not by trusting a sales call.

License MIT OR Apache-2.0 Pick whichever fits your project. Both ship in the repo.

What OPEN means here

Use it for anything

Commercial, private, embedded, forked. The dual MIT OR Apache-2.0 license lets you pick whichever terms fit your project. No usage cap, no seat count, no phone-home.

Read every line

The runtime, the compiler, the IR spec, the daemon, the example agents — all in the open. The “glass box” is not just a runtime law; it is the licensing posture.

Verify the claims

The replay, trust, and IR command surface is exercised end-to-end by the repo’s gate. You do not have to take a marketing line on faith — clone it and run the quickstart.

·

The 50:50 doctrine

Liria sits on the OPEN side of the MOGOS Collective’s open-vs-paid split: kernels, specs, and the compiler stay free. A paid extension layer can exist alongside an open core, but it must be real before it is named. For Liria today, there is no paid layer to sell — so this page does not pretend otherwise.

If and when a paid extension layer ships for Liria, it will be additive to — never a paywall in front of — the open core you can clone today. Honesty about that boundary is the point of having it.

Clone it. Run it. Keep it.

The fastest way to evaluate an open runtime is to run its quickstart.