Schedule callCluster.dev —
Open Source tool for cloud native infrastructures
- Combine power of all your infrastructure tools
- Create platform-as-a-service for your teams
- Customize your projects and infrastructures
Make your infrastructure outstanding with Cluster.dev!
Previously disconnected tools — now orchestrated
No more bash and groovy wrapper scripts! Pass variables and statuses across your tools. Trigger only the necessary ones.
Cluster.dev makes all pieces of your infrastructure work together as one. And will manage all variables, secrets and dependencies.
No more hidden knowledge for your teams
Observe changes and state of your infrastructure in a single place — your Git repo. Use a common solution for all type of changes. Forget about manual runbooks and CI/CD magic.
You deserve to have an overview of all your infrastructure in a single place!
Cluster.dev is a GitOps-first tool, which means you will always know where and what has been changed.
Confidence in infrastructure changes
Be sure that your tools are doing what you expect them to do.
Everything in Cluster.dev has a state. Even scripts and k8s manifests.
Cluster.dev supports infrastructure testing and allows you to propagate changes with confidence. Observe actual changes that you want to make!
Security, independence from third-party vendors
Pass secrets to third-party tools even if they don't support your secrets store.
With its powerful integration possibilities, Cluster.dev allows you to pass secrets to third-party tools, without any compromises.
Customization for every piece of infrastructure
With its amazing template engine, Cluster.dev allows you to customize configs, scripts, manifests, Terraform code and whole infrastructures.
Reuse the code, create copies of your projects or environments and save time of your team for the real challenges!
Kubernetes operator
Feel the power of self-healing with our major k8s integration.
Upcoming...
Solutions
Too many tools
and solutions?
Check out how Сluster.dev differs from Terraform, Terragrunt, Pulumi, Crossplane and other solutions
How it works
Study the example to understand how templating works in Cluster.dev
Our Clients & Reviews
Partstech
Problem: Old infrastructure was hard to manage as it was not fully described in code. What has been described didn’t match the real configuration.
Solution: The infrastructure has been transitioned under Cluster.dev management. All working is done via Cluster.dev infrastructure repository, ensuring exact correspondence of code to infrastructure.
Deco
Problem: Highload customer websites needed a new infrastructure with dynamic resource allocation, deployed on a cloud with affordable prices.
Solution: Cluster.dev has been customized for working with DigitalOcean cloud provider. A dedicated template has been designed to deploy a fault-tolerant infrastructure for WordPress.
Ewa finance
Problem: Each project needed a separate infrastructure for prod, dev and stage, with the possibility to shut down dev and stage infras beyond working time to save costs.
Solution: We used one of the Cluster.dev stack templates to replicate the environments. The template spins up fully provisioned infras in different AWS accounts and shuts them down when needed.
Partstech
Problem: Old infrastructure was hard to manage as it was not fully described in code. What has been described didn’t match the real configuration.
Solution: The infrastructure has been transitioned under Cluster.dev management. All working is done via Cluster.dev infrastructure repository, ensuring exact correspondence of code to infrastructure.
Deco
Problem: Highload customer websites needed a new infrastructure with dynamic resource allocation, deployed on a cloud with affordable prices.
Solution: Cluster.dev has been customized for working with DigitalOcean cloud provider. A dedicated template has been designed to deploy a fault-tolerant infrastructure for WordPress.
Ewa finance
Problem: Each project needed a separate infrastructure for prod, dev and stage, with the possibility to shut down dev and stage infras beyond working time to save costs.
Solution: We used one of the Cluster.dev stack templates to replicate the environments. The template spins up fully provisioned infras in different AWS accounts and shuts them down when needed.
Blog
