Roadmap
MDK development roadmap and vision
MDK follows a two-week release cadence to keep progress visible, collect feedback early, and progressively harden the platform — from a rudimentary end-to-end foundation toward a production-ready release.
Release principles
- Release every two weeks to keep momentum and feedback loops short
- Use four maturity phases to mark clear readiness jumps
- Start with a working end-to-end developer experience, then harden progressively
- Reach production readiness progressively, not by a single large release
- Follow standard semantic versioning — the
0.xline means MDK is still in development and not intended for production
Versioning and naming strategy
MDK uses standard semantic versioning (MAJOR.MINOR.PATCH):
- A new version ships every two weeks, bumping the minor:
0.2.0→0.3.0→0.4.0→ … - Patch releases (
0.x.1) go out only when a fix is needed between the scheduled releases, e.g. 0.2.1 - While MDK is in the
0.xline, interfaces may change and the platform is not intended for production — this is the standard semver signal, and we use it deliberately so developers can read it literally 1.0.0marks the first production-ready release
Maturity is tracked by phase, not by version number — each phase spans several bi-weekly releases. The four phases describe how ready MDK is at each stage:
| Phase | Production-readiness |
|---|---|
| Foundation | Experimental. End-to-end but rudimentary. Not stable. |
| Lab testing | Complete enough to build against end-to-end, in a lab. Not stable, not for production. |
| On site testing | Stable enough to test at real sites under real operating conditions, closely monitored. Not yet production-ready. |
| Production Ready | Ready for production deployment, with stable interfaces and compatibility guarantees. |
2026
2026 moves MDK through four phases:
- May: Foundation
- July: Lab testing
- October: On site testing
- December: Production Ready
Between phases, MDK ships a new release every two weeks, starting from the Foundation release at the end of May. The diagram below shows only the phase milestones; the bi-weekly releases land in the windows between them.
Release plan
Phase descriptions below focus on the level of maturity and production-readiness at each stage. The exact feature scope of each two-week release is decided as we go and is not fixed by this roadmap.
Foundation
Released end of May 2026.
The first public release is about visibility, direction, and feedback. It is intentionally rudimentary: developers can clone it, run an end-to-end example, and get a concrete feel for how MDK fits together. Interfaces are expected to change. The goal is to show where MDK is heading and invite feedback from developers, partners, and early contributors — not to support real workloads.
Lab testing
Target: end of July 2026.
At this stage MDK is complete enough to build against end to end. Developers can run a full workflow and experiment with MDK in their own labs. It is not stable — breaking changes are still expected between releases — and it is not ready for production. The goal is to validate the end-to-end developer workflow and surface integration gaps before MDK is exposed to real operational conditions.
On site testing
Target: end of October 2026.
This is the first stage intended for testing at real sites. MDK should be stable enough to run on site under real operating conditions, while still being monitored closely. The goal is to validate performance, robustness, deployment workflows, and operational fit in real scenarios. This is not yet a stability commitment — interfaces may still change before production readiness.
Production Ready
Target: end of December 2026.
This is the first production-ready release (1.0.0). By this point MDK offers a solid baseline for production
deployment, with stable core interfaces, validated workflows, and documentation that supports adoption by operators,
integrators, and developers building on top of the platform. From here, standard semver compatibility guarantees apply.