Break Room / Build it yourself
Six people use it. Now what?
Frank ran the numbers
Congratulations on the six users. Don't rebuild anything yet. Watch for errors, watch the bill, and let real problems tell you what to fix next.
The internet is full of advice for running sites with millions of users. You have six, and that's the right number to be thinking about.
Six users is not a reason to read about Kubernetes. Please step away from the architecture diagrams.
Know when it breaks
Set up a free uptime check that emails you if the site goes down, and turn on error alerts from your host or server function. Most small sites don't fail dramatically. Something quietly stops working and nobody tells you, so the goal is to hear about it before your users do.
Watch the bill weekly
For most AI-powered side projects, the AI calls are the biggest cost. Look at your spending once a week while it's new. If one feature costs more than the rest combined, that's the thing to look at, usually with a shorter prompt, a cheaper model or saving answers you've already paid for. SideFrog runs on about $8 a month for the site itself; here's the breakdown.
Count what matters
Free analytics tell you which pages people visit and what they click. Pick the one or two numbers that tell you the idea is working, like sign-ups or completed checks, and ignore the rest for now.
Add pieces only when you need them
- A database, when the site has to remember something between visits.
- Logins, when people need their own stuff. Use a sign-in service rather than building it.
- Payments, when someone wants to pay. Use a hosted checkout.
- More servers, when your host's own charts say you're running out. On serverless hosting, that's rarely your problem first.
Know when to stop vibe coding
Vibe coding is great for getting to the first real users. When real money, sensitive data or a lot of customers depend on the site, it's time for someone who does this for a living to look it over.
When to get real help
Some things are worth paying a professional for, even on a side project:
- Taking payments. Use a hosted checkout like Stripe's so card numbers never touch your code.
- Health, financial or other sensitive personal information.
- Logins and passwords. Use a sign-in service instead of building your own.
- Anything aimed at kids.
- Real customers depending on it every day.
That's where you stop being cheap. If you want a second pair of eyes before you get there, pick a time with Mark or message him on LinkedIn.
Got an idea? SideFrog gives you a straight verdict, who'd pay, a first test to run and names with an open .com, in about ten seconds.
Check your ideaWant help building it? Mark helps people vibe code their first site with AI. Pick a time with Mark or message him on LinkedIn.
Questions people ask
When does a side project need a real server?
Usually much later than you think. Serverless functions and static hosting handle thousands of visitors a day without you managing anything. Move when your host tells you you're hitting limits, not before.
What should I do if it suddenly gets popular?
Check your bill and your rate limits first, then your error alerts. A sudden spike is often a bot, not a fan club.
Should I rewrite it properly now that it works?
Not until something specific hurts. Rewrites eat months. Fix the part that's actually causing trouble.