Skip to main content
Vibe Code Forum

Article: Keep costs under control: credits, tokens and surprise bills

Vibe coding can be cheap, but there are three places money disappears: the AI tools you build with, the services your app uses, and hosting. Prices and free limits change often, so check each tool's own pricing page; this guide is about the habits.

1. The tools you build with

App builders and AI editors usually have a monthly plan with a usage allowance (messages, credits or requests), and charge for, or slow down, usage beyond it.

  • Small, specific requests cost less than vague ones that need five follow-ups.
  • Don't loop. Asking the same failing fix ten times burns credits. Roll back and rethink instead. See When it breaks.
  • Start fresh chats for new tasks; long conversations cost more per message. See Tokens and context windows.
  • Agents use a lot. A long agent run can use as much as hours of chat. Give agents small, clear tasks.
  • Watch the usage page weekly in the first month until you know your pattern.

2. The services your app uses

If your app calls an AI model, sends email or texts, or uses maps, you pay per use, and so does every user and every bot that finds your app.

  • Set a monthly spending cap at each provider where possible, plus email alerts at, for example, 50% and 80%.
  • Rate-limit your own endpoints: a limit per user per minute stops one person (or a script) running up the bill.
  • Cache answers that don't change instead of calling the API every time.
  • Pick the right model size. Small, fast models are much cheaper and fine for simple jobs like tagging or short summaries.

3. Hosting and databases

Free tiers are generous for learning. Costs grow with traffic, storage and always-on servers.

  • Turn on billing alerts before you upgrade from free.
  • Delete projects, databases and preview deployments you no longer use.
  • Look at the usage dashboard after any launch or post that brings a spike.

The surprise-bill checklist

If a bill jumps: check which service, then which project, then which day. Usual suspects are a leaked API key (revoke it; see I pushed my API key to GitHub), a loop calling an API, a bot hammering an unprotected form, or an agent left running.

More in Build guides