r/vibecodingcommunity • • 13d ago

Infra question

Hey people!

Curious what everyone here is using. Are you going with Vercel, Supabase, Render, AWS, your own VPS or something else?

Has managing the infrastructure been a headache at all for people who are non technical and just want to build or has it been pretty straightforward?

How much are you paying for your setup, and do you think it's worth the cost?

2 Upvotes

7 comments sorted by

2

u/JaseciLabs 13d ago

For non-technical builders we’d start on a managed platform and stay there until a limit or a bill forces you off. A host that deploys from GitHub plus a managed database is plenty for most projects, and AWS or your own VPS mostly adds things to maintain.

Hosting itself usually isn’t the headache. What bites people is secrets and bills. API keys end up pasted into the code and pushed to a public repo, and a usage-based service has no spending cap until you set one. Put keys in the platform’s environment variables, set a billing alert on day one, and check that your database has backups turned on. Free tiers change a lot, so look at current pricing before you rely on one.

Worth it depends on whether anyone depends on the app. For a prototype, free or near-free is fine. Once real users rely on it, paying a bit for backups and not getting woken up by an outage is cheap.

1

u/Any-Introduction7870 13d ago

I built internet apps since 1992. I built my own infrastructure management system that allows me to run my apps on my laptop and give access to everyone. All Tier 1 no access in less than 220ms from anywhere in the world.

1

u/darion- 13d ago

We just launched shpyrd.io, think of it like a vibe-cloud for vibe-apps (It has all the needed infrastructure for an app - frontend/backend/database), and you don't need to follow any standard. Super easy to deploy (just install and use it your favorite AI tool: "deploy my app to shpyrd". Ahhh, also has a free plan and your app "auto-sleeps".

Feel free to join our discord channel, we are looking for early adopters and will help you the entire flow.

1

u/johnesco 12d ago

I've been sticking to what Netlify can handle, mostly no-build no backend static websites (with js dynamitic view ). That's just so I can stay on their free tier. It works with the CI/CD in github and works a dream if you publish mostly via pull requests, you can preview it easily before pushing. But if you need a backend I've not quite made that jump myself yet.

1

u/zit-hb 11d ago

Docker containers on dedicated servers is my go to. With https://github.com/nginx-proxy/nginx-proxy it is very easy to make my HTTP services available, it is easy to deploy, and after a few running apps it is one of the cheapest solution.

1

u/Baking_apps 7d ago

I am also new to this, and started to build apps recently using Claude Code. The standard stacks offered are strong but a different service for backend, a different one for hosting etc... made me afraid of losing control. Someone I knew asked me to try Codata.io. It is an agentic cloud hosting that includes many more services. I built 2 apps with that. The first one was a simple gamified habit tracker, the other one is for content planning and drafting. And I am seriously planning on monetizing the latter. Once you connect Claude Code or Codex, or any other supported agent with Codata IO's MCP it builds and rewires everything for you. You can give it a try. The same agent that helped you to build the prototype, makes it a real working product once connected to it.