CLUBER: SaaS Platform for Comprehensive Sports Club Management
Automation of Ephemeral Environments and CI/CD on AWS to Accelerate Development and Improve Code Quality
Accelerate your development with ephemeral environments
THE TAKEOFF
Cluber is a SaaS platform specialized in the comprehensive management of sports clubs. It allows organizations to centralize registrations, payments, communications, and events in a single system, providing a seamless experience for both managers and members.
The main goal was to reduce bottlenecks in the development cycle, optimizing the process of validating changes and enabling teams to work in parallel without conflicts. In addition, the aim was to improve operational efficiency through automated ephemeral environments and a modern CI/CD strategy, all while keeping cost control in place.
TESTIMONIAL
“Ephemeral environments have given us much more flexibility in our development process. Before, we had to wait days to test changes, and now we have an environment ready in 15 minutes. The team can work in parallel without conflicts, and we’ve significantly improved the speed of our iterations. The implementation has been very solid and stable from day one.”
The main goal was to reduce bottlenecks in the development cycle, optimizing the process of validating changes and enabling teams to work in parallel without conflicts. In addition, the aim was to improve operational efficiency through automated ephemeral environments and a modern CI/CD strategy, all while keeping cost control in place.
PROJECT PHASES
Phase One: We identified bottlenecks—validations that took 48–72 hours, shared environments causing conflicts, and a high risk of manual deployment errors.
Phase Two: We migrated from Jenkins to GitHub Actions, defined all infrastructure as code with Terraform/Terragrunt, and deployed services on AWS ECS with dynamic load balancers and auto-scaling.
Phase Three: Each Pull Request spins up its own isolated environment with a unique subdomain, database, and automatic routing rules. They are destroyed upon closing the PR, ensuring zero orphan resources and cost optimization.
Phase Four: We limited to 6 simultaneous environments, enabled proactive monitoring in CloudWatch, and laid the groundwork for broader DevOps adoption and more frequent releases.
PR validation
Simultaneous environments
Feedback time