Why your cloud bill is unpredictable, and which charges to look for
Traffic spikes should not produce invoice spikes. Egress fees, per-visit metering and per-execution billing are the three line items that turn a fixed cost into a variable one.
In short
Unpredictable hosting bills usually come from three metered charges: bandwidth egress, monthly visit allowances with overage fees, and per-execution automation billing. All three are avoidable by choosing plans not metered on those axes.
A predictable hosting bill is a fixed number arriving on the same day each month. Plenty of infrastructure is not sold that way, and the difference rarely becomes visible until something good happens to your traffic.
Three charges do most of the damage. All three are disclosed, none are hidden, and all three are easy to miss when comparing plans because none appear in the headline price.
Egress: paying for your own traffic to leave
Bandwidth into a cloud platform is typically free. Bandwidth out is charged per gigabyte, and that charge is called egress.
For a brochure site it is negligible. For anything serving images, video, downloads or a busy API it becomes the largest line on the invoice, and it scales with exactly the thing you were hoping for — more visitors. A post that does unexpectedly well produces a bill that does unexpectedly well too.
The second-order problem is that egress makes leaving expensive. Moving several terabytes off a platform means paying to extract your own data, which is why regulators have taken an interest in the practice. Check the egress rate even if your traffic is small today.
Visit metering: paying per person
Managed WordPress platforms commonly meter by monthly visits rather than resources. The plan includes an allowance, and exceeding it triggers an overage charge per thousand visits or an automatic bump to the next tier.
The logic is defensible — visits correlate with load better than disk space does. The problem is that visits are the least predictable number in your business and the one you control least. A newsletter mention, a seasonal peak, or a bot ignoring robots.txt all consume the allowance identically.
It also creates an awkward incentive. You end up mildly hoping for less traffic near the end of a billing period, which is not a thought a hosting plan should ever produce.
Per-execution billing on automation
Workflow automation platforms usually charge per task, per execution or per operation. At small volumes this is cheap and entirely reasonable.
It stops being reasonable at the point automation starts working. A workflow firing on every order, every form submission or every webhook scales its cost linearly with the success of the thing it automates. Teams routinely find they have built something valuable that costs more to run each month than the process it replaced.
The alternative is self-hosting the automation engine on infrastructure you already pay for, where the marginal cost of an execution is zero. That is a real trade — you take on the operational burden — but for a workflow running thousands of times a month the arithmetic is not close.
What predictable looks like
Our plans are not metered on any of those three axes. Bandwidth is unmetered for normal website use on hosting plans, with no per-gigabyte egress charge. VPS tiers carry a transfer allowance from 4 TB to 32 TB, which ordinary application traffic sits well inside. Nothing is metered by visits, so a traffic spike does not produce an invoice.
For automation, managed n8n starts at €19 a month on dedicated resources with no per-execution billing. A workflow that runs ten times a month and one that runs ten thousand times cost the same, because the cost is the server rather than the event.
The trade-off is honest. A fixed plan means paying for headroom you do not always use, and at genuinely large scale a metered platform with a global edge will outperform us. What you get instead is a number you can budget, and no relationship between your success and your bill.
Three questions for any provider
What is the egress charge per gigabyte, and what happens if I move my data out? A provider with no egress fee says so immediately.
Is anything metered by visits, requests or executions, and what is the overage rate? Ask for the rate, not just whether an allowance exists.
What is the maximum this plan can cost me in a month? If there is no answer, it is variable-cost infrastructure whatever the headline price suggests. That may still be the right choice — but it should be a choice you made deliberately.