Roadmap
Roadmap
What the platform can actually do today, organized by what it helps with rather than which internal tool provides it. This list grows as new capabilities are built, unlike v1 Overview, which describes one specific release.
Status
Available
In dev
Planned
Milestone
Pilot
GA
Building a new service
| Capability | Status |
|---|---|
| A new service can be built in Go or Rust from the start | In dev Target: Sep 11, 2026 |
| Multiple functional APIs can be combined into a single container | In dev Target: Oct 9, 2026 |
| A team building a pilot component only has to write the actual business logic; the underlying scaffolding is already hardened and reusable | In dev Target: Jan 27, 2027 |
| A new team can scaffold a tested, working service on their own, using documented, default tooling | In dev Target: Jan 27, 2027 |
Everyday developer experience
| Capability | Status |
|---|---|
| A stable, documented local development environment that stays consistent with production | In dev Target: Nov 13, 2026 |
| A single, standard way for engineers to make changes to the monolith; about half of engineers already use it, and the older tool is being phased out | In dev Target: Nov 13, 2026 |
Observability
| Capability | Status |
|---|---|
| Monitoring is automatically set up for your app and picked up in production, with no configuration needed | Available Pilot |
| Monitoring is automatic, consistent across every component, and fully self-serve, with no platform-team involvement needed | In dev Target: Oct 29, 2026 |
| A baseline monitoring dashboard is already configured inside every new service’s repository | In dev Target: Jan 29, 2027 |
Testing
| Capability | Status |
|---|---|
| A documented testing strategy is provided to every new modular component | In dev Target: Oct 23, 2026 |
| Contract and performance tests run automatically for pilot components | In dev TBD |
| Fully integrated into Theseus’s end-to-end test pipeline | Planned TBD |
Data & migrations
| Capability | Status |
|---|---|
| Databases and caches can be provisioned, though currently this is done manually | Available Pilot |
| Can automatically provision a database, cache, or other backing store for a new component | In dev TBD |
| A new component can provision its own backing stores automatically, without a manual request to the platform team | In dev TBD |
| A built-in framework handles database migrations | In dev TBD |
Deployment & release
| Capability | Status |
|---|---|
| Supports services that need more than one network port | Available Pilot |
| A hardened, CI-compatible build image available in the development environment | In dev Target: Oct 30, 2026 |
| A declarative way to generate and deploy configuration, already simplifying deployment for Artifact Registry and Orbit | In dev Target: Nov 13, 2026 |
| Every service deploys from automatically generated configuration, fully self-serve | In dev TBD |
| A manual rollback process exists for pilot components, to help recover quickly if something goes wrong | In dev TBD |
| Standardized build images available for components in testing | In dev TBD |
| Supports multiple instances of a resource, like more than one database, in a single service’s setup | In dev TBD |
| Rollback becomes fully automated and standardized across every component | Planned TBD |
| Every component uses the same standardized, self-serve build process | Planned Target: Jan 27, 2027 |
Identity & secrets
| Capability | Status |
|---|---|
| Identity and secrets management is handled centrally, with secure defaults built in | In dev TBD |
Self-managed delivery
| Capability | Status |
|---|---|
| A tested, ready-to-use way to move from GitLab’s older install method to a newer one | In dev Target: Dec 18, 2026 |
| A simple screen for self-managed admins to install, update, enable, and disable components without editing configuration files | In dev TBD |
| A single-machine install option, set up with one command | In dev TBD |
| Every self-managed component using the newer, Kubernetes-based install method is configured the exact same way | In dev TBD |
Status reflects current understanding and may shift as work progresses; check with the platform team for the latest on any specific row.
Last updated on