Caproni is now the strategic development platform

Going forward, Caproni is GitLab’s strategic development platform, built for modular services under the Theseus vision. This enables teams to develop and verify their services in a production-like environment.

Over the coming quarters, Caproni will replace the current usage of the GitLab Development Kit, for all GitLab contributors, including team members, customers in the Co-Create Program, and community contributors.

What this means

• Caproni already supports monolith and modular service development (like Artifact Registry).
• New services that need a production-like development environment should use Caproni today; existing teams should plan migrations to Caproni.
• GDK will largely be limited to receive critical bug fixes.

Action required

If your team is building modular services on GDK, please familiarize yourself with Caproni by reading the documentation and let us know any blocking gaps to migrate.

We’re keeping track of enabling edit mode for existing services in a separate epic.

Next steps

We’ll be publishing a full support and deprecation timeline in the coming weeks. In the meantime, reach out in the #proj_caproni Slack channel with questions, read the Caproni docs, or get started with GitLab development using Caproni.