A Bill That Does Not Move

Metered hosting charges per request, per gigabyte and per hour, which means the invoice can grow in a month when nothing was released. Nobody can budget against that, and nobody can explain it afterwards either.

A fixed-price server replaces the metering with one published monthly amount, sized once rather than scaled automatically. Traffic no longer changes the total, and the staging copy shares the machine instead of doubling it.

The number can then be put in a budget a year ahead and still be right, which is the part that actually matters to a business that is not an IT company.

One Window, Not a Project

Migrations get quoted in quarters because they are usually attempted in pieces, and every piece left behind keeps its own bill running. A database on a managed service outlives the move that was supposed to end it.

Everything goes in one planned window instead: DNS authority, directory sign-in with its redirect addresses, the databases, the deployment pipelines, and the checks that prove the result. Three separate estates were moved this way inside sixteen days, with no reported data loss.

What follows is a short, known list rather than an emergency: a mail port, a stale endpoint, a missing header on a staging hostname.

Free to Move Again

The first move is not the point. Any provider can raise its prices, and in June 2026 the independent one used here did exactly that, more than doubling the plan this practice runs.

That is an argument for portability rather than against it. The same build runs on a large provider where its managed services earn their price, on an independent European host where a predictable bill matters more, or on hardware the business already owns.

Switching is a configuration change rather than a rebuild, so the decision stays reversible and stays cheap to revisit. Nothing has to be rewritten to take the comparison seriously a second time.

If the bill outgrows the value again, the answer is a maintenance window rather than another project, and the business is the one choosing when to open it.

3 estates
moved off metered hosting inside sixteen days, zero reported data loss
EUR 35.49
published monthly price of one server carrying a whole estate
0
extra euros for the staging copy, because both slots share one machine
20 TB
traffic included, against per-gigabyte metering once a free tier ends

Turning the Hosting Bill Into a Number You Choose

Find Out What You Are Paying For 2 steps
01

Start With the Bill, Not the Architecture

Metered hosting prices requests, gigabytes stored, gigabytes sent and hours run, each as its own line. So the invoice moves in a month when nobody shipped anything, and no one in the business can say which line grew or why. Read the actual line items first and group them into compute, storage, traffic and managed services. That grouping is the whole diagnosis.
02

An Alert Usually Decides This, Not a Meeting

Nobody schedules a hosting review. Instead, budget alerts fire earlier in the month than they should, across several environments at once, with no release to explain it. That is the moment the question becomes real. In the delivered work the alerts fired unusually early across three environments on 8 July 2026, and the decision to move was taken the same week.
Fix the Monthly Number 3 steps
03

Price Both Targets From Published Rates

A comparison is worth nothing unless its shape is stated. At West Europe list prices, one Azure App Service Premium v3 P1v3 instance on Linux is EUR 0.1564 per hour, about EUR 114 a month, and the same plan on Windows is EUR 0.2970 per hour, about EUR 217. A four-core, eight-gigabyte server at an independent European provider publishes at EUR 35.49.
04

Count the Traffic as Its Own Bill

Egress is the line that surprises people, because it is charged on visitors rather than on anything the business controls. West Europe list pricing gives the first hundred gigabytes a month free, then EUR 0.0703 per gigabyte, so a terabyte of traffic adds about EUR 65 on top of compute. The fixed-price server includes at least twenty terabytes in its EU locations.
05

Put the Staging Copy on the Same Machine

Staging environments get cut first when hosting is metered, because each one doubles a bill nobody can predict. Run two slots on one server instead: one serving customers, one carrying the next version, each with its own hostnames and its own configuration file. The candidate copy then adds no line to the invoice, which removes the only real argument for not having one.
Move It in One Window 2 steps
06

Move the Whole Estate, Not the Easy Half

A partial migration leaves the expensive parts behind: a database still on a managed service, a pipeline still publishing to the old platform, a sign-in registration nobody touches. Move DNS authority, directory sign-in with its redirect addresses, the databases, the pipelines and the verification together, in one window. Three separate estates were moved this way inside sixteen days, with no reported data loss.
07

Expect a Short List of Things That Break

A cutover is finished when the list after it is closed, not when the traffic switches. The recurring items are known and worked in the same window: outgoing mail refused on one port and moved to another, configuration pointing at endpoints that no longer exist, and staging hostnames missing the header that keeps them out of search results. None is a surprise any more.
Stay Free to Move Again 2 steps
08

A Fixed Price Is Not a Frozen Price

Independent providers raise prices too. On 15 June 2026 the plans this practice runs went up sharply, the four-core plan from EUR 13.99 to EUR 35.49 a month. That is the argument for portability rather than against it. What matters is not that one provider stays cheapest forever, but that leaving is a maintenance window rather than a rebuild, whoever moves their prices next.
09

Hand It Over Without Hiring a Specialist

What runs is ordinary containers behind a shared reverse proxy that renews its own certificates, described in files any qualified developer reads. Server administration can be handed to the business, with database access scoped to its own data and sign-in keys rather than passwords. DNS authority moves with it while the registrar stays where it is, so nothing depends on one person's account.

Frequently Asked Questions

What does hosting actually cost per month?
It depends on the shape of the comparison, so here is one stated plainly. At West Europe list prices an Azure App Service Premium v3 P1v3 instance is about EUR 114 a month on Linux and about EUR 217 on Windows, before database and traffic. A four-core, eight-gigabyte server at an independent European provider publishes at EUR 35.49, carrying several containers at once.
Is an independent European host always the cheaper answer?
No, and it should not be presented that way. A large provider earns its price where its managed services genuinely replace work you would otherwise do, and where compliance or procurement requires it. The independent host wins where a predictable monthly bill matters more than managed extras. The point is that the choice stays open rather than being settled once by the first architecture.
What happens if the cheaper provider raises its price?
It already has. On 15 June 2026 the plans used here went up sharply, the four-core plan from EUR 13.99 to EUR 35.49 a month. Nothing about that changes the approach, because the application was never tied to that provider. Moving it is a configuration change in a maintenance window, so a price rise triggers a comparison rather than a rebuild.
Do we need someone on staff to run this?
No specialist role is created by it. What runs is ordinary containers behind a shared reverse proxy that renews its own certificates, described in files any qualified developer can read and change. Administration can be handed to your side with database access scoped to your own data, and DNS authority moves with the estate while your registrar stays exactly where it is.