What Meridian is

Meridian is an experimental, general-purpose engine for games and interactive applications. It is written in Rust and shaped around one integrated creator application, also named Meridian.

It exists because the game I want to make needs an engine I could not buy. Project Meridian is the first proving game, but the engine is meant to stay useful beyond one project.

One engine, one creator application

The runtime, rendering, asset pipeline, tools, modeler, profiler, build workflow, and play experience are intended to meet inside one application. Some of those foundations exist now. The complete product does not.

The website uses names such as Penumbra, Cairn, Wavefront, and Alluvium to make ownership clear. A name is not proof that a complete implementation exists; the current status page makes that distinction explicit.

Open-source release planned

Meridian is planned for an open-source release under MIT or Apache-2.0, with no engine fee or royalty. Its source remains private during early development, so it is not yet available for public use, modification, or redistribution.

The eventual public repository is planned to contain the engine, specifications, tests, examples, and sanitized evidence. It will not contain Project Meridian’s private creative material.

The game stays separate

Project Meridian is proprietary. Its story, world, art, and future game code live in a separate private repository. Meridian can receive reusable requirements and generated or sanitized fixtures, but its eventual public release must not become a back door into the game.

That separation is deliberate: the game can remain a game, and Meridian can remain an engine other people can actually use.

Where to go next

• Read architecture boundaries to see how ownership is kept explicit.
• Read maturity and evidence before interpreting roadmap language.
• Read the planned source workflow to see how public builds will work after release.