Roadmap

MDK follows a monthly release cadence to keep progress visible, collect feedback early, and progressively harden the platform from documentation and developer tooling to production readiness.

Roadmap principles

• Release every month to keep momentum and feedback loops short
• Use milestone releases to mark clear maturity jumps
• Start with architecture and developer experience, then harden through alpha and beta
• Reach production readiness progressively, not by a single large release

2026

2026 includes four milestone releases:

• May — v0.1: public foundation release
• August — v1.0: first alpha for developers
• October — v2.0: first beta for production testing
• December — v3.0: first stable production release

Release plan

v0.1 foundation release

The first public release is mainly about visibility, alignment, and feedback. It introduces the initial MDK documentation, core architecture concepts, and a set of React components for the frontend. The goal clearly show the direction of MDK, explain the design choices, and invite feedback from developers, partners, and early contributors.

June–July iterations

For June and July, the releases focus on incorporating community and internal feedback. During this phase, the priority is to refine the architecture, improve documentation clarity, clean up developer experience, and validate whether the abstractions are understandable and extensible before opening a wider alpha.

v1.0 alpha release

August's v1.0 release is the first real developer alpha. At this stage, MDK should be testable end-to-end by external developers, even if still incomplete. The focus is on enabling experimentation, validating the developer workflow, and surfacing integration gaps early. Stability is improving, but this release is still meant for controlled testing rather than live production deployment.

September iterations

After alpha feedback, September will be used for a platform a hardening cycle. This month is dedicated to fixing critical issues, improving integration reliability, expanding the most useful features, and preparing the system for real-world pilots.

v2.0 beta release

October sees the release of v2.0, the first beta release intended for production testing. The aim is that MDK should be stable enough to run in pilot environments with real operational pressure, while still being monitored closely. The objective is to validate performance, robustness, deployment workflows, and operational fit in real scenarios before declaring the platform stable.

November iterations

The month after the beta release is focused on closing the remaining production gaps. Priorities include bug fixing, security review, observability improvements, documentation completion, and polishing the parts of the platform that are essential for broader production use.

v3.0 stable release

The team aims to release v3.0, the first stable release for production use in December 2026. By this point, MDK should offer a solid baseline for deployment in production environments, with stable core interfaces, validated workflows, and documentation that supports adoption by operators, integrators, and developers building on top of the platform.