Post

Every time a team outgrows Vercel pricing, their only real option is to self-host. And self-hosting means rebuilding the entire deployment pipeline from scratch and saying goodbye to all the DX they loved in the first place.

That felt like a solvable problem. So I solved it. I built BYOC (Bring Your Own Cloud.) You click one button, connect your AWS account, and CloudFormation runs inside your own account.

It provisions everything automatically. My platform never sees your data.But halfway through building it I caught myself thinking okay, but what if someone wants GCP next year?

Am I just moving the lock-in problem from Vercel to AWS? So I went one step further. I built a provider abstraction layer. The platform itself has no opinion on which cloud you use. AWS is live right now. But any other provider like GCP, Azure, whatever is one interface implementation away.

Swap the provider, everything else stays exactly the same. Same DX. Same deployment flow. Different cloud.That's the part I'm most proud of. It's not just BYOC. It's actual portability.

0 reposts1 like

What I shipped in 4 weeks: → Git-push deployments for all frontend frameworks → BYOC with one-click CloudFormation provisioning → Provider abstraction layer built for multi-cloud from day one → Real-time logs → Custom domains with automatic DNS and SSL → Environment variables and usage tracking