About
CephalonEngine is a modular .NET 10 framework for building production-grade applications without trading away rigor for speed. It is opinionated about the engine, additive about everything else.
Roadmap
The next several minors, the long-range direction, and the .NET 11 readiness lane.
Open the roadmap BacklogBacklog
The full engine backlog grouped by capability.
Open the backlog HistoryRelease notes
Every shipped version with the change summary and link to migration notes.
Open the release notes ProcessGovernance
How planning happens, how decisions are made, how disputes get resolved.
Open governance ReferenceFAQ
Frequently asked questions about scope, performance, licensing, and adoption.
Open the FAQ LegalLicense
MIT-licensed. Full text and what it means for you.
Open the license MarketingPress kit
Logos, screenshots, brand guidelines.
Open the press kitIn one paragraph
Section titled “In one paragraph”CephalonEngine is a modular framework for .NET 10. It composes a small, stable engine with a wide catalog of opt-in companion packages — data adapters, eventing transports, observability providers, identity, multi-tenancy, agentics, retrieval, edge runtimes. Every package ships with an explicit maturity label so adopters know what to rely on. Every public surface has a typed contract recorded in the runtime manifest. The same engine boots an ASP.NET Core host, a generic-host worker, or a custom embedded host — the team picks the shape, not the framework.
Who builds it
Section titled “Who builds it”CephalonEngine is built by Cephalon-Labs and a growing community of contributors. The repo lives at github.com/Cephalon-Labs/CephalonEngine. The docs site is open-source at github.com/Cephalon-Labs/CephalonEngine-Docs.
What we ship every week
Section titled “What we ship every week”The preview track is on autonomous continuous shipping — slice → ship → merge → repeat. The eventing track is currently landing broker topology, partition behaviour, scheduled delivery, DLQ replay, and process manager state proofs. Track progress on the Roadmap.
Where this is going
Section titled “Where this is going”The long-range direction is documented in Roadmap and Long-range direction. Short version:
- adoption-ready engine (M4) across the core + AspNetCore host + Worker.
- adoption-ready data adapters for the most-requested backends.
- adoption-ready eventing for Wolverine plus a second adapter for diversity.
- ship a stable
1.0.0once the manifest schema, runtime contract, and configuration shape are frozen.