A small business and a developer want opposite things from a bill. The business wants to know the number. The developer wants to pay for exactly what runs. The mistake the industry made was forcing both onto the same model, and then forcing a product change to move between them.
What is not in the bundle. Mail is not offered at launch. Domain registration is not resold; bring your own and the pod points DNS at it. Both are candidates for a paid add on later, and neither is load bearing for the product to make sense.
Nothing on this page is a price list. The numbers are illustrative. What matters is the shape of the model and whether it holds up under questioning, which is the point of the conversation this page exists to support.
You buy a size and you know what it costs. Use a fraction of it or all of it, the bill is the same. Nobody wants to pay one dollar in January and forty in February for a bakery website.
Developers and heavy users can switch the same pod to measured pricing and pay for what they actually consume. No new product, no migration, no data move. It is a billing setting, not a platform.
You can switch back. Most businesses never turn it on, and most developers never turn it off.
The reason people fear usage pricing is not the cost, it is the ambush. Your assistant watches the pod and tells you in plain language before anything changes, so a bigger month is a decision you made rather than a shock you discovered.
You can also set a ceiling you do not want to cross. Real growth gets a heads up. One unusually good day gets absorbed, because a mention on the news is not a new business, it is a Tuesday.
Growth in traffic is growth in the business. Paying a little more at fifty thousand visitors a month is alignment, not punishment. What was punishment was the old model, where getting bigger meant a migration weekend and a new invoice for the same website.
The model above is the part that is decided. The numbers underneath it are not, and pretending otherwise would be the fastest way to lose a serious conversation.
The cost floor for one pod is now built from published container rates rather than guessed, and the growth model is interactive: running the numbers. Two findings worth knowing before you read it.
One position that is already settled: this should not try to be the cheapest option on the market. Competing on price against operators with a structurally lower cost base is a losing game, and it is not what the product is for. That argument is in the open questions alongside the rest of what is unresolved.
Abuse handling, identity verification, payment processing, network capacity, peering and out of hours support are the expensive, unglamorous foundations underneath any number on this page. An operator that already runs them has a cost base a startup would spend three years rebuilding.
Read the case for why now, the technical page for what is actually under it, and the open questions for what is not resolved.