What this website costs to run. The whole bill, line by line.

Every quote for a website, an app or an agent contains a line for hosting, and almost nobody on either side of that quote knows what the number should be. The buyer cannot check it. The seller is often passing on a guess. And the one document that would settle it — an actual bill — is the one thing nobody publishes.

So here is ours. This site runs on Vercel. We pulled the billing records through Vercel's own billing API on three separate days in September 2026, rather than reading a pricing page, and these are the numbers that came back.

Forty-one of fifty lines are zero

The first thing you notice opening a cloud bill is that it is enormous and almost entirely irrelevant. Ours carries fifty distinct line items every single day. Nine of them have a number on them. The other forty-one bill at exactly zero — Queue Message Deletes, Sandbox Provisioned Memory, Blob Storage Size, BotID Deep Analysis Requests, Firewall OWASP Excess Bytes, and thirty-six more.

That ratio is not a criticism of the platform; it is the shape of every usage-priced product. But it is why people cannot read their own bill, and it is worth naming as a buying problem: a bill that lists everything you are not using hides the three things you are.

The nine lines that are not zero

Serving the website is free. Watching it is not.

Read that table again with one question in mind: which line is the website?

Edge Requests — every visit. Fast Data Transfer — every byte sent to every reader. Build Minutes and Deployment Storage — building and storing the thing. All four billed $0.0000, on all three days, comfortably inside the plan's allowance.

The largest single line, every day, is Observability Events: 53%, 57% and 38% of the bill on the three days. That is the cost of recording what happened. Second is compute — provisioned memory and active CPU — which on a site built as static HTML is the analytics endpoint and the counter, not the pages.

Which gives the actual finding, and it is not the one we expected when we opened the API:

Three things this changes about buying

1. Stop negotiating the hosting line. For anything the size of a professional firm's website, it is noise. A supplier quoting you £40 a month of "hosting" for a brochure site is quoting for their time, their margin or their risk — which is legitimate — but not for infrastructure. Ask which.
2. Ask what the observability costs, because on our bill it is the biggest thing and it is invisible in every quote we have ever seen. It is also the line you least want cut: it is the record, and the record is the product.
3. Look at list versus billed. Ours ran $0.95–$1.19 at list against $0.28–$0.52 billed — roughly two thirds absorbed by the plan. That gap is the number that moves when you grow, and it is the one nobody models. It is the same shape of trap as per-minute AI pricing: fine until it is not, and the crossover is never on the pricing page.

What this does not tell you

It is one site, ours, with modest traffic, built as static files with almost no server behind it. A firm running a customer portal, a database or a document store will have a different bill with different big lines, and a site with a hundred times the traffic will cross into paid transfer. Do not take our numbers as yours. Take the method: pull your own billing records through the API rather than reading the invoice total, sort by cost, and look at what is actually at the top.

It also does not price the thing that actually costs money, which is not infrastructure at all — it is the deciding, the building and the supervising.

That is the argument in the £200 floor, and it is why the triage tool asks about hours before it asks about software. If you want to see the same discipline applied to every other number on this site, the register is here, and the pipelines we build are what put a bill like this in front of a person on a schedule.