Nobody lies awake worrying about bandwidth overage. I went looking for what developers actually post about hosting bills, and the fear is more specific and a lot worse than “I used too many gigabytes.”

It shows up in three shapes.

Someone else’s traffic becomes your invoice. From r/vercel:

some random scraping bot farm found our unauthenticated api endpoint and just spent 48 hours spamming parallel requests… small dev teams have to tank unexpected cloud infrastructure bills.

A meter runs out and your live app goes dark. From r/lovable:

It is literally a static site, but because my credits ran low, they completely freeze and lock down the entire workspace and deployment ecosystem… If your credits hit zero, your app goes offline.

You are charged for a thing that is doing nothing. From r/replit:

Now I was able to lower my usage on Replit Agent to zero. My issue is… “Production database compute” that costs 0.16/hour.

Three different platforms, one shared problem: the number on the invoice is not under your control. This post is about what a flat price actually changes, and what it honestly does not.

Fear 1: a bot farm writes your invoice

This is the one that hurts most, because you did nothing wrong and the bill still arrives.

A meter cannot tell a customer from a crawler. On Vercel’s Pro plan, checked against vercel.com/pricing on 3 September 2026, you get 10M Edge Requests and 1 TB of Fast Data Transfer included, then pay from $2 per million requests and from $0.15 per GB. Fluid Active CPU is 4 hours a month included, then from $0.128 an hour. A bot farm hammering an open endpoint for a weekend spends all four of those meters at machine speed, and every one of them is billed the same as a paying user would be.

Vercel is not careless about this. Every new team gets a default $200 on-demand usage budget with email, web and SMS alerts, and you can set it to pause the project when it is hit. There is managed bot protection and Attack Challenge Mode. But look at what the safety net actually offers: a bill, or your site going dark. Those are the two outcomes.

On an InstaPods pod there is no third meter to spend. Requests, bandwidth and CPU time are not counted for billing purposes anywhere in our system. The same bot farm makes your pod busy, your app slow, and your invoice identical.

The honest limits. We do not autoscale, so a genuine flood degrades your app rather than being absorbed by more capacity. We do not ship a managed WAF, so rate-limiting the bot is your nginx config and your job. What we take off the table is the financial consequence, not the traffic.

Fear 2: the meter is also your off switch

The r/lovable post above is the clearest version of this because the app was static. Nothing about the code changed. Only the balance did, and the deployment went down with it.

That is the structural problem with a single credit balance: it pays for building the app and for serving the app, so an afternoon of prompting can take your production site offline. Lovable documents that credits from a monthly plan expire two months after they are issued, and that a custom domain requires a paid plan, which means the subscription quietly becomes your hosting bill long after you stopped building. Replit is the same shape from a different angle: Core is $20/mo for $20 of monthly credits, and both agent prompts and publishing costs come out of that one pot.

There is no balance on an InstaPods pod. Nothing you do in a dashboard drains toward zero, and deploying forty times in a day costs the same as deploying once.

Here is the part I will not pretend about: we do switch pods off. For non-payment, and only for non-payment. The sequence is fixed and it is slow on purpose:

WhenWhat happens
Charge failsSubscription goes past due. Your pod keeps running.
Day 6Warning email: 24 hours until suspension.
Day 7Pod is stopped. Not deleted. Your data is untouched.
+3, +10 days suspendedReminder, then final warning.
+21 days suspendedFinal notice email with a live payment link.
+7 days after that noticePods are deleted.

That is roughly 35 days from the first failed charge to anything being destroyed, with four emails along the way, and paying at any point puts everything back. The difference from a credit meter is not that we never turn anything off. It is that the trigger is an unpaid invoice you can see coming, not a balance you spent asking for a grey button.

Fear 3: paying for something that is doing nothing

The Replit complaint is precise: usage driven to zero, and a database still charging by the hour.

I am going to concede this one rather than dodge it, because the honest answer makes the point better. An InstaPods pod is always on, and you pay for the idle hours too. A stopped pod still bills. Only deleting it stops the charge. If your app gets four visits a week, a scale-to-zero platform will genuinely beat us on price, and Replit’s Autoscale (idle after fifteen minutes, idle time free) is a real option for a prototype nobody uses.

What flat pricing removes is not the cost of idleness. It is the arithmetic. There is no hourly rate to multiply out, no compute unit to reason about, and no month where your database charges more than the month before for reasons you have to go and investigate. $3 is $3 whether the pod served ten requests or ten million.

And the thing charging $0.16/hour in that quote is a database. On InstaPods, PostgreSQL, MySQL or Redis installs inside the pod you are already paying for and adds exactly $0.

What can actually appear on an InstaPods invoice

I would rather show you the bound than assert a vibe, so I went and read our own billing code before writing this section.

Every line item on an InstaPods invoice has the same shape: the pod name, the plan, and the number of days it existed. That is the only kind of charge our invoicer can generate. The one other line that can appear is a negative one, when account credit is applied.

There is no bandwidth field, no request counter, no compute-hour rate and no egress rate anywhere in a plan definition, because those concepts do not exist in the pricing model. There is nothing to accidentally leave enabled.

So the maximum you can be charged in a month is arithmetic you can do yourself:

(each pod’s plan price) × (the days it existed) / (days in the month)

Which means your bill can only move when you move it: creating a pod, deleting one, or changing a plan. Resizes are prorated to the day, so an upgrade on the 15th costs half a month of the difference, not a full one.

Things that do not add to it: traffic of any volume, the number of requests, PostgreSQL, MySQL or Redis, daily backups, custom domains, SSL certificates, team members, deploys, or SSH sessions.

Things worth knowing before you take that as a promise: a card is required before your first deploy (adding one grants a one-time $10 credit), stopped pods still bill until deleted, and the plan prices are $3, $7, $15, $25 and $49 for Launch, Build, Grow, Scale and Turbo.

So where does bandwidth actually come in?

It is real, it is just not the scary part. Per-GB egress is what makes the other three problems expensive rather than being a problem by itself.

Most platforms bill it one of three ways. AWS, GCP and Azure charge per GB out, around $0.09/GB at the first tier. Vercel, Netlify and Render include an allowance and then charge overage, which is where a spike turns into an invoice. Cheap shared hosts advertise “unlimited” and throttle you under load instead, which is one of the four real differences between a VPS and shared hosting and the one people hit first.

We do none of them. InstaPods runs on dedicated servers with unmetered ports, so we are not reselling anyone’s bandwidth at a markup and have nothing to pass through. Worth saying plainly: we also do not throttle. There is no traffic cap and no egress limit on a pod, so a spike makes your app slow only if it exhausts the CPU and RAM you are paying for.

When metered pricing is the right answer

It genuinely is, sometimes, and a page that pretends otherwise is not worth citing.

Metered wins when your traffic is spiky and mostly zero. A prototype with a handful of weekly visits on a scale-to-zero platform will cost less than $3. It wins at serious scale, where per-GB optimisation and CDN edge caching are an engineering discipline with someone assigned to them. And it wins when you need global first-byte times, because a single-region pod cannot compete with an edge network.

Flat wins when the app needs to be up, the traffic is unpredictable, and nobody on the team wants to own a cost model. Which describes most side projects, most internal tools, and most small SaaS apps before they hire an infrastructure person.

The comparison, for an app that stays up

A small production app, one region, always on, with a database:

PlatformWhat you payWhat moves it
InstaPods Build$7/moOnly you: adding a pod or changing plan
Vercel Pro$20/mo per deploying seatActive CPU, memory, transfer, edge requests, build minutes, plus a separate database vendor
Replit Core$20/mo for $20 of creditsAgent prompts and hosting draw on the same balance; Core credits do not roll over
Lovable Pro$25/mo at Lovable’s published rateCredits per edit; a drained balance takes the deployment down
Render$7/mo per service, and $25/mo more for a Pro workspaceEach service is a separate line, disks billed per GB

Competitor figures checked 2026-08-10 and re-verified for Vercel on 2026-09-03. Prices move, so check theirs before you decide.

The actual pitch

instapods deploy my-app --preset nodejs

A real Linux server with root and SSH, a live URL with SSL, a database in the same pod, and an invoice you can calculate in your head before you deploy.

Deploy on InstaPods, from $3/mo flat or see the plans.

Related reading: