STACKS
Certified governance, automated flexibility
Let devs choose approved and appropriate infra configurations from a custom service catalog you own – and say “no more” to forced migrations by using certified, user-friendly Stacks. Platform maintainers release at their pace and app owners upgrade when they’re ready with Stack Versioning. This is a fundamental shift in managing your infrastructure lifecycle and service catalog.
Governance without the Handbrake? You own your Cycloid
SERVICE CATALOG
Are expert-only config processes, inflexible Git templates, and lack of governance and observability hurting your delivery? Stacks allow you to easily reproduce automation parameters across environments encouraging best practice and compliance in a full GitOps approach. Stack Versioning introduces a decoupled workflow where platform teams iterate and production environments only use certified Stacks for reduced downtime.
Faster deployment
Reduce time-to-market and eliminate human error with pre-configured, up-to-date, and validated Stack options.
- Easy configuration process
- Access to public and private stacks
True governance
Ensure production only uses certified tags, while development teams safely test feature branches.
- Pick specific Git tags or branches directly during the component creation wizard.
Managed flexibility
Bring flexibility to your end-users while ensuring governance by offering a private service catalog created by and for your teams.
- Custom rules and variables
- Version control and factorization
- Different scenarios/use cases for one Stack
Zero lock-in
Own your automation and deploy anywhere.
- Reproducibility between different environments
- Automation stored in your Git repository
- Deploy on traditional hosting, public and private cloud, Kubernetes, PaaS, etc.
Safe transitions
No forced migrations. Upgrade a component when it’s ready – reducing downtime risk and daily friction.
- Look for “Update Available” badges on your components and projects
- Cycloid now tells you exactly when you’re falling behind.
Full visibility
Stop guessing who’s on what. See your stack footprint across projects and environments.
- Use the new “Adoption” tab to track version distribution across your organization
- Perfect for auditing and technical debt management.
USE CASES
How Stacks and Stack Versioning works
From your service catalog, pick the component, then upgrade (or downgrade) on your own terms. Thanks to Stack Versioning, you’ll know that production environments only use “Certified” tags, while development teams experiment with bleeding-edge branches, reducing downtime and day-to-day friction.
Real world use cases for Stack Versioning
The Sandbox Sprint
Create a new feature branch for your stack (e.g., feat/eks-1.31-upgrade), spin up a test component to validate it, and iterate without ever touching the main branch used by the rest of the company.
Legacy Support
Keep your “Old-but-Gold” legacy apps on v1.0.0 stability while your new microservices take advantage of the high-performance features in v2.4.0.
Staged Rollouts
Deploy a new stack version to your Staging environment first. Once it’s battle-tested, roll it out to Production at your own convenience.
Technical Debt
Audit instantly by identifying which projects are relying on deprecated versions and plan your upgrade paths efficiently.
Start your first Stack in just a few clicks!
Stacks in detail
Dive deeper into the technology behind Stacks or see our list of popular repositories on GitHub.
