The Story
Blossom was created by Tung Nguyen, an engineer who has spent years building deployment tools and infrastructure frameworks across every major platform.
Experience That Shaped Blossom
Over the years, I’ve built open source tools for every major deployment approach:
- jets - Ruby serverless framework
- kubes - Kubernetes deployment tool
- ufo - AWS ECS deployment tool
- terraspace - Terraform framework
- And many more tools across the DevOps landscape
Through running a DevOps software consultancy, I worked with teams across AWS, GCP, and Azure - seeing firsthand what works and what doesn’t at different scales. I was also fortunate to be recognized as an AWS Container Hero for contributions to the container ecosystem.
Why Blossom?
After building tools for Kubernetes, ECS, serverless, and Terraform - and using them in production across dozens of companies - a clear pattern emerged:
Most teams need platform simplicity, not orchestration complexity.
While working across all these platforms, I saw the same challenges repeatedly:
- Kubernetes was powerful but overkill for most applications
- Serverless was simple but had too many constraints
- Heroku was easy but expensive and locked you in
- ECS was AWS-only and still required deep infrastructure knowledge
Blossom embodies the lessons learned from all of these. It’s the deployment platform I wish existed when I was building those other tools - one that provides platform simplicity while keeping you in control of your infrastructure and costs.
The Philosophy
Engineer at heart: I love learning, tinkering, and solving real problems. Blossom reflects an engineer’s approach to deployment - transparent, debuggable, and built on proven technologies like SSH and Docker Compose rather than complex abstractions.
Experience-driven design: Every architectural decision in Blossom comes from production experience. The “Compose-over-SSH orchestrator” approach isn’t theoretical - it’s what works reliably at scale without the operational burden of self-managed orchestration.
Honest trade-offs: There are no silver bullets in infrastructure. Blossom is designed for the 90% of applications that don’t need Kubernetes’ complexity. For teams running hundreds of microservices across 50+ servers, Kubernetes might still be the right choice. For everyone else, Blossom offers a better path.
Multi-Cloud by Experience
Having worked across AWS, Azure, and GCP through consulting engagements, I understand the value of not being locked into a single cloud provider. Blossom’s multi-cloud support isn’t a checkbox feature - it’s built from the ground up to work seamlessly across all major providers:
- AWS, Azure, GCP (the big three)
- Hetzner, DigitalOcean, Vultr, Linode, OVHCloud (cost-effective alternatives)
- On-premises infrastructure (for regulated industries)
This flexibility comes from years of helping companies navigate cloud migrations and multi-cloud strategies.
The Journey Continues
Building deployment tools has taught me that the best solutions come from understanding the full spectrum of options. Blossom isn’t built in isolation - it’s informed by the strengths and weaknesses of every platform I’ve worked with.
If you’re looking for a deployment platform built by someone who’s been in the trenches of Kubernetes, Swarm, ECS, Serverless, and everything in between - welcome to Blossom.