Most teams that leave Vercel don’t want to. They leave
because the bill got too big and there’s no middle ground
it’s either Vercel’s cloud or rebuild everything yourself.
I spent 4 weeks building the middle ground.
What I built
A deployment platform where users bring their own cloud
account. You connect your AWS account, CloudFormation
provisions everything inside it automatically. The platform never
touches your data.
Git push to deploy. Works with every static and SSR
frontend framework — Next.js, Remix, SvelteKit, Astro,
Vue, Angular, Vite, all of them.
The architecture decision I’m most proud of
I didn’t build this for AWS specifically.
I built a provider abstraction layer. The platform has no
opinion on which cloud you use. AWS is the first
implementation, but GCP, Azure, or any other provider
is one interface implementation away.
Swap the cloud, everything else stays exactly the same. Same deployment
flow. Same Vercel’s DX. Different infrastructure.
That’s not just BYOC. That’s actual portability.
The stack
- Next.js frontend
- Express API + build worker
- Drizzle ORM on Postgres (Neon)
- AWS ECS Fargate for SSR deployments
- S3 + CloudFront for static
- CloudFormation for automated BYOC provisioning
- Cloudflare for DNS
What it looks like
Built this solo in 4 weeks. Happy to answer any questions
about the architecture or the BYOC implementation.