I've been building a lot of tools for my company internally and have been doing a combination of self-hosting on VPS/Vercel/whatever else. Super curious how everyone is going from localhost to sharing in your team.
Ask HN: How do you host your vibe coded tools/sites?
1–10 of 11 posts
Re: Ask HN: How do you host your vibe coded tools/sites?
#2Cloudflare workers/pages/D1/R2 works great for me on the free plan. If you’re not familiar, I typically use workers for API type stuff (including auth). D1 is database, R2 is storage (images, files?). Pages are.. pages.
Re: Ask HN: How do you host your vibe coded tools/sites?
#3I use Netlify connected to Github/Gitlab, which does a build on every commit to the main branch. For low-volume static sites (which all of mine are) this is free, fast, and convenient.
Re: Ask HN: How do you host your vibe coded tools/sites?
#4I use Netlify connected to Github/Gitlab, which does a build on every commit to the main branch. For low-volume static sites (which all of mine are) this is free, fast, and convenient.
what about something with a db? or auth?
Re: Ask HN: How do you host your vibe coded tools/sites?
#5Many use our service https://controlplane.com - we have an MCP server that makes it trivial to ask for postgres, kafka, cassandra, mongo, cockroachdb, mysql, or many other databases. It is easy and does not limit you in terms of where you can run (any cloud, on prem), and even run multi-region and multi-cloud. I am interested to hear your experience.
Re: Ask HN: How do you host your vibe coded tools/sites?
#6I use Netlify connected to Github/Gitlab, which does a build on every commit to the main branch. For low-volume static sites (which all of mine are) this is free, fast, and convenient.
what about something with a db? or auth?
I'm actually using Github issues as a low-volume/high-latency DB for a project right now. I use a Netlify function to do extremely simple auth and then open an issue on Github, which triggers a CI action, which appends to a .jsonl file in the repo (different branch), which triggers a Netlify build, which then serves the new jsonl file. (If the repo were public, this wouldn't even have to trigger a rebuild of the website, it could just get the .jsonl from Github directly).
It's totally hack-a-licious but it also totally works for my N<10 users.
Re: Ask HN: How do you host your vibe coded tools/sites?
#7Earlier quoted context omitted.
what about something with a db? or auth?
I'm actually using Github issues as a low-volume/high-latency DB for a project right now. I use a Netlify function to do extremely simple auth and then open an issue on Github, which triggers a CI action, which appends to a .jsonl file in the repo (different branch), which triggers a Netlify build, which then serves the new jsonl file. (If the repo were public, this wouldn't even have to trigger a rebuild of the webs…
Wow that's super cool and creative. I assume this is an internal dev tool?
Re: Ask HN: How do you host your vibe coded tools/sites?
#8[dead]
Re: Ask HN: How do you host your vibe coded tools/sites?
#9Earlier quoted context omitted.
I'm actually using Github issues as a low-volume/high-latency DB for a project right now. I use a Netlify function to do extremely simple auth and then open an issue on Github, which triggers a CI action, which appends to a .jsonl file in the repo (different branch), which triggers a Netlify build, which then serves the new jsonl file. (If the repo were public, this wouldn't even have to trigger a rebuild of the webs…
Wow that's super cool and creative. I assume this is an internal dev tool?
It's for a personal link bookmark site[0]. And I guess I had made the repo[1] public after all. It's been working well for about 6 months now.
Re: Ask HN: How do you host your vibe coded tools/sites?
#10Cloudflare tunnels for stuff requiring an actual machine. Cloudflare or Netlify Pages for static projects (with D1 as a database when needed).