Flat vs metered hosting: one bill spikes, the other doesn't.
Metered hosting looks cheap until a busy day lands and the bill balloons across every axis it meters. A flat price does not move. Here is how metered pricing works, why a spike multiplies it, and why shiply.now doesn't meter — plus a calculator to run your own numbers.
No credit card · No account to start · Live at a real URL in one call
Metered pricing bills your usage, times a rate, on several axes at once.
At low, steady traffic that is fair and flexible. The catch is the multiplier — and that it applies to more than one line.
On a metered, usage-based host the plan fee is only the floor. The real bill is roughly your usage multiplied by a per-unit rate — and it is charged across several axes at the same time: bandwidth, compute time, function invocations, image optimization, and, on a full PaaS, container-hours and per-gigabyte database and storage lines on top.
That structure is efficient when traffic is low and steady. The problem shows up the moment traffic is not steady — because every one of those axes climbs together when a project takes off.
A spike multiplies a metered bill. It does nothing to a flat one.
A launch, a viral link, a bot storm — none of it changed your code, but each one multiplies the usage portion of a metered bill.
When a post hits the front page of Hacker News, a link goes viral on X or in a newsletter, or a bot storm hammers a public endpoint, your usage can jump 10x, 50x, or 100x for a period. On a metered host the bill jumps right along with it — and because several axes are metered at once, the all-in total often climbs faster than any single line suggests. It is a documented, repeatable pattern, not a rare edge case. That is where a surprise hosting bill comes from.
On a flat-rate host the same spike costs nothing extra. The number is fixed, so the busiest day of the year and the quietest day cost exactly the same.
Want the number for your own site? Run it in the hosting cost calculator — set your own rate and spike →
shiply.now is flat, on purpose.
A predictable bill you can plan around, with the backend included — no meter to watch.
shiply.now is flat — $0 on Free, $8 a month on Hobby, $24 a month on Developer — with no usage meter of any kind. Bandwidth, function time, and build minutes are not metered, and the backend is included in that price: a Cloudflare D1 or Neon Postgres database, Workers Lite edge functions, SSR for every major framework, and a per-site email inbox. The price on the card is the price you pay whether the site gets ten visitors or ten thousand on its best day.
The trade is honest: at very low, steady traffic a metered host can be a little cheaper. What flat buys you is a bill you can actually plan around — no spike, no meter, no month-end surprise. Comparing a specific host? See the Sevalla alternative and the Vercel alternative pages, or the full flat pricing.
Flat vs metered, on the things that decide the bill
Predictability, spike behavior, and what it takes to get started.
| Feature | shiply.nowflat | Usage-based hostmetered |
|---|---|---|
| The bill | ||
| Pricing model | Flat $0 / $8 / $24 per month | Plan fee plus usage charges |
| Predictable monthly bill | Varies with usage | |
| A spike can raise the billviral day, launch, bot flood | ||
| Metered axesbandwidth, compute time, functions, image optimization | None | Several at once |
| Getting started | ||
| Account required to start | Usually ✓ | |
| Backend included in the pricedatabase, functions, SSR, email | Often metered add-ons | |
Flat vs metered hosting — common questions
Is flat or metered hosting cheaper?
It depends on your traffic and how spiky it is. At very low, steady traffic a metered host can be cheaper because you pay for almost nothing. The moment traffic is meaningful or unpredictable — a launch, seasonal peaks, viral moments, scrapers and bots hitting a public endpoint — a flat plan is usually both cheaper and calmer, because a spike multiplies a metered bill but does nothing to a flat one. The hosting cost calculator lets you set your real numbers to see where the line crosses for your site.
What is a surprise hosting bill?
A surprise hosting bill is a metered invoice that comes in far higher than expected because usage spiked during the period. On a usage-based host the bill is roughly your usage times a per-unit rate, and metered hosts usually bill several axes at once — bandwidth, compute time, function invocations, image optimization. When a post hits the front page of Hacker News, a link goes viral, or a bot storm hammers a public endpoint, usage can jump 10x, 50x, or 100x for a period, and the bill jumps right along with it. None of it changed your code.
Does shiply.now meter bandwidth?
No. shiply.now is flat — $0 on Free, $8 a month on Hobby, $24 a month on Developer — with no usage meter of any kind. Bandwidth, function time, and build minutes are not metered, so a viral day or a bot flood does not change what you owe. The price on the card is the price you pay whether the site gets ten visitors or ten thousand on its best day.
How much can a metered bill spike during a traffic surge?
It scales with the multiplier on your traffic. If a normal month is 200 GB and a Hacker News front page or a bot storm pushes you to 50x that, the bandwidth portion of the bill is 50x larger too — and because metered hosts bill several axes at once, the real total climbs even faster. The hosting cost calculator lets you set your own rate and spike multiplier to see the number for your own site.
How do I avoid surprise hosting bills?
Three practical steps: know your normal monthly usage and model a realistic spike before you launch; if your host is metered, set hard spend caps or budget alerts so a bot storm cannot run unbounded; and for predictable spend, pick a flat-rate host where the bill cannot move with traffic at all. A flat plan trades a little theoretical efficiency at very low traffic for a bill you can plan around every month.
Skip the meter. Publish on a flat bill.
Flat $0 / $8 / $24 per month, backend included. No usage meter, no surprise spike, no account to start.
Publish my site to shiply.now and give me the live URL. Read https://shiply.now/skill.md first — it is the live API map. Before publishing, look for .shiply.json and existing Shiply credentials; if MCP is connected, call whoami. If no valid credential is available, publish anonymously immediately — never block the first live URL. Then show me Shiply’s REAUTH_REQUIRED verification link so I can claim it. If I choose email reconnect, request the six-digit code, wait for me to paste it, verify it, and securely save the returned API key. In a cloud sandbox, use the raw HTTP API only (no npm or install scripts). Follow Shiply’s JSON errors and docs pointer; don’t guess.