The problem: Almost every company on the cloud struggles with cost management. While optimizing production costs can be complex, reducing non-production costs should be a straightforward case of shutting down resources when they’re not in use. However, most companies lack an elegant solution for this.
The solution: CloudPal
- A downtime scheduler for non-production resources (currently supports AWS EC2 & RDS)
- start / stop button, allowing users to override the schedule (eg. if working on weekends).
Next up on the feature roadmap is:
- Intelligent start / stop functionality for non-production resources - resources will automatically stop when not in use and quickly spin back up when needed, resulting in lots more delicious cost savings!
- Support for more cloud providers and resource types (eg. ECS, K8s, etc.)
We're really happy we get to show this to you all, thank you for reading about it! Please let us know your thoughts and questions in the comments.
Many thanks,
Sri & Brian
Deleted Comment
Users can override it by adding a custom tag to their resources to change the hours or not have the workload shut down. It's reduced our AWS costs tremendously.
Since we heavily push using terraform even for dev stuff, users can quickly re-spin up their instances, fix DNS records and the like with a terraform apply to get back up and running when they get back to their desk.
Another primary reason for them to prefer CloudPal is that most software engineers can use CloudPal without a lot of IaC or AWS knowledge such as tagging resources.
All the very best on the project Sri and Brian. _Eyes on this_
Good luck on your project, though.
Great to offload some of the work to the tools like this!
Congratulations and All the best
Sri & Brain