This article covers seven current options. It is not a benchmark ranking: we did not deploy the same site and traffic test on every platform, so the order does not claim that number three is faster than number five. Product details and prices were checked against official sources on July 25, 2026.

Disclosure: QDE publishes this comparison and appears first. We sell cPanel shared hosting, so our commercial interest should be visible before the recommendations, not hidden in the conclusion. The other six providers are included because they sell a cPanel hosting product to new customers and offer a useful range of contract terms, locations, support models, and resource limits.

What "cPanel hosting" means in this comparison

cPanel is the account-level interface used to manage files, domains, databases, email, PHP settings, certificates, and applications on a Linux hosting server. The provider runs WHM and the underlying server. You receive a restricted cPanel account.

The cPanel logo does not make two hosting plans equivalent. A provider can disable individual interfaces, choose different backup software, impose its own CPU and memory limits, and decide whether migrations or restores are included. Bluehost places cPanel behind the Bluehost Portal. Hosting.com sells it as a separate product from standard web hosting. GoDaddy packages it inside a broader account dashboard. The familiar cPanel screen is only one layer of the service.

Backups need particularly careful wording. cPanel can generate a full account archive, but its own backup documentation says customers cannot automatically restore a full backup from the cPanel interface. That normally requires the destination host or someone with WHM access. cPanel's Transfer Tool is also a WHM administrator function, not a button available to every shared-hosting customer.

How the seven providers compare

Promotional prices are difficult to normalize. Some require one, two, or three years of advance payment, while others bill monthly. Taxes, region, free-domain terms, email, and renewal prices also differ. The table records the pricing pattern that matters most, but the checkout total is the number to compare.

1. QDE

QDE shared hosting runs in Amsterdam and uses cPanel on every plan. Starter costs €2.95 per month, Standard €4.95, and Premium €9.95. Those are monthly prices rather than short introductory rates tied to a multi-year prepayment.

Every account receives a dedicated IPv4 address, daily offsite backups, free TLS certificates, MariaDB with phpMyAdmin, and a selectable PHP version from 8.2 through 8.5 for each site. The network has a 10 Gbps shared uplink. "Shared" matters: 10 Gbps describes the connected port, not bandwidth reserved for one hosting account.

The service is intended for PHP, WordPress, and static sites. Each account can use up to 512 MB of RAM. A project that needs root access, Docker, system packages, or an unrestricted Node.js or Python environment belongs on a VPS instead.

QDE accepts iDEAL, PayPal, credit cards, Bitcoin, Litecoin, USDT, and Monero. You can inspect the interface before buying through the QDE cPanel demo with username demo and password I8.aB?*+AFx~t{w-.

Best fit: a site owner who wants cPanel on Netherlands infrastructure, a dedicated IPv4 address, and month-to-month billing without a renewal jump.

Check before ordering: the 512 MB account limit and PHP-focused environment are designed for conventional websites, not custom server software.

2. Bluehost

Bluehost is the longest-running host on the current WordPress.org hosting recommendation page. Its current Starter shared plan supports up to 10 websites with 10 GB of NVMe storage. It also includes a first-year domain, Let's Encrypt certificates, a WordPress migration tool, CDN access, and a 30-day hosting refund period.

cPanel is present, but Bluehost no longer makes it the center of every task. Its June 2026 cPanel access guide says most functions are available in the Bluehost Portal, with a cPanel button for database, email, FTP, and other advanced settings. Bluehost Cloud does not include cPanel at all.

The regular rate deserves as much attention as the signup offer. Bluehost's current shared-hosting price sheet lists Starter renewal at $15.99 per month on a monthly term, $11.99 per month equivalent for 12 months, or $9.99 per month equivalent for 36 months. Longer terms reduce the monthly equivalent but require more money up front.

Best fit: a new WordPress owner who values Bluehost's setup flow, WordPress tooling, and large support library, while still wanting cPanel available for traditional hosting tasks.

Check before ordering: confirm the product says shared or web hosting if cPanel is mandatory. Bluehost Cloud uses a different management setup.

3. HostGator

HostGator shared hosting still provides cPanel. Its current shared-hosting feature table lists Hatchling, Business, and Pro plans with 10, 50, and 100 websites respectively. Storage ranges from 10 GB to 100 GB, and every tier lists SSL, a CDN, a migration tool, managed WordPress updates, and a 30-day money-back period.

There is an awkward documentation mismatch. The feature table uses Hatchling, Business, and Pro, but HostGator's published renewal price chart still lists Hatchling, Baby, and Business. That chart puts Hatchling at $17.59 for one month, $13.19 per month equivalent for a one-year renewal, and $10.99 per month equivalent for three years.

Treat the cart and renewal notice as authoritative for the exact product you select. Saving a copy of the checkout summary is sensible when the public plan names do not line up cleanly.

HostGator and Bluehost are not independent corporate groups. HostGator states that it is an indirect subsidiary of Newfold Digital, and Bluehost lists Newfold Digital as its parent company. Their account portals, promotions, and feature development can still differ, but buyers comparing corporate concentration should know the connection.

Best fit: a first-time site owner looking for an established cPanel host with a low promotional entry point and a path to larger hosting products.

Check before ordering: verify the plan name, website limit, renewal term, and regular price in the cart because HostGator's current comparison and renewal pages do not fully agree.

4. InMotion Hosting

InMotion Hosting shared plans pair cPanel with NVMe storage and more generous published site limits than most entry plans in this list. Launch supports two websites and 100 GB of storage. Power supports 10 websites and 200 GB. Pro supports 40 websites, 300 GB, 2 vCPU cores, 4 GB of RAM, a dedicated IP address, and WHM access for up to four client cPanel accounts.

InMotion also includes tools that are unusual on basic shared hosting. Its current page lists SSH, Git, Node.js, Python, Ruby, WP-CLI, MySQL, and PostgreSQL. These remain managed shared accounts without root access, but they cover more development workflows than a PHP-only plan.

The long refund window is another practical difference. InMotion advertises a 90-day full money-back guarantee and a free migration using one cPanel or WordPress backup. Launch promotions start around $4.79 or $4.99 per month equivalent on prepaid terms, with published renewal rates around $13.99 to $14.99 for those terms. Month-to-month pricing is higher.

Backups should not be inferred from the refund period or migration offer. The plan table describes Backup Manager as available, so check whether the backup schedule you want is included or added separately.

Best fit: a small agency or developer who wants cPanel, substantial storage, SSH, and modern runtime tools without administering a VPS.

Check before ordering: compare the prepaid total, renewal rate, and backup option. Launch support is chat and ticket only, while phone support starts on higher tiers.

5. Hosting.com, formerly A2 Hosting

A2 Hosting became Hosting.com in April 2025, not 2026. The company announced the rebrand after its acquisition by World Host Group, while A2 Hosting, LLC remains the legal company trading under the Hosting.com name.

The product split has since changed. Standard web hosting now uses the Hosting.com panel. Customers who specifically want cPanel must choose Pro cPanel Hosting. That dedicated line includes the full cPanel interface, LiteSpeed on NVMe storage, MariaDB, Softaculous, domain email, daily backups with 30 days of restore points, free SSL, and migration assistance. Hosting.com advertises a 30-day money-back guarantee for new shared-hosting purchases.

This is an important distinction for old A2 comparisons. A review that says "A2 Hosting includes cPanel" may describe an existing account or an earlier lineup. In 2026, the product name at checkout decides which panel a new customer receives.

Best fit: a cPanel user moving from another host who wants a managed LiteSpeed stack and provider-assisted backup-and-restore migration.

Check before ordering: select Pro cPanel Hosting explicitly. The cheaper or more prominent standard web-hosting path may use Hosting.com's own control panel instead.

6. Namecheap

Namecheap shared hosting uses cPanel and Softaculous across its Stellar, Stellar Plus, and Stellar Business plans. The entry Stellar plan supports three websites and includes 20 GB of SSD storage. It is advertised at $1.91 per month for the first year, billed as $22.92, and currently renews at $55.88 per year. A month-to-month renewal is $5.88.

Those renewal numbers changed on May 19, 2026. Namecheap published the new shared-hosting renewal table rather than making customers reconstruct it from a discount percentage. Stellar Plus renews at $85.44 per year and Stellar Business at $128.88.

Backup coverage differs by tier. Namecheap says Stellar Plus and Business receive cPanel AutoBackup with daily, weekly, and monthly restore points. The hosting policy describes a less extensive internal schedule for entry-level Stellar accounts. The current refund policy gives first-time shared-hosting accounts 30 days.

Namecheap also publishes shared-account resource limits in its hosting acceptable-use policy. Physical memory is 1 GB on a standard shared account and 2 GB on Stellar Plus and Stellar Business, with separate CPU, process, and I/O limits. That transparency makes it easier to judge whether a busy plugin stack still belongs on shared hosting.

Best fit: a Namecheap domain customer, personal site, or small business that wants inexpensive cPanel hosting and one account for domains and hosting.

Check before ordering: entry-level backups are not the same as the AutoBackup policy on Plus and Business, and the free standard SSL offer has a one-year term.

7. GoDaddy

GoDaddy Web Hosting uses cPanel on its Linux shared plans. Current regional product pages list NVMe storage, AutoSSL, daily account backups, unmetered bandwidth, CloudLinux resource controls, a 99.9% uptime promise, and an automated migration tool. The higher Web Hosting Plus range offers guaranteed processing and memory resources for sites that have outgrown ordinary shared allocation.

GoDaddy's plan names, prices, included email, and SSL terms vary by country. For example, current product pages in some markets list Starter, Economy, Deluxe, and Ultimate, while older comparison material still refers to Maximum. Use the localized checkout for the country that will own and pay for the account.

The refund wording also deserves a direct look. The hosting page advertises 30 days, while GoDaddy's May 2026 refund policy gives annual plans 30 days and monthly plans only 48 hours under its standard terms. The policy also contains product-specific exceptions, so a monthly purchase should not be treated as a 30-day trial without checking the applicable regional terms.

Best fit: a small business that already uses GoDaddy for domains and prefers to keep hosting, billing, and account support with the same large vendor.

Check before ordering: compare the localized renewal price, SSL duration, mailbox terms, refund window, and site limit. They are not uniform across markets.

What to compare before choosing

The word "cPanel" answers only the interface question. These details usually matter more after the first week:

1. The exact product: Bluehost Cloud has no cPanel, and Hosting.com's standard web hosting uses its own panel. Product families can mix control panels.
2. The full first invoice and renewal: multiply the monthly equivalent by the prepaid term, add tax and domain costs, then record the regular renewal price.
3. CPU, memory, processes, and I/O: "unmetered bandwidth" says little about how many PHP workers or concurrent requests the account can handle.
4. Backup frequency and restore method: check retention, offsite storage, database and mailbox coverage, self-service restore, and any restore fee.
5. Email and SSL after year one: a free first-year mailbox or certificate can become a separate renewal charge.
6. Migration scope: ask whether the provider moves files only or also transfers databases, mailboxes, DNS zones, cron jobs, certificates, and account settings.
7. Server location and support hours: a familiar panel does not shorten network distance or guarantee that an experienced technician is available when the site fails.

Take screenshots of the product summary and renewal terms before paying. Hosting pages change more often than most buyers revisit them.

When a VPS is the better answer

cPanel shared hosting is usually the simpler choice for WordPress and conventional PHP applications. The provider maintains the operating system, web server, mail stack, and cPanel license. You work inside the account limits.

A VPS becomes the better fit when you need root access, Docker, custom system services, unusual extensions, a private network layout, or predictable server-level resources. Some shared hosts expose Node.js or Python tools, as InMotion does, but that is not the same as controlling the runtime and operating system.

Running cPanel on a VPS also changes the economics. The cPanel license may cost extra, and you remain responsible for administration unless the VPS is explicitly managed. Our shared hosting vs VPS comparison covers that boundary in more detail. The companion article on whether cPanel is still the best control panel in 2026 compares cPanel with Plesk, CloudPanel, HestiaCP, CyberPanel, and DirectAdmin.

Which provider should you shortlist?

QDE is the most direct fit here for monthly EU cPanel hosting with a dedicated IPv4 address. Bluehost has the clearest WordPress-first onboarding, but cPanel sits behind its portal and is absent from Bluehost Cloud. HostGator remains a promotional-price option, provided you verify the current plan and renewal table.

InMotion is the strongest starting point for agencies and developers who want SSH, modern runtime tools, larger storage allocations, and a long refund period. Hosting.com is worth considering for LiteSpeed and cPanel migration, but only through its separate Pro cPanel Hosting product. Namecheap is attractive for inexpensive small sites and existing domain customers. GoDaddy suits businesses that value having one vendor for domains and hosting more than having the simplest pricing sheet.

No provider wins every category. Pick two that match the site, compare their final checkout and renewal totals, then ask both the same questions about backups, resource limits, migration, and support.

Want a month-to-month cPanel account in Amsterdam, or help deciding whether your application needs a VPS instead? Contact the QDE team with the sites, mailboxes, and software you plan to run.

Frequently asked questions about cPanel web hosting

Is cPanel hosting still worth it in 2026?

Yes, when you want a familiar Linux hosting interface and expect to move between conventional shared hosts. The panel is mature and widely documented. It is less important than the provider's resource limits, backups, support, and renewal terms, and it does not suit applications that need root access or a custom server stack.

Does every plan from these providers include cPanel?

No. Bluehost Cloud does not include cPanel. Hosting.com uses its own panel for standard web hosting and sells cPanel through a separate Pro cPanel Hosting product. VPS and dedicated plans from several providers may also price the cPanel license separately. Check the exact product, not just the brand.

Can I move a full cPanel account to another provider?

Usually, but the destination host often has to perform the full restore through WHM. A customer can create and download a full account backup when the host enables that interface, but cPanel does not give ordinary account users an automatic full-backup restore button. Ask the new provider what its migration includes and test mail, DNS, cron jobs, databases, and certificates after the move.

Which cPanel host is the cheapest?

That changes with promotions, terms, taxes, and regions. Namecheap displayed the lowest first-year monthly equivalent in this group on July 25, 2026, but it requires annual prepayment and renews at a higher rate. QDE starts at €2.95 per month with monthly billing and no introductory jump. Compare the total over the period you expect to stay, not the largest sale number.

What does QDE cPanel shared hosting include?

Every QDE shared plan includes cPanel, a dedicated IPv4 address, daily offsite backups, MariaDB with phpMyAdmin, TLS certificates, WordPress management, and per-site PHP selection from 8.2 through 8.5. Plans are billed monthly, include a 99.9% uptime SLA, and have a 14-day money-back guarantee under the current terms.

This article covers seven viable choices for different needs. It is not a laboratory speed ranking: we did not deploy the same site on all seven platforms, so we will not pretend that a provider is "40% faster" based on its own marketing. The provider facts and advertised prices below were checked against official pages on July 25, 2026.

Disclosure: QDE publishes this comparison and is included in it. We put QDE first so that commercial interest is visible rather than tucked away at the bottom. The other six providers were selected because they sell an active Netherlands-hosted shared hosting product, publish enough detail to compare, and represent a useful range of panels, contract terms, and service models. Their order is not a claim that number four is objectively faster than number five.

What Netherlands-based hosting does, and does not, tell you

A server closer to most of your visitors can reduce the minimum network round-trip time. That helps, but location alone does not determine page-load time. Application code, caching, database work, image weight, a CDN, and the route between the visitor's ISP and the host can easily matter more.

Amsterdam is home to AMS-IX, one of the world's largest internet traffic hubs. That gives Dutch networks access to a strong interconnection market. It does not mean every host in the Netherlands peers directly at AMS-IX or uses the same routes. Check the provider's own network information or Looking Glass instead of treating a Dutch address as proof of identical connectivity. Our page on EU-based infrastructure explains that distinction in more detail.

Data residency needs the same careful wording. Keeping the hosting leg inside the European Economic Area can avoid an international transfer for that part of the service. The European Commission's transfer guidance explains the additional safeguards that can apply when personal data leaves the EEA.

None of that makes a website GDPR-compliant automatically. You still need a lawful basis, suitable security, a processor agreement where required, retention rules, and correct handling of analytics, forms, cookies, and user requests.

The seven providers at a glance

The price column records the advertised pattern, not a normalized total cost. Contract length, advance payment, VAT treatment, domain charges, and optional email differ, so compare the full checkout amount before ordering.

1. QDE

QDE shared hosting runs on QDE's own Amsterdam infrastructure and uses cPanel. The Starter plan is €2.95 per month with monthly billing rather than a teaser rate tied to a long initial term. Every plan includes a dedicated IPv4 address, daily offsite backups, a 99.9% uptime SLA, a 14-day money-back guarantee, and a choice of PHP 8.2 through 8.5 per site. Payments include iDEAL, PayPal, credit cards, and cryptocurrency.

The network is the same Amsterdam platform used for QDE's VPS service, with a 10 Gbps shared uplink and AMS-IX peering. "Shared" matters here: 10 Gbps describes the connected port, not throughput reserved for one hosting account.

The limit is what the shared tier is designed to run. It supports PHP and static sites, and each hosting account can use up to 512 MB of RAM. Node.js, Python, Docker, custom system software, and root access require a VPS instead.

Best fit: a site owner who wants familiar cPanel management, a dedicated IPv4 address, and predictable monthly billing on Dutch infrastructure.

2. TransIP

TransIP's current web hosting plans use its own control panel and store data across two Dutch availability zones: Amsterdam and Delft/Alblasserdam. The entry plan provides one website, 20 GB of storage, five 2 GB mailboxes, and a regular price of €9.99 per month. The advertised €1 rate applies to the first three months.

Backup detail is better than the one-word "automatic" found on many pricing tables. TransIP's web hosting backup documentation says Basic keeps restore points for 10 days, while larger plans retain 14 or 30 days. File snapshots are hourly for the most recent day and daily after that; databases are backed up daily. Email is not included in the same self-service restore flow.

One contract detail deserves attention. TransIP's availability policy gives its VPS product a direct uptime guarantee, but classifies web hosting among the other services without one. Compensation may apply when one of those services is unavailable for more than two hours.

Best fit: developers and small businesses who prefer TransIP's integrated Dutch platform and may later add VPS or public cloud services, and who do not need cPanel or DirectAdmin familiarity.

3. Hostnet

Hostnet web hosting is managed through Mijn Hostnet, not cPanel. Its Lite plan advertises €4.99 per month during the promotional period and a normal price of €9.99, excluding VAT. The product page lists daily automatic backups for the website and mailboxes, free Let's Encrypt wildcard certificates, SSD-backed cluster hosting, and support seven days a week.

Hostnet says its green data centers are in Amsterdam. Its own help material also shows that files, PHP settings, and email are managed through Mijn Hostnet. That can be straightforward for a first-time owner, but it is a provider-specific workflow rather than a portable cPanel account.

The promotional price applies to the first contract period. Hostnet's current terms summary says renewal is at the normal rate and cancellation must arrive no later than one month before the contract ends.

Best fit: a Dutch small business that values a broad domain, email, website, and managed-service catalog more than using a standard third-party control panel.

4. Vimexx

Vimexx's Netherlands web hosting has the lowest displayed introductory price in this group: €0.45 per month for Basic, followed by a €2.99 renewal price. Basic includes 8 GB of SSD storage, 100 GB of monthly traffic, DirectAdmin, free SSL, and at most one backup per day retained for seven days.

The differences between tiers are substantial. Plus advertises up to seven backups per day retained for 60 days, 100 GB of storage, active DDoS protection, and a support SLA, while Basic lists no support SLA or DDoS protection. Compare the tier you will actually buy rather than carrying the Plus feature list down to the cheapest plan.

Vimexx says its infrastructure is housed in BIT data centers in Ede and describes Dronten as a second server location. It documents DirectAdmin as its web hosting panel. The standard site is primarily Dutch, which may be a practical consideration for an international team.

Best fit: price-sensitive Dutch-speaking users who are comfortable with DirectAdmin and willing to inspect the renewal price and tier-specific backup and support limits.

5. Antagonist

Antagonist publishes unusually clear resource and backup figures. Its hosting comparison assigns the Slim plan one CPU core, 1 GB of RAM, 50 GB of SSD storage, and 28 restore points spanning two weeks. Plus and Pro increase both the isolated resources and the backup history. All three use DirectAdmin and include managed server operation, SSL, SSH, Installatron, and a 30-day money-back period.

Slim costs €5.55 per month for the first year and renews at €9.99 per month. Antagonist states that these prices exclude VAT and are paid in advance. That is less eye-catching than a €0.45 teaser, but the published CPU, RAM, backup, and renewal figures make the trade easier to evaluate.

Antagonist's location documentation places its servers in the Netherlands, at Previder in Hengelo. The company focuses heavily on managed web and reseller hosting; it is not the natural choice if the next step is an unmanaged root-access VPS.

Best fit: a site owner who wants a managed DirectAdmin environment, explicit account resources, and frequent self-service restore points.

6. Yourhosting

Yourhosting's current web hosting lineup combines Dutch-hosted service with installation help, migration help, daily automatic backups, and optional service bundles. Its Basic plan advertises €0.99 per month for six months when a 12-month term is paid in advance; the page shows €14.99 as the regular monthly price for that term. A 36-month selection lowers the displayed regular monthly equivalent but requires a much longer commitment.

Yourhosting uses Plesk for its main hosting environment. Its Plesk documentation covers files, mail, databases, phpMyAdmin, and WordPress management. This is useful if you already know Plesk or want a standard panel without cPanel.

Yourhosting puts more guided help around the hosting account, including installation, migration, callback, and webmaster options on selected plans. Check which services are included in the exact tier and which become paid extras later.

Best fit: a business that prefers Plesk and values onboarding and optional hands-on help enough to accept annual or multi-year billing.

7. Versio

Versio web hosting runs on a Netherlands-based high-availability cloud with NVMe storage and redundant SAN storage. The current Start Web, Complete Web, and Max Web plans cover two, five, or ten websites and retain backups for 7, 14, or 60 days respectively.

The advertised €0.99 price applies for the first three months when the selected term is paid in advance. The later monthly equivalent varies between the one-, two-, and three-year options, so the checkout total is more useful than the banner price. Business email is currently shown as an add-on rather than an included mailbox allowance.

All web and reseller hosting customers use DirectAdmin. Versio also sells reseller hosting and VPS plans, which gives agencies a route to separate client accounts or move beyond shared hosting without immediately changing providers.

Best fit: users managing several sites who want DirectAdmin and a possible path to reseller hosting, provided they account for the term length and separate email cost.

What to compare before signing up

Seven product pages can still hide seven different definitions of "included." Check these items against the exact tier in your cart:

• Total initial and renewal cost: Multiply the post-promotion monthly equivalent by the committed term, then add VAT, the domain, email, migration, and any required service bundle.
• Control panel and migration format: A cPanel, Plesk, or DirectAdmin backup may shorten a move between compatible systems. A proprietary panel usually means moving files, databases, DNS, cron jobs, and mail through a provider-specific process.
• Backup scope: Confirm whether files, databases, and email are all protected, how often each is captured, how long restore points remain, and whether self-service restores cost extra. Keep an independent copy for data you cannot afford to lose.
• Resource limits: Storage is only one limit. CPU, RAM, processes, inodes, database size, outgoing mail, and the number of sites often determine whether a real workload fits.
• Uptime wording: "High availability" and monitoring are architecture claims. An SLA states a threshold, exclusions, claim procedure, and remedy. They are not interchangeable.
• Data location and contracts: Ask where the live data and backups reside, which legal entity signs the agreement, and whether a suitable processor agreement is available. A Dutch company address alone does not answer those questions.

Which Dutch host should you choose?

Choose QDE if you specifically want monthly cPanel hosting, a dedicated IPv4 address, and a clean path to an Amsterdam VPS. Choose TransIP for a broad Dutch infrastructure portfolio and its proprietary panel, or Hostnet for a custom environment with a larger menu of guided business services.

Vimexx is the price-led DirectAdmin option, but its entry tier is materially different from Plus. Antagonist costs more at entry and publishes clearer account-resource and restore-point figures. Yourhosting is the Plesk choice in this group, with more onboarding services and longer billing options. Versio fits multi-site or reseller-oriented users who are comfortable adding email separately.

If your shortlist contains shared hosting and a server you would manage yourself, read shared hosting vs. VPS hosting before comparing plan names. Root access and maintenance responsibility will matter more than a small monthly price difference.

If QDE's monthly cPanel model fits your requirements, review the Amsterdam shared hosting plans and their exact account limits before ordering.

Frequently asked questions about Dutch shared hosting

Does Dutch shared hosting come with cPanel?

It depends on the provider. QDE uses cPanel; Vimexx, Antagonist, and Versio use DirectAdmin; Yourhosting uses Plesk; and TransIP and Hostnet use their own management environments. Check the migration path as well as the interface, especially if you already have a full-account backup from another panel.

Do Netherlands shared hosting plans include a dedicated IP address?

Many shared hosting products use an address across multiple accounts, and several providers do not promise a dedicated address on their public plan pages. QDE includes one dedicated IPv4 address with every shared hosting account. A dedicated IP is not normally required for HTTPS because modern clients support SNI, but it can be useful for IP allowlists or isolating address reputation.

How fast is Dutch shared hosting?

There is no honest provider-wide number. A 10 Gbps port describes network capacity at one point in the system; it is not a guarantee that one shared account will transfer at 10 Gbps. QDE lists a 10 Gbps shared uplink, while other providers describe their own caching and network designs. Test the actual site, its cache behavior, time to first byte, error rate, and latency from the visitor regions that matter to you.

What backup, uptime, and refund terms should I look for?

Look for separate answers. A useful backup policy names frequency, retention, covered data, storage location, and restore procedure. An SLA names an availability target and remedy. A money-back guarantee defines how long you can cancel and what charges are excluded. One does not replace either of the others.

QDE publishes daily offsite backups, a 99.9% uptime SLA, and a 14-day money-back guarantee. Other providers in this comparison publish different combinations, including longer restore histories or 30-day refund windows, so match the terms to the failure you need to recover from.

When should I move from shared hosting to a VPS?

Move when the application needs root access, custom system packages, long-running services, Docker, Node.js or Python support that the shared plan does not provide, or resource isolation beyond the host's account limits. A VPS also moves operating-system patching, monitoring, and recovery work onto you unless you buy a managed service.

Choose Plesk when supported Windows Server management matters. Consider CloudPanel for a self-managed Linux web or application server that does not need a local mail stack. HestiaCP offers a free all-in-one Linux setup with mail and DNS, while CyberPanel centers its free core on OpenLiteSpeed. DirectAdmin is the lower-priced commercial option worth testing for shared hosting and reselling.

QDE sells cPanel-based shared hosting and unmanaged VPS plans on which customers can install another panel. We therefore have a commercial interest on both sides of this comparison. The useful question is not which dashboard looks nicest. It is which panel matches your tenant model, applications, migration plan, and willingness to administer the server.

A control panel changes operations, not server ownership

A hosting control panel turns common system-administration tasks into web forms and guarded workflows. It can create domains, Unix users, mailboxes, databases, DNS zones, scheduled jobs, backups, and TLS certificates without making the customer edit each service configuration by hand.

That convenience gives the panel considerable access to the machine. Treat it as a privileged management layer: keep the panel and operating system patched, require multi-factor authentication, restrict administrator access where practical, store backups away from the server, and test restores.

A license does not make an unmanaged VPS managed. If you install a panel on an unmanaged server, you still own operating-system updates, firewall policy, mail reputation, capacity planning, monitoring, incident response, and recovery. With managed shared hosting, the provider normally handles that layer and gives each customer a limited panel account. This difference often matters more than the logo in the browser.

Why cPanel remains a strong default

cPanel's roots go back to hosting automation scripts written in 1996. That history produced a deep body of documentation, trained support staff, migration experience, and integrations for billing, reselling, backups, security tools, and PHP applications.

Its two-layer model is particularly well suited to shared hosting:

• WHM gives the server owner or reseller control over packages, accounts, DNS, mail, limits, and server services.
• cPanel gives each customer a separate interface for domains, files, databases, email, certificates, and applications.

That account boundary is one reason providers keep using it. A new support technician is more likely to know cPanel than a younger panel, while customers can move a conventional cPanel backup between participating hosts with less retraining. cPanel's Transfer Tool also covers many cPanel-to-cPanel migrations.

There are limits. cPanel is a Linux product. Its current system requirements cover AlmaLinux, CloudLinux, Rocky Linux, and Ubuntu rather than Windows Server. Its account-based licensing also becomes expensive when a host adds many independent customers.

What cPanel costs in 2026

As of July 25, 2026, the official cPanel Store pricing for 2026 lists these monthly cloud-license rates:

Those are direct Store rates before tax, discounts, or cPanel Partner pricing. They are not necessarily what a hosting provider pays or passes on to a customer.

The scaling effect is easy to miss. At the direct Store rate, a Premier license for 300 accounts works out to $167.99 per month: $69.99 for the first 100 accounts and $98 for the remaining 200. Server cost, support, backups, monitoring, and other software still sit on top.

An account is not the same thing as a domain. One cPanel account may host several domains when its package allows that. Plesk editions, by contrast, are commonly described by domain limits. Compare the way you isolate customers and subscriptions rather than putting the headline account and domain numbers side by side.

For one managed website, the license math may be invisible because the host spreads it across the platform. For a developer running one small VPS, a $29.99 monthly panel can cost more than the server. For a host with hundreds of isolated accounts, per-account growth becomes a budget line that deserves its own forecast.

How the alternatives compare

The table describes products, not management quality. A carefully maintained HestiaCP server is a better choice than a neglected cPanel server. A provider that answers incidents, tests backups, and patches quickly may be worth more than the difference between two panel licenses.

Plesk

Plesk is cPanel's closest commercial peer in this group. Its Web Admin, Web Pro, and Web Host editions use domain-oriented limits and target site owners, agencies, and hosting providers respectively.

Its decisive difference is operating-system support. Plesk's current system requirements cover both Linux distributions and supported Windows Server releases. If an application needs IIS, ASP.NET Framework, or another Windows-specific component, cPanel and the Linux-only alternatives do not solve that requirement.

Plesk offers Git and Docker through extensions, but read the extension limits before treating those features as a complete container platform. For example, Plesk's Docker documentation notes platform, backup, and migration constraints. Root access and a dedicated container workflow may still be the cleaner choice for a container-heavy service.

Plesk's Migrator documentation lists cPanel 11.5 and later as supported sources. That is useful during a move, but it does not make the two products identical. Account layout, subscriptions, extensions, web-server rules, mail, and DNS still need a trial migration and verification.

CloudPanel

CloudPanel Community Edition is free to use. Its current technology stack is aimed at PHP, Node.js, Python, static sites, and reverse-proxy workloads on Nginx, with database and caching components available for application hosting.

The scope is deliberately narrower than cPanel. CloudPanel's own email documentation says that it does not provide an email server and recommends a separate mail service. That is often a sensible design for a developer managing application servers. It is a poor substitute for cPanel when customers expect to create local mailboxes, forwarders, spam rules, and webmail in the same account.

CloudPanel is a good candidate for a small agency or developer who already knows Linux, uses external email, and wants a focused application panel without per-account fees. The operator must still maintain the server. "Free panel" means a zero-dollar license, not zero operating cost.

HestiaCP

HestiaCP is a GPLv3 control panel based on the earlier VestaCP project. It includes web hosting, DNS, Exim and Dovecot mail services, databases, Let's Encrypt certificates, and backups. It also supports PostgreSQL alongside MariaDB or MySQL, which can be useful for a mixed set of small applications.

Its compact scope suits a personal server, a small organization, or an administrator who wants an all-in-one Linux panel without a commercial license. The trade is a smaller plugin, support, and migration ecosystem than cPanel.

Hestia's official backup and restore documentation covers HestiaCP and VestaCP backups. Do not assume a cPanel account archive will restore directly. Budget for a site-by-site migration or a tested third-party process.

CyberPanel

CyberPanel's free core is GPLv3 and uses OpenLiteSpeed. Its core feature and add-on list includes mail, DNS, FTP, databases, SSL management, and WordPress tooling, while some advanced functions are paid.

That makes CyberPanel a practical candidate when OpenLiteSpeed and LSCache for WordPress fit the workload. It also offers an automatic cPanel backup importer, which can shorten a migration. Import is the beginning of the test, not proof that every mailbox, DNS record, cron job, PHP extension, rewrite rule, and certificate arrived correctly.

Check compatibility before moving an Apache site with a large or unusual .htaccess file. OpenLiteSpeed does not behave exactly like Apache in every configuration, and CyberPanel sells additional .htaccess tooling. A benchmark using your plugins, cache state, database, and traffic pattern is more useful than a generic claim that one web stack is faster.

DirectAdmin

DirectAdmin's current retail pricing starts at $5 per month for Personal PLUS, $15 for Lite, and $29 for Standard. The plans differ by account and domain limits, with Standard allowing unlimited accounts and domains under the license terms shown on that page.

DirectAdmin covers the normal shared-hosting stack and supports several web-server configurations. It also documents a cPanel conversion and import process, including known issues and a recommendation to test one account before a bulk move.

It is less ubiquitous than cPanel, but it occupies a useful middle ground: a commercial product and support channel without cPanel's direct Store price. Hosts should still compare billing integrations, backup systems, reseller workflows, staff familiarity, and migration results rather than choosing on license price alone.

A panel name is not a performance benchmark

CloudPanel, CyberPanel, and other lean panels are often advertised as faster than cPanel. The panel can influence the default web server, caching tools, process manager, and background-service footprint, but its name does not determine requests per second.

A fair test keeps these variables under control:

• the same CPU, RAM, storage, operating system, and network;
• the same PHP or application runtime and worker limits;
• the same database version, data set, and buffer configuration;
• identical application code, plugins, cache state, and TLS setup;
• measured latency and error rate at several concurrency levels; and
• enough run time to expose memory pressure, cache misses, and background jobs.

If a panel saves 300 MB of idle memory but lacks the mail, backup, or tenant controls you require, it has not improved the complete hosting system. Conversely, there is little value in paying for a large control-panel ecosystem when one administrator runs three application servers and never uses the reseller or mail features.

Migration tools reduce work, but they do not remove risk

cPanel, Plesk, CyberPanel, and DirectAdmin all provide migration or import paths for at least some source configurations. Coverage differs, and third-party plugins can add state that no generic importer understands. Treat a panel change as a server migration.

Before changing DNS:

1. Inventory domains, aliases, DNS zones, mailboxes, forwarders, cron jobs, databases, users, PHP versions and extensions, TLS certificates, rewrite rules, and backup policies.
2. Export one representative account and import it into a test server.
3. Compare files, database row counts, DNS records, mailbox counts, scheduled jobs, and application behavior.
4. Test the new site through a local hosts-file override before public cutover.
5. Keep the old server unchanged long enough to provide a rollback path.
6. Plan the final database and mail synchronization so writes are not silently lost.
7. After cutover, monitor certificate renewal, mail queues, bounces, background jobs, error logs, and backup completion.

The migration tool should be chosen only after the inventory. A successful progress bar cannot tell you whether a payment webhook, obscure mailbox rule, or nightly cron job still works.

How to choose in 2026

Start with five questions:

1. Who maintains the operating system? If the answer is "the hosting provider," evaluate the complete managed service. If it is you, include patching, monitoring, mail, and recovery time in the panel cost.
2. Do you need local email and DNS? CloudPanel is intentionally lean and has no mail server. cPanel, Plesk, HestiaCP, CyberPanel, and DirectAdmin cover more of the traditional hosting stack.
3. Do you need Windows Server? Choose Plesk from this group. The others are Linux panels.
4. How are tenants separated? Count real customer accounts, subscriptions, and domains under each vendor's license model. The units are not interchangeable.
5. What must migrate? Test the actual importer against a representative account before committing to the destination panel.

cPanel remains the strongest default when a host needs predictable shared-hosting and reseller workflows, customers already know the interface, and the license cost is spread across a managed platform. It is harder to justify on a small self-managed VPS when you only need a web server, database, and certificate automation.

Plesk wins the Windows requirement. CloudPanel wins a narrower free application-server brief. HestiaCP offers a free conventional hosting stack. CyberPanel is worth evaluating for an OpenLiteSpeed-centered WordPress setup. DirectAdmin deserves a test when you want commercial support with lower direct license prices.

Where QDE fits

QDE's shared hosting uses cPanel on our Amsterdam infrastructure. It is intended for PHP, WordPress, and static sites whose owners want the provider to maintain the hosting platform. Each account includes a dedicated IPv4 address, selectable PHP 8.2 through 8.5 per site, MariaDB with phpMyAdmin, and cPanel-based WordPress management.

If you want to inspect the interface first, open the QDE cPanel demo and sign in with username demo and password I8.aB?*+AFx~t{w-.

QDE's unmanaged KVM VPS plans are the better fit when you need root access, Node.js, Python, Docker, a custom web stack, or a control panel of your own choosing. Installing and maintaining that panel remains your responsibility. If that boundary is still unclear, our shared hosting vs VPS guide explains the wider resource, isolation, and administration differences.

Want a managed cPanel account or help deciding whether your workload belongs on a VPS? Contact the QDE team with the applications, domains, and mail requirements you need to run.

Frequently asked questions about cPanel and control panels

Does QDE shared hosting include cPanel?

Yes. Every QDE shared hosting plan includes cPanel, and every account receives a dedicated IPv4 address. The account still uses a shared hosting platform; the IPv4 assignment is exclusive to that account.

Which PHP versions can I use with QDE cPanel hosting?

QDE shared hosting supports PHP 8.2 through 8.5. You can select the version per site, which helps when separate applications have different runtime requirements.

Can I manage databases through cPanel?

Yes. QDE shared hosting includes MariaDB and phpMyAdmin, so you can create databases, manage users, browse tables, and run queries without SSH access.

Is WordPress installation really one click?

"One-click" is industry shorthand. QDE's cPanel WordPress workflow automates the files, database, and initial setup, but you still choose details such as the domain and administrator credentials. The installation normally takes a few clicks rather than a manual database and configuration process.

What if QDE shared hosting is not right for my site?

QDE shared hosting has a 99.9% uptime SLA and a 14-day money-back guarantee under the current hosting terms. Test the service with the real application, plugins, mail flow, and traffic pattern during that period rather than relying only on a feature list.

Two checks matter before you pay for one. First, "dedicated" means that the provider assigns the address only to your account or server. "Static" means that the address is expected to stay the same. Providers often bundle those properties, but they are not identical. Second, a website's dedicated IP may not be the IP that its mail server uses for outbound messages.

What a dedicated IP address is

A dedicated IP address is a public IPv4 or IPv6 address assigned exclusively to one account, server, or customer while that allocation remains active. You can still host several domains of your own on it. The word "dedicated" describes who may use the address, not how many sites you run or whether you own a physical server.

Shared hosting commonly works differently. Many customer accounts can use one public IP, while the web server selects the right site from the hostname in each request. This is efficient and does not stop those sites from using separate domains or certificates.

An account can therefore have a dedicated IP while still sharing the operating system, CPU, RAM, storage, and uplink with other accounts. If you are comparing those wider resource and management differences, read our shared hosting vs VPS hosting guide.

Where a dedicated IP helps

Stable allowlisting, when the address is also static

Partner APIs, corporate firewalls, VPNs, license servers, and remote management rules often allow traffic only from or to approved IP addresses. A predictable address makes those rules much easier to maintain.

The traffic direction matters. A dedicated address assigned to a server is an obvious destination for inbound SSH, RDP, or HTTPS. For a partner that allowlists your source IP, confirm that outbound traffic is translated to the same address. A provider can route inbound traffic to one IP while sending outbound traffic through another gateway.

Ask whether the address will survive reboots, host maintenance, and normal migrations. A dedicated address can still be renumbered under a provider's terms, so use DNS names where the integration supports them.

Email reputation can belong to one sender

A dedicated sending IP separates your IP reputation from other senders. Google's email sender guidelines explain that activity from every sender on a shared IP affects that IP's reputation. With a dedicated sending address, your own complaints, bounces, sending pattern, and list hygiene determine the address history.

This only applies to the sending IP. A dedicated website IP does nothing for deliverability if cPanel, your hosting provider, or a third-party email service sends mail through a different shared relay. Check the Received headers of a delivered message or ask the provider which public IP its SMTP service uses.

The IP is only one part of delivery. As of July 24, 2026, Gmail also requires sender authentication, valid forward and reverse DNS, TLS, and controlled spam rates. A dedicated IP without PTR records, SPF, DKIM, DMARC where required, and sensible sending practices is simply a private way to build a bad reputation.

Address-level incidents have a smaller blast radius

If several unrelated sites or senders share one address, an address-specific blocklist entry, firewall rule, rate limit, or provider mitigation can affect all of them. Exclusive use removes that particular dependency.

This isolation has limits. A large attack can still congest shared infrastructure or trigger controls at a wider prefix or network level. A dedicated IP reduces exposure to events tied to one shared address; it does not turn shared infrastructure into a private network.

Legacy software and IP-based licensing still exist

Some vendor licenses, older applications, partner integrations, and monitoring systems identify a server by IP instead of by hostname or account identity. A dedicated static IP may be the simplest compatible endpoint.

Verify that requirement before choosing a plan. Connecting to a website by raw IP can select the wrong virtual host, and a normal TLS certificate for example.com will not validate when a client connects to https://203.0.113.10/.

Where it does not help

HTTPS no longer requires one

Server Name Indication in RFC 6066 lets a TLS client include the hostname it wants during the handshake. The server can then choose the matching certificate even when several domains use the same underlying IP address.

Modern browsers and web servers support SNI, so ordinary HTTPS is not a reason to buy a dedicated address. Exceptions are limited to legacy clients and unusual configurations that cannot send or process SNI.

A fresh sending IP starts without a reputation

A new dedicated IP has no sending history. Sending a large campaign immediately can cause throttling or junk-folder placement while mailbox providers decide how to treat it. Amazon SES documents the same tradeoff in its shared and dedicated IP comparison: shared pools are ready immediately and suit low-volume senders, while standard dedicated IPs need warm-up and consistent volume.

For a small website that sends password resets, contact-form replies, and a few invoices, a well-managed shared mail service may produce better results with much less work. Dedicated email infrastructure is most useful when the sending volume and operational requirements justify maintaining it.

IPv4 may cost extra

The RIPE NCC exhausted its remaining IPv4 pool in November 2019. Networks now recover addresses, use transfer markets, or share IPv4 space while IPv6 deployment continues. That scarcity is why many providers limit extra IPv4 addresses or charge a monthly fee for them.

Check whether the advertised price includes the first dedicated IPv4 address, whether additional addresses are available, and what justification the provider requires. IPv6 space is far more plentiful, but an IPv6-only service will not replace IPv4 reachability for every visitor or integration.

It does not allocate more server resources

An IP address does not add CPU time, RAM, storage I/O, throughput, or DDoS filtering. It also does not repair an outdated plugin, close an exposed admin panel, or configure a firewall. Those are separate properties of the hosting platform and application.

Compliance requires more than an address assignment. As of July 24, 2026, the PCI Security Standards Council describes effective segmentation in terms of controls such as properly configured firewalls, routers with access-control lists, VLANs, and other technologies that restrict access. Its segmentation guidance does not make a dedicated IP a substitute for validated isolation. If an audit matters, ask the assessor about the complete architecture rather than buying an IP and treating the box as checked.

How to check what your hosting already includes

Start with the provider's control panel, order confirmation, and product documentation. Those sources can tell you whether the address is contractually assigned only to your account. A command on the server can show which addresses it sees, but it cannot prove that the provider does not reuse an upstream proxy, NAT address, or mail relay.

For a domain, inspect the public DNS records:

dig +short A example.com
dig +short AAAA example.com

If the site uses a CDN or reverse proxy, these results show the proxy's public addresses rather than the origin server. Seeing unrelated domains on the same address is evidence that the address is shared, but finding no other domains is not proof that it is dedicated. Reverse-IP databases are incomplete, and one customer can legitimately host many domains.

On a Linux VPS, list the addresses on active interfaces:

ip -brief address show up

Compare the result with the VPS control panel. Private addresses, link-local addresses, and a single configured address from a larger routed IPv6 subnet may all appear, so the provider's allocation details still matter.

If the server sends mail directly, check whether you control reverse DNS for its sending address:

dig -x 203.0.113.10 +short

Replace the documentation address with the real sending IP. A matching PTR record helps with mail setup, but it does not prove exclusivity either.

When the product page is unclear, ask the provider four precise questions:

1. Is this public IPv4 address assigned only to my account or server?
2. Is it expected to remain unchanged during routine maintenance and migrations?
3. Does outbound web and SMTP traffic use this address?
4. Can I set its PTR or reverse DNS record?

Those answers are more useful than a generic "dedicated IP included" badge.

Do you need one?

Choose a dedicated IP when a stable allowlist, a verified IP-based integration, direct high-volume mail, or address-level tenant isolation has operational value. Skip it when the only reasons are standard HTTPS, better rankings, faster pages, or a vague promise of improved security.

QDE sells both shared hosting and VPS plans, so our product interest is direct. Every QDE KVM VPS includes one dedicated IPv4 address and a /64 IPv6 subnet. Every QDE shared hosting account includes one dedicated IPv4 address, with one IPv6 address available on request. The shared hosting account still shares server resources; only its public IPv4 assignment is exclusive to that account.

Need help choosing between them? Contact the QDE team with the software you run and any IP, mail, or allowlisting requirements.

Frequently asked questions about dedicated IP addresses

What is the main benefit of a dedicated IP address?

It gives one account or server exclusive use of an address. That can provide a predictable endpoint and separate address-level reputation or blocking from unrelated tenants. The benefit only applies at the IP layer.

Is a dedicated IP the same as a static IP?

No. Dedicated means exclusive to one customer while assigned. Static means expected to remain unchanged. Many hosting products provide both, but you should confirm the provider's migration and renumbering policy when a firewall or partner integration depends on the address.

Does every QDE VPS include a dedicated IP?

Yes. Every QDE VPS plan includes one dedicated IPv4 address and a /64 IPv6 subnet as standard plan features.

Do I need a dedicated IP for an SSL certificate?

No for normal modern hosting. SNI lets one IP serve the correct certificate for many domain names. A dedicated IP is only relevant for legacy clients or a specific configuration that cannot use SNI.

Will a dedicated IP automatically improve email deliverability?

No. It isolates the sending IP's reputation only when outbound mail actually uses that address. New IPs also need a careful warm-up, valid forward and reverse DNS, email authentication, and clean sending practices. Low-volume senders often do better on a reputable shared mail service.

Can shared hosting include a dedicated IP?

Yes. Dedicated describes the address assignment, not the server resources. QDE shared hosting assigns one dedicated IPv4 address to each account even though the account still runs on a shared hosting platform.

Plausible is open source, cookie-free web analytics. The dashboard covers page views, visitors, referrers, entry and exit pages, countries, devices, goals, and custom events without trying to build an advertising profile for each visitor.

On a Linux VPS, the setup is Docker Compose behind Nginx and Let's Encrypt. We will keep the application port on localhost and finish with updates and backups. The analytics data stays with you, but the server maintenance does too.

What Plausible keeps on your server

Plausible splits its data between two databases. PostgreSQL holds accounts and site settings; ClickHouse holds the analytics events. According to Plausible's security and privacy documentation, the normal tracking flow uses no cookies and does not store raw visitor IP addresses or User-Agent strings. It creates a daily identifier with a rotating salt instead.

That is a much lighter data footprint than traditional advertising analytics, but self-hosting does not make a site compliant by default. Hosting location, Nginx logs, custom event properties, retention, access controls, and your privacy notice still count. Keep names, email addresses, account IDs, and other personal data out of custom properties.

ClickHouse sets the baseline for the server. The official Plausible Community Edition repository recommends at least 2 GB of RAM and a processor with SSE 4.2 or NEON support. For a small site, a QDE KVM VPS with at least 2 GB of RAM is a sensible starting point and gives you the root access needed for Docker. Start higher if you expect busy sites, long data retention, or several properties on one instance.

Before you begin

Have these ready:

• A fresh Debian, Ubuntu, CentOS Stream, Rocky Linux, or AlmaLinux server
• Root access or a user with sudo privileges
• At least 2 GB of RAM
• A domain or subdomain such as plausible.example.com
• DNS A and, if used, AAAA records pointing to the server
• Ports 80 and 443 open in any host or provider firewall

We use plausible.example.com throughout the guide. Replace it with your real hostname, and wait for DNS to resolve before asking Certbot for a certificate.

1. Install the required system packages

On Debian or Ubuntu:

sudo apt update
sudo apt install -y git curl openssl ca-certificates

On CentOS Stream, Rocky Linux, or AlmaLinux:

sudo dnf install -y git curl openssl ca-certificates

Nothing unusual here: Git handles the repository, curl downloads the Docker installer and checks local endpoints, OpenSSL generates the secrets, and the CA bundle keeps HTTPS downloads working.

2. Install Docker and Docker Compose

Docker's convenience script is the quickest route. Inspect it first if your server policy requires that, then run it:

curl -fsSL https://get.docker.com -o get-docker.sh
sudo bash get-docker.sh

On a production host with tighter package controls, follow the repository setup for your distribution in the Docker Engine installation guide instead.

If you are not logged in as root, add your current user to the docker group:

sudo usermod -aG docker $USER

The group change takes effect after you log out and back in. If you want to continue in the current session, start a new shell with:

newgrp docker

Treat membership in the docker group as root access, because that is effectively what it grants. Only add trusted administrator accounts. Docker covers the details in its Linux post-installation guide.

Enable Docker at boot and confirm both Docker Engine and the Compose plugin are available:

sudo systemctl enable --now docker
docker version
docker compose version

If either version command fails, fix Docker before moving on. The rest of the guide assumes both Engine and Compose are working.

3. Clone Plausible Community Edition

Clone the official repository and print the branch Git checked out:

git clone https://github.com/plausible/community-edition plausible
cd plausible
git branch --show-current

Plausible CE uses a separate branch for each release, and compose.yml pins the matching application image. The clone command leaves out -b, so Git checks out whichever version branch the repository currently marks as default. Compare the printed branch with the current official quick start before moving on. Keep that branch name in mind: a normal git pull will not jump to the next release later.

The repository includes Plausible, PostgreSQL, ClickHouse, and a set of conservative ClickHouse settings. Put your local configuration in .env and compose.override.yml; leave the tracked compose.yml alone. That avoids needless merge conflicts when it is time to upgrade.

4. Configure the environment

Start with an empty environment file:

touch .env

Add the public URL, then generate separate secrets for sessions and encrypted TOTP data:

echo "BASE_URL=https://plausible.example.com" >> .env
echo "SECRET_KEY_BASE=$(openssl rand -base64 48)" >> .env
echo "TOTP_VAULT_KEY=$(openssl rand -base64 32)" >> .env
chmod 600 .env

SECRET_KEY_BASE must stay the same after installation. Plausible uses it for sessions and other derived secrets. TOTP_VAULT_KEY protects two-factor authentication secrets at rest.

The TOTP key is optional. Without it, Plausible derives one from SECRET_KEY_BASE with PBKDF2. We set a separate random value anyway. Back up .env securely, and never paste either secret into a ticket, chat, or screenshot.

One small gotcha: the TOTP_VAULT_KEY assignment has one equals sign before the generated value. If the OpenSSL output ends in =, that character belongs to the Base64 value.

The official configuration reference covers the remaining options, including registration, SMTP, geolocation, database URLs, and Docker secrets.

5. Bind Plausible to localhost port 8000

Write the internal HTTP port to .env:

echo "HTTP_PORT=8000" >> .env

Plausible already defaults to port 8000. Writing it down makes the relationship between .env and the override file obvious when you come back to this setup months later.

Create compose.override.yml so Docker publishes that port only on 127.0.0.1:

cat > compose.override.yml <<'EOF'
services:
  plausible:
    ports:
      - "127.0.0.1:8000:${HTTP_PORT}"
EOF

The quotes around 'EOF' are doing real work. They leave ${HTTP_PORT} untouched until Docker Compose reads .env. Without the quotes, your shell can expand an unset variable first and write a broken port mapping.

Let Compose parse the merged configuration before starting anything. The --quiet flag checks the file without printing your secrets:

docker compose config --quiet

Plausible will now listen at 127.0.0.1:8000, where only the server itself can reach it. That is what we want. Nginx will handle the public traffic.

6. Start Plausible

Pull the container images and start the stack:

docker compose pull
docker compose up -d

The first start is not instant. PostgreSQL and ClickHouse need to pass their health checks before Plausible can set up its databases. Give the stack a moment, then check it:

docker compose ps
docker compose logs --tail=100 plausible

Once the containers are up, test the local HTTP endpoint:

curl --head http://127.0.0.1:8000

Any HTTP response confirms that the host can reach Plausible. If the connection fails, run docker compose logs --tail=200 and fix the container error before adding Nginx to the mix.

7. Configure Nginx as the reverse proxy

Install Nginx, Certbot, and Certbot's Nginx plugin.

On Debian or Ubuntu:

sudo apt update
sudo apt install -y nginx certbot python3-certbot-nginx

On CentOS Stream, Rocky Linux, or AlmaLinux:

sudo dnf install -y epel-release
sudo dnf install -y nginx certbot python3-certbot-nginx

The configuration path differs by distribution. On Debian or Ubuntu, create:

/etc/nginx/sites-available/plausible.example.com.conf

On CentOS Stream, Rocky Linux, or AlmaLinux, create:

/etc/nginx/conf.d/plausible.example.com.conf

Put the same server block in either file:

upstream plausible {
    server 127.0.0.1:8000;
}

server {
    listen 80;
    listen [::]:80;

    server_name plausible.example.com;

    location / {
        proxy_pass http://plausible;
        proxy_http_version 1.1;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location /live/websocket {
        proxy_pass http://plausible;
        proxy_http_version 1.1;

        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }
}

The /live/websocket block is easy to miss, but the live dashboard needs it. The other headers pass the original hostname, client chain, and request scheme to Plausible. This setup follows Plausible's reverse proxy guidance and adds the usual forwarded headers.

On Debian or Ubuntu, enable the site:

sudo ln -s /etc/nginx/sites-available/plausible.example.com.conf /etc/nginx/sites-enabled/

If that symlink already exists, leave it alone.

On CentOS Stream, Rocky Linux, or AlmaLinux with SELinux enforcing, Nginx also needs permission to reach the local upstream:

sudo setsebool -P httpd_can_network_connect 1

Test the configuration, enable Nginx at boot, and reload it:

sudo nginx -t
sudo systemctl enable --now nginx
sudo systemctl reload nginx

Treat nginx -t as a gate. Fix every reported error before requesting a certificate.

8. Add HTTPS with Certbot

With DNS resolving and ports 80 and 443 reachable, let Certbot request the certificate and update the Nginx virtual host:

sudo certbot --nginx -d plausible.example.com

Run one more configuration test before reloading Nginx:

sudo nginx -t
sudo systemctl reload nginx

Check the public endpoint from the command line:

curl --head https://plausible.example.com

Test certificate renewal now, while the setup is still fresh:

sudo certbot renew --dry-run

9. Create the first user and restrict registration

Open https://plausible.example.com and register the first user. Add your website in the dashboard, then copy Plausible's tracking snippet into the site's <head>.

Plausible defaults to invitation-only registration after the first account is set up. We still write the value to .env, so the intended behavior is obvious the next time someone reads the file:

echo "DISABLE_REGISTRATION=invite_only" >> .env
docker compose up -d

Invited users can still register with this setting. Use DISABLE_REGISTRATION=true only when you want to block every new account, invitations included.

Take one final look at the stack:

docker compose ps
docker compose logs --tail=100 plausible

Update Plausible

Plausible's release model is easy to miss. Every release gets its own version branch, and security fixes are not backported to old versions. A plain git pull stays on the branch you already have; docker compose pull then reads the image tags from that same branch. Both commands can finish successfully while Plausible remains on the old release.

Before upgrading, read the project's release page and upgrade guide. Some releases have extra steps for PostgreSQL or ClickHouse. Take a backup first, then replace vX.Y.Z below with the exact target branch from the release notes:

cd plausible
git status --short
git pull origin vX.Y.Z
docker compose pull
docker compose up -d

docker compose pull is optional here. It refreshes every image in the new Compose file, but git pull origin vX.Y.Z is the command that selects the Plausible release by updating the pinned image. If Git reports a conflict, stop and resolve it. The same goes for any extra migration step in the release notes.

Check the containers and the Plausible log after the upgrade:

docker compose ps
docker compose logs --tail=100 plausible

Because the local port binding lives in compose.override.yml, the tracked compose.yml stays clean and is less likely to conflict during git pull origin vX.Y.Z.

Keep application-level backups

A server snapshot is useful, but Plausible keeps important state in both PostgreSQL and ClickHouse volumes. Back up both databases, keep a copy outside the VPS, and run at least one test restore. Discovering an incomplete backup after a failure is too late.

QDE includes daily offsite VPS backups, giving you another recovery point for server-wide mistakes. Treat them as an extra layer underneath your database backups, not a replacement for them.

Once those checks pass, add the tracking snippet and wait for the first visits to appear. From then on, it is ordinary server care: read the release notes, apply updates, watch storage, and make sure the backups still restore.

The €1 difference between QDE's entry plans should not decide this. Your software, your need for email, and your willingness to maintain Linux matter far more.

QDE has just added cPanel Shared Hosting alongside our existing KVM VPS plans. We sell both. That gives us an obvious commercial interest, but very little reason to steer a WordPress blog onto a server its owner does not want to maintain. A Docker application, meanwhile, will not fit into shared hosting just because cPanel is convenient.

Shared hosting leaves the server to the provider

Shared hosting puts several customer accounts on one server and one operating system. The provider's system administrators maintain that operating system, apply security patches, tune the services, monitor the host, and deal with hardware or network faults. You look after the website.

Day-to-day work happens in a browser. cPanel covers files, FTP accounts, domains, email accounts, databases, SSL certificates, and common site tasks. cPanel's documentation gives a good picture of what sits behind that dashboard. You do not need SSH to create a mailbox or install WordPress.

QDE Shared Hosting starts at €2.95/month. Starter includes 10 GB of NVMe storage, up to 512 MB of RAM per hosting account, 4 TB of monthly transfer, a 10 Gbps shared uplink, a dedicated IPv4 address, 10 email accounts, 10 SQL databases, and daily offsite backups. It supports PHP 8.2 through 8.5 and static HTML, with MariaDB available through cPanel.

A VPS makes you the sysadmin

A virtual private server is a virtual machine with its own operating system. QDE uses KVM, the virtualization system built into the Linux kernel. The Linux KVM documentation covers the virtual machine and vCPU interfaces behind it. In ordinary use, the important part is simpler: the VPS boots its own Linux installation and gives you full root access.

You choose the packages, runtime, web server, database, firewall rules, and update schedule. Node.js, Python, Go, Docker, PostgreSQL, Redis, WireGuard, background workers, and custom systemd services are all reasonable VPS workloads.

QDE VPS Hosting starts at €3.95/month. Ryzen Mini includes one AMD Ryzen 7950X CPU core, 1 GB RAM, 15 GB of pure NVMe storage, 4 TB of monthly transfer, one dedicated IPv4 address, a /64 IPv6 subnet, daily offsite backups, and a 10 Gbps shared uplink. RAM and storage are allocated to the VPS and are not oversold. CPU time still comes from a physical host. The word "private" describes the virtual machine's isolation, not ownership of a bare-metal server.

The good and bad of shared hosting

The strongest case for shared hosting is all the maintenance you never see. You are not responsible for kernel updates, web server patches, the mail stack, PHP packaging, or the host firewall. For a WordPress blog, company website, portfolio, or small PHP application, those jobs add risk without making the site any better.

Email is easy to underestimate. On shared hosting, you can create info@example.com, connect it over IMAP, set up forwarding, and get back to the website. Running mail on a VPS means maintaining an MTA, spam filtering, DKIM, SPF, DMARC, reverse DNS, queues, reputation, and deliverability. It can be done. It is also a separate operations project.

cPanel helps when more than one person works on a site. A colleague can add a domain, restore a file, or create a database user without sudo access and without knowing where a particular service keeps its configuration.

The tradeoff is that CPU, memory, and the underlying services are shared with other accounts. A well-run platform applies resource controls, but another busy account can still compete for host resources. That is the noisy-neighbor problem. It matters less to a modest brochure site than to a job that regularly keeps every CPU core busy.

You also stay within the software stack supplied by the host. QDE Shared Hosting runs PHP, MariaDB, and static sites. It does not provide long-running Node.js or Python daemons, Docker, a custom database server, or root access. No cPanel setting changes that boundary.

The good and bad of a VPS

Root access removes the provider's application list as a constraint. You can choose a Linux distribution, pin runtime versions, run containers, configure a reverse proxy, or install a database that is not available on a shared plan. One VPS can host a website, API, queue worker, scheduled jobs, and monitoring agent if the plan has enough resources.

The isolation is clearer too. Your allocated RAM and NVMe storage belong to your virtual machine, and another customer cannot read your filesystem or change your packages. A /64 IPv6 subnet gives you address space for services that can use it.

This is also why an inexpensive VPS can create more work than an inexpensive website. QDE VPS plans are unmanaged. You must apply operating system updates, secure SSH, configure the firewall, maintain your services, and investigate failures. If an update breaks Nginx at 02:00, the invoice does not include someone logging in to repair your configuration.

Treat a public VPS as exposed from its first boot. Internet-wide scanners do not wait for you to finish setting up the application. Keep internet-facing services patched, limit management access where possible, and disable anything you do not need. Use SSH keys, disable password login when practical, and apply the first round of updates before deploying the application.

A server management panel or one-click stack can reduce the amount of configuration you do by hand. It does not turn an unmanaged VPS into a managed service. Daily backups give QDE customers a recovery path after a bad change, but last night's backup will not contain data written this morning. Keep application-level backups for data you cannot recreate.

Starter and Ryzen Mini side by side

The entry price differs by €1/month. The products are still built for different jobs.

Paying €1 more for a VPS does not make server maintenance disappear. Saving €1 on shared hosting does not give you Docker or root access. Price is the least useful distinction between these two plans.

Daily offsite backups are standard on both. That gives you a way back when a WordPress update goes wrong or you damage a VPS configuration. Provider backups are still a safety net, not the only copy of important data.

Common projects and the sensible default

A WordPress blog, small business site, portfolio, or PHP application belongs on shared hosting unless it has an unusual requirement. Shared hosting is also the straightforward choice when you need email on your own domain and have no interest in operating a mail server. You manage sites, files, domains, and mailboxes in cPanel. The host manages the server.

A developer who needs Node.js, Python, Go, Docker, or a custom database should choose a VPS. The same applies to APIs, bots, game servers, VPNs, self-hosted applications, development environments, and anything that must run continuously in the background. You get the control, along with the maintenance bill measured in time rather than euros.

Starting on shared hosting and moving to a VPS later is normal. The move is a migration rather than a one-click plan upgrade because the server layout and mail setup are different. Both products can live under the same QDE account, and our team can help with the handoff when your requirements change.

Which one should you order?

Choose the product that fits today's job. A website owner who never wants to open a terminal will usually be happier on shared hosting. A developer who needs to control packages, services, and networking will reach shared-hosting limits quickly.

Compare cPanel Shared Hosting from €2.95/month and Ryzen VPS Hosting from €3.95/month without treating the VPS as an automatic upgrade. Shared hosting buys convenience. A VPS buys control. You can change course later.

Umami is a smaller, cleaner option. It is an open-source, privacy-focused analytics platform for page views, referrers, devices, countries, events, and campaign data. You can run it on your own server with PostgreSQL, and the official Docker setup is short enough to understand before you paste it.

Below is a full VPS setup: Docker Compose for Umami and PostgreSQL, Nginx as the public reverse proxy, Let's Encrypt certificates through Certbot, plus the two maintenance jobs people tend to forget: backups and updates.

Why keep analytics data local

Website analytics can look harmless because the dashboard is clean. The data behind it is still behavioral data: visited URLs, timestamps, referrers, device information, country-level location, and any event names you define. With a third-party analytics service, that stream leaves your infrastructure by design.

Self-hosting Umami keeps that data on your side. Traffic records land in your PostgreSQL database, on your server, under your backup policy. You still need a privacy policy, and you still need to understand the consent rules that apply to your site. The difference is that you are not sending analytics into a large advertising ecosystem just to learn which blog post is getting traffic.

The server requirements are modest. A small KVM VPS is enough for a personal site or a few low-traffic projects. A larger instance gives PostgreSQL more room if you track several websites or keep data for a long time. Fast storage helps more than people expect because analytics is mostly database reads and writes.

What you need before installing Umami

You need:

• A Linux server with root or sudo access
• A domain or subdomain for Umami, such as stat.example.com
• DNS already pointing that hostname to your server's IPv4 address
• Ports 80 and 443 open on the server firewall
• A shell session as either root or a sudo-capable user

The Compose file below binds Umami to 127.0.0.1:3000, so the app port is not exposed directly to the public internet. Nginx accepts public HTTP/HTTPS traffic and proxies it to the local container.

Install Docker and Docker Compose

On Debian, one short path is to use extrepo if your release includes the Docker CE repository entry:

sudo apt update
sudo apt install extrepo
sudo extrepo enable docker-ce
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

For other Linux systems, Docker provides a convenience script:

curl -fsSL https://get.docker.com -o get-docker.sh
sudo bash get-docker.sh

Docker documentation describes that script as useful for testing and development, so inspect it first if this is a production server. On Debian or Ubuntu, make sure the Compose plugin is present:

sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

On CentOS Stream, Rocky Linux, or AlmaLinux, install the same packages through dnf after the Docker repository has been configured:

sudo dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

If you are not running as root, add your current user to the docker group:

sudo usermod -aG docker $USER

Before testing, log out and back in, or run newgrp docker. The Docker Linux post-installation guide warns that membership in the docker group grants root-level privileges, so only add users who should have that level of access.

Enable Docker and confirm both Docker and the Compose plugin work:

sudo systemctl enable --now docker
docker version
docker compose version

Create the Umami Compose file

Create a dedicated directory for Umami:

mkdir -p ~/services/umami
cd ~/services/umami

Generate two random values before writing the file: one for Umami authentication tokens and one for PostgreSQL:

openssl rand -hex 32
openssl rand -hex 32

Create compose.yaml:

name: umami

services:
  umami:
    container_name: umami
    image: docker.umami.is/umami-software/umami:latest
    ports:
      - "127.0.0.1:3000:3000"
    environment:
      DATABASE_URL: postgresql://umami:CHANGE_ME_DB_PASSWORD@umami-db:5432/umami
      DATABASE_TYPE: postgresql
      APP_SECRET: CHANGE_ME_APP_SECRET
    depends_on:
      umami-db:
        condition: service_healthy
    init: true
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "curl http://localhost:3000/api/heartbeat"]
      interval: 5s
      timeout: 5s
      retries: 5

  umami-db:
    container_name: umami-db
    image: postgres:18-alpine
    environment:
      POSTGRES_DB: umami
      POSTGRES_USER: umami
      POSTGRES_PASSWORD: CHANGE_ME_DB_PASSWORD
    volumes:
      - ./data:/var/lib/postgresql
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
      interval: 5s
      timeout: 5s
      retries: 5

Replace both CHANGE_ME_DB_PASSWORD values with the same PostgreSQL password. Replace CHANGE_ME_APP_SECRET with a different random string. The Umami environment variable docs describe APP_SECRET as the value used to secure authentication tokens, so do not reuse it elsewhere.

Checked on July 2, 2026, Docker Hub lists postgres:18-alpine as an active official Postgres image tag. It is a reasonable choice for a fresh Umami install. For an existing install, treat database major versions carefully: make a pg_dump, test a restore, and only then change the image tag.

Start Umami

Pull the images and start the stack:

docker compose pull
docker compose up -d

Check the containers:

docker compose ps
docker compose logs -f umami

Umami listens on http://127.0.0.1:3000 from the host. Because the container is bound to localhost, you will not open it directly from your browser yet. Nginx will be the public entry point.

The default administrator account is:

• Username: admin
• Password: umami

The Umami login guide says to change that password immediately after your first login. Do it before adding websites or sharing the URL.

Configure Nginx as a reverse proxy

Install Nginx:

# Debian or Ubuntu
sudo apt update
sudo apt install nginx

# CentOS Stream, Rocky Linux, or AlmaLinux
sudo dnf update
sudo dnf install nginx

For this example, the analytics hostname is stat.example.com. Replace it with your real hostname.

On Debian or Ubuntu, create /etc/nginx/sites-available/stat.example.com.conf:

upstream umami_backend {
    server 127.0.0.1:3000;
}

server {
    listen 80;
    listen [::]:80;

    server_name stat.example.com;

    location / {
        proxy_pass http://umami_backend;
        proxy_http_version 1.1;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Enable it:

sudo ln -s /etc/nginx/sites-available/stat.example.com.conf /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx

On CentOS Stream, Rocky Linux, or AlmaLinux, put the same server block in:

/etc/nginx/conf.d/stat.example.com.conf

Then test and start or reload Nginx:

sudo nginx -t
sudo systemctl enable --now nginx
sudo systemctl reload nginx

Nginx configuration files under /etc/nginx/ require root privileges. If nginx -t fails, fix that before touching Certbot.

Add HTTPS with Certbot

Install Certbot and the Nginx plugin:

# Debian or Ubuntu
sudo apt install certbot python3-certbot-nginx

# CentOS Stream, Rocky Linux, or AlmaLinux
sudo dnf install epel-release
sudo dnf install certbot python3-certbot-nginx

Issue the certificate:

sudo certbot --nginx -d stat.example.com

After Certbot edits the Nginx config, check the site:

sudo nginx -t
sudo systemctl reload nginx

Now open:

https://stat.example.com/

Log in with admin and umami, then change the password from Settings before doing anything else. A public analytics dashboard with default credentials will not stay yours for long.

Certbot packages often install a systemd timer for renewals. Check it:

systemctl list-timers | grep certbot
sudo certbot renew --dry-run

If your install does not create a timer and you are following Certbot's pip/virtualenv method, the EFF Certbot instructions use a cron job like this:

echo "0 0,12 * * * root /opt/certbot/bin/python -c 'import random; import time; time.sleep(random.random() * 3600)' && sudo certbot renew -q" | sudo tee -a /etc/crontab > /dev/null

For distro packages, prefer the package's timer when it exists. Run sudo certbot renew --dry-run either way, so you know renewal works before the certificate is close to expiry.

Add a website and install the tracking script

Once you are logged in, go to Websites and click Add website. The Umami add-a-website guide covers the two fields that matter: the name can be anything, and the domain should be the actual website domain so Umami can filter your own site correctly.

After saving the website, open its edit screen and copy the tracking code. The Umami collect data guide says to place that code in the <head> section of the site you want to track.

The snippet looks roughly like this:

<script defer src="https://stat.example.com/script.js" data-website-id="YOUR-WEBSITE-ID"></script>

Visit your site, then return to the Umami dashboard. If no data appears, open the browser developer tools and check whether script.js and /api/send requests reach stat.example.com. Browser extensions and aggressive content blockers can block analytics scripts, even self-hosted ones.

Back up Umami

The data that matters lives in PostgreSQL. Create a backup directory and dump the database:

mkdir -p ~/services/umami/backups
cd ~/services/umami
docker exec umami-db pg_dump -U umami -d umami | gzip > backups/umami_$(date +%F).sql.gz

Copy that .sql.gz file somewhere outside the VPS. Also keep a copy of compose.yaml, because it records the image, ports, and environment variable shape you need for a clean restore.

If you host Umami on QDE, the platform-level daily backups are a useful second layer, but they are not a replacement for an application-level database dump. A dump is portable. A server snapshot is convenient. Keep both.

Update Umami

Back up first, then update from the Umami directory:

cd ~/services/umami
docker compose pull
docker compose up -d

Watch the logs after the update:

docker compose logs -f umami

The Umami README recommends pulling the new Docker image and recreating the container for Docker-based updates. For major releases, read the release notes before you pull. Analytics data is small compared with a photo library, but losing it because you treated the database casually is still annoying.

Keep the analytics close to the app

Self-hosting Umami gives you useful traffic numbers without routing visitor data through Google Analytics. The moving parts are ordinary: Docker for the app and PostgreSQL, Nginx for the public hostname, Certbot for HTTPS, and a small backup routine you can run from cron.

The privacy benefit is strongest when the rest of the stack matches it. Run Umami on infrastructure you control, keep the database in a jurisdiction you understand, and avoid adding more third-party scripts than you removed.

QDE provides privacy-focused VPS hosting in the Netherlands with KVM virtualization, NVMe storage, 10 Gbps uplinks, full root access, and daily offsite backups. That is a practical place to run Umami while keeping analytics data under your own administration.

Frequently asked questions about self-hosting Umami

Is Umami free to self-host?

Yes. Umami is open source, and you can run it on your own server. Your cost is the VPS, domain, and the time you spend maintaining the service.

Does Umami replace Google Analytics?

For most small and medium websites, yes. Umami gives you page views, referrers, countries, devices, events, and campaign tracking. It does not replace every advanced Google Analytics workflow, but it covers the numbers many site owners actually use.

Do I need a big VPS for Umami?

No. A small VPS is enough for a personal site or a few low-traffic websites. If you track many domains, keep a long retention window, or run other services on the same machine, give PostgreSQL more RAM and disk headroom.

Why bind Umami to 127.0.0.1?

Binding the container to 127.0.0.1:3000 keeps the app port private. Only Nginx is exposed publicly on ports 80 and 443, which gives you one public entry point for TLS, headers, and access control.

Where does Umami store data?

In the Compose file above, Umami stores analytics data in PostgreSQL, and PostgreSQL writes its files under ~/services/umami/data on the host. The portable backup is the pg_dump output rather than the raw database directory.

What should I do right after the first login?

Change the default admin password. The official Umami docs state that the default account is admin with password umami, and the first task after logging in is to change it.

For server operators, the useful parts are the new kernel, package-management behavior, OpenSSH defaults, database versions, and upgrade work around older cgroup, PostgreSQL, MySQL, and SSH setups.

Release overview

Ubuntu published Ubuntu 26.04 LTS "Resolute Raccoon" on April 23, 2026. Canonical lists it as a long-term support release with standard security updates and critical bug fixes until April 2031. With Ubuntu Pro ESM, that support window can extend to April 2036.

For small VPS plans, the baseline remains practical. Ubuntu's release notes state that Server 26.04 LTS requirements start at 1.5 GB RAM and 4 GB of storage, depending on workload. QDE's template includes cloud-init support and Fail2Ban for SSH protection.

What is new for servers

Kernel, init, and package management

Ubuntu 26.04 ships with Linux kernel 7.0 for the GA generic stack and HWE stack, according to the LTS user summary. The same summary notes that the real-time Linux kernel is now available in the main archive, outside Ubuntu Pro.

systemd moves to 259, and the important compatibility change is cgroup v1 removal. Legacy and hybrid cgroup hierarchies are gone. If you still run old LXC hosts, monitoring agents, or custom service units that assume cgroup v1 paths, test before doing an in-place upgrade.

APT moves to the 3.x line. Ubuntu's notes list APT 3.1 and call out two server-relevant changes: TLS and file hashing now use OpenSSL, and apt-key has been removed. Repository signing should use keyrings and signed-by, not scripts that still pipe keys into apt-key add.

Dracut is now the default initial ramdisk infrastructure, replacing initramfs-tools. initramfs-tools remains available, but the default boot plumbing has changed. Custom kernels, storage drivers, remote unlock setups, and recovery playbooks need checking.

Memory safety and cryptography

Ubuntu 26.04 continues Canonical's memory-safety work. sudo-rs is now the default sudo provider, while the original C sudo remains available as sudo.ws. The core utilities are provided by rust-coreutils; Ubuntu still provides GNU fallbacks, and cp, mv, and rm remain GNU implementations because of unresolved compatibility issues.

The cryptography stack also changes. OpenSSL 3.5 includes post-quantum cryptography support for ML-KEM and ML-DSA. OpenSSH 10.2 is included, and Ubuntu's OpenSSH notes list the hybrid post-quantum key exchange mlkem768x25519-sha256 as available by default. DSA support is removed, and host DSA keys are no longer generated.

For operators, the short version is simple: rotate any remaining DSA SSH keys before you upgrade. Modern clients should negotiate post-quantum hybrid key exchange without extra configuration.

Virtualization, identity, and compute

The 26.04 virtualization stack includes QEMU 10.2 and libvirt 12.0. Ubuntu also documents confidential-computing support around Intel TDX and AMD SEV-SNP in its virtualization notes. Platform operators and dedicated server users building their own virtualization hosts should notice this first.

For identity, authd is available from the Ubuntu archive and supports OpenID Connect workflows, including Google IAM and Microsoft Entra ID device registration. Teams standardizing Linux login through an identity provider should evaluate it in staging before using it on production access paths.

Updated server stack

Ubuntu 26.04 brings a large server stack refresh. The versions below are the ones administrators will notice first when selecting the QDE template.

PostgreSQL 18 is one of the more important server updates. Ubuntu highlights the new PostgreSQL I/O subsystem, with storage-read improvements measured at up to 3x in upstream testing, and the database-friendly uuidv7() function. The upstream PostgreSQL 18 upgrade documentation is still required reading for existing database hosts.

Upgrade considerations

New deployments are straightforward. In-place upgrades need more care.

• cgroup v1 removal can break old container and service-management assumptions. Check old LXC hosts and custom service units before upgrading.
• PostgreSQL major upgrades are data migrations, not ordinary package updates. Plan pg_upgrade, dump and restore, or logical replication.
• Ubuntu documents a known PostgreSQL throughput and latency regression triggered by a Linux 7.0 change when huge pages are not enabled. For PostgreSQL on 26.04, turn huge pages on and set PostgreSQL huge_pages to on.
• MySQL 8.0 to 8.4 includes configuration and default changes. Oracle's MySQL 8.4 upgrade notes list incompatible changes and changed server defaults, so review custom mysqld.cnf before moving production databases.
• DSA SSH keys should be removed before the upgrade. OpenSSH 10.2 no longer supports the weak DSA signature algorithm.

For new servers, use Ubuntu 26.04 LTS now. For production migrations from Ubuntu 24.04 LTS, especially database or container hosts, waiting for the 26.04.1 point release scheduled for August 27, 2026 is a reasonable default.

Current QDE Linux templates

The current QDE Linux template set is:

• Debian 12 and 13. Debian 11 is approaching the end of LTS on August 31, 2026, so use 12 or 13 for new deployments.
• Ubuntu 22.04, 24.04, and 26.04.
• Rocky Linux 8, 9, and 10.
• AlmaLinux 8, 9, and 10.
• CentOS Stream 9 and 10.

All QDE Linux templates include Fail2Ban for SSH protection, and cloud-init is supported on all templates.

QDE also provides netboot.xyz.iso for customers who prefer to install an operating system manually. Use it for a custom partition layout, installer-driven setup, or a system image outside the standard template list.

How to deploy on QDE

For a new server, select the Ubuntu 26.04 LTS template during checkout. For an existing VPS or dedicated server, use OS reinstall in the control panel after taking backups.

If you are building a fresh service today, Ubuntu 26.04 LTS is the right default. If you are moving a running 24.04 system, treat it as an upgrade project: test your containers, database engines, SSH keys, boot tooling, and monitoring agents first.

Start from the QDE VPS page when you are ready to deploy Ubuntu 26.04 LTS.

This guide compares six registrars based in or operating from Europe, including one Swiss option. We'll cover what actually makes a registrar "European," what to look for before you hand over your details, and where each provider fits depending on whether you want broad TLD coverage, the lowest bulk pricing, or a single account for both your domain and your hosting.

What "European" actually means here

A registrar is European if the company behind it is headquartered and operates in Europe, not just if it happens to sell you a .eu domain. That distinction matters because the jurisdiction your registrar sits in determines which laws govern your account data, your billing records, and how your registrant details are published.

There's a useful split worth understanding. EU-based registrars fall squarely under the GDPR, which is why they redact personal information from public WHOIS by default rather than charging for it as a privacy add-on. Switzerland sits outside the EU but maintains its own strict data protection laws and is recognized as offering adequate protection, so a Swiss registrar can give you a slightly different legal footing while still working fine for EU customers.

One more detail: the .eu extension itself is managed by the registry EURid, and it can only be registered by residents or organizations within the EU, Iceland, Liechtenstein, or Norway. Most European registrars offer it, but it's not something a US-resident customer can pick up.

What to look for in a European domain registrar

Before the list, here's what separates a registrar worth keeping a domain with from one you'll want to transfer away from in a year.

Flat, honest pricing is the big one. Plenty of registrars advertise a low first-year price that quadruples on renewal. The better European providers show you the same number for registration and renewal, so there's no second-year shock.

Free WHOIS privacy should be the default, not a paid line item. EU registrars redact registrant data automatically under GDPR, so if a provider is trying to sell you privacy protection separately, that's a sign it isn't really built around European norms.

Beyond that, look for free DNS management with full record control (A, AAAA, CNAME, MX, TXT), the freedom to use your own nameservers, no lock-in when you want to transfer out, support during hours that match your time zone, and payment methods that suit you, whether that's SEPA, iDEAL, cards, or crypto.

The best European domain registrars

QDE: best for keeping your domain and hosting together

QDE keeps its registrar offering deliberately narrow, focusing on the three extensions most teams actually use: .com, .net, and .org. Each is €10.95 per year, and that's the price for both registration and renewal, so there's no teaser rate that climbs later. Every domain includes free DNS management, WHOIS privacy redaction by default, the option to use any nameservers you like, and no lock-in when you want to move on.

Where QDE stands out isn't TLD breadth, it's consolidation. The company is a Netherlands-based host first, so you can register a domain and point it at a QDE VPS or shared hosting from the same account, with one set of billing and one dashboard. Payments include PayPal, cards, iDEAL, and cryptocurrency, which is rare among traditional registrars. If you want hundreds of obscure extensions, look further down this list. If you want your domain, DNS, and server living in one EU account, QDE is the cleanest fit.

Gandi: best for transparent registration with broad TLD coverage

Gandi is the French registrar that built its reputation on a "no bullshit" approach long before transparency became a selling point. It carries a large catalog of TLDs, includes WHOIS privacy at no cost, and runs an interface designed to help you manage domains rather than push add-ons at every step.

Pricing isn't the cheapest in this list, and a round of increases a few years back annoyed some long-time users, but you always know what you're paying. For a French company processing your data under GDPR with a genuinely wide extension lineup, Gandi remains the default recommendation for most people who just want a solid, honest registrar.

OVHcloud: best for scale and low bulk pricing

OVHcloud is Europe's largest cloud and hosting provider, and its domain pricing reflects that scale. If you're registering or managing a large portfolio, or you want domains, DNS, hosting, and cloud infrastructure under one French, GDPR-compliant roof, OVHcloud is hard to beat on cost.

The trade-off is polish. The platform is sprawling and the interface can feel more enterprise than friendly, so it suits teams comfortable navigating a larger control panel more than someone registering their first domain.

Infomaniak: best for privacy and sustainability

Infomaniak is the Swiss option, and it's the one to look at if data protection and environmental footprint both matter to you. Because it operates from Switzerland, your data benefits from some of the strictest privacy laws around while the company still meets the requirements for doing business across the EU.

It's also one of the more environmentally serious providers in this space, running on renewable energy and offsetting well beyond its own emissions. Service quality is consistently well regarded. If a Swiss jurisdiction and a clear sustainability record appeal to you, Infomaniak earns its place.

EuroDNS: best for European country-code domains

EuroDNS, based in Luxembourg, specializes in exactly what its name suggests. If you need European ccTLDs like .eu, .de, .fr, .nl, or .no, or you manage a portfolio of country-specific domains and want bulk tools and knowledgeable support during European business hours, this is the specialist pick.

It's less suited to people who mainly want cheap .com domains, where a budget registrar will undercut it, and WHOIS privacy isn't always free here. But for niche European extensions that the big US registrars don't even carry, EuroDNS does one job and does it well.

INWX: best for developers and resellers

INWX is a German registrar popular with power users, agencies, and resellers. It supports a broad range of TLDs, offers competitive pricing, and is known for a capable API that makes automating registrations and DNS changes straightforward.

The interface is functional rather than flashy, which is the point. If you're managing domains programmatically or running them as part of a larger operation, INWX gives you the control and tooling to do it without fuss.

Honorable mentions

A couple of others are worth a look depending on your setup. Hetzner offers very competitive domain pricing alongside its well-known German hosting, which makes it convenient if your servers already live there.

Openprovider in the Netherlands runs a wholesale, membership-style model that's aimed at resellers managing domains at volume rather than individuals registering one or two.

How to move a domain to a European registrar

Switching is more routine than people expect, and it usually takes a few minutes of active work plus some waiting.

Start by unlocking the domain at your current registrar and requesting the authorization code, sometimes called an EPP or transfer code. Make sure WHOIS privacy isn't blocking the transfer confirmation email, and check that the domain isn't inside the 60-day lock that applies right after registration or a previous transfer.

Then start the transfer at your new registrar, enter the auth code, and approve the confirmation email when it arrives. The transfer typically completes within five to seven days, and most registrars add a year to your registration as part of the move, so you don't lose the time you'd already paid for. Point your DNS records before you switch if you want zero downtime.

So which European registrar is best?

There isn't a single winner, and any list that claims one is selling you something. Gandi is the safe all-rounder for transparent registration across a wide range of extensions. OVHcloud wins on scale and bulk cost. Infomaniak is the pick for Swiss-grade privacy and sustainability. EuroDNS owns the European country-code niche, and INWX is built for developers and resellers.

If your priority is keeping a domain in the same place as the server it points to, with flat pricing and privacy switched on by default, QDE registers .com, .net, and .org at €10.95 a year, renewal included, with free DNS management and no lock-in. It's a European provider operated from the Netherlands, with data handling aligned to EU privacy law and cryptocurrency among its payment options.

Thanks for reading! If you're also deciding where to host the site behind that domain, QDE runs high-performance KVM VPS in the Netherlands on pure NVMe storage with 10 Gbps uplinks, so you can register and deploy from one account.

Ready to register a domain or spin up a server? Contact our team and we'll help you find the right fit.

Frequently asked questions about European domain registrars

Why choose a European domain registrar over a US one?

A European registrar processes your account and registrant data under EU law, redacts your personal details from public WHOIS by default, and typically avoids the aggressive upselling and renewal price jumps common with the large American providers. For EU customers it also means support and billing aligned to your time zone and payment methods.

Are European registrars GDPR compliant?

EU-based registrars operate directly under the GDPR, which is why WHOIS privacy is automatic rather than a paid extra. Swiss registrars like Infomaniak fall under Switzerland's own strict data protection laws while still meeting EU requirements.

Can anyone register a .eu domain?

No. The .eu extension is restricted to residents and organizations in the EU, Iceland, Liechtenstein, or Norway. Most European registrars offer it, but you'll need to meet the residency requirement.

Does WHOIS privacy cost extra at European registrars?

Usually not. Under GDPR, EU registrars redact registrant personal data from public WHOIS, RDAP, and RDDS output by default, so it's included rather than sold separately. A few registrars still treat it as an add-on, so it's worth checking.

Which registrar is cheapest for .com domains?

Large-scale providers like OVHcloud tend to have the lowest bulk pricing, while flat-rate registrars like QDE keep registration and renewal at the same €10.95 so there's no second-year increase. The cheapest first-year price isn't always the cheapest over several years.

Can I transfer my existing domain to a European registrar?

Yes, as long as the domain is at least 60 days past its last registration or transfer and isn't locked. You'll unlock it, get the authorization code from your current registrar, and approve the transfer at the new one, which usually completes within a week and adds a year to your registration.

Can I register a domain without buying hosting?

Yes. Registrars sell domains as a standalone product, and you're free to point yours at any host or use your own nameservers. With a provider like QDE you can keep the domain and hosting together if you want, but it isn't required.

That's the problem Linkwarden was built to solve, and it's why a lot of people choose to self-host Linkwarden instead of handing their reference library to a third-party service. It's an open-source bookmark manager that saves a full copy of every page you bookmark, a screenshot, a PDF, a single HTML file, and a clean readable version, so the content stays accessible even after the original goes offline. Think of it as a private Wayback Machine you own end to end, with collections, tags, search, and a few AI tricks layered on top.

This guide covers what Linkwarden does, what you need to run it, and how to deploy it with Docker on your own server. We'll also set up the parts most quick-start guides skip: full-text search, AI tagging, backups, and a reverse proxy so you can reach it over a real domain.

What Linkwarden actually does

At its core, Linkwarden is a bookmark manager. You save a link, drop it into a collection, and add some tags. The part that sets it apart is preservation. The team behind it built the whole app around the reality of link rot, so saving a bookmark also means saving the page itself.

When you add a link, Linkwarden fetches the page and stores several formats locally: a full-page screenshot, a PDF, a single self-contained HTML file, and a stripped-down readable view for distraction-free reading. If you'd rather lean on a public archive too, it can optionally push a snapshot to the Internet Archive's Wayback Machine on your behalf. Either way, you keep your own copy.

The "and more" is where it earns a permanent spot in a self-hosted stack:

• Collections and nested sub-collections, plus multiple tags per link, for organizing a large library
• Full-text search across everything you've saved, powered by Meilisearch
• Local AI tagging that reads a page's content and suggests tags automatically
• RSS subscriptions that pull new articles into a collection on their own
• Shared collections with per-member permissions, handy for team research
• Reader view with text highlighting and annotation
• Chrome and Firefox extensions, a documented API, and bulk import or export

So it sits somewhere between a read-it-later app and a real web archive, which is a useful combination if you do research, write, or just hate losing good links.

Why run your own instance

Linkwarden offers a hosted Cloud plan, and it's a fair option if you don't want to manage anything. But self-hosting makes sense for a few reasons.

You own the data. Every screenshot, PDF, and HTML capture lives on your storage, not someone else's, which matters if you're archiving sensitive research, internal documentation, or anything you can't afford to lose access to. There are no per-seat fees either, so adding teammates to a self-hosted instance doesn't change your bill.

Privacy is the other half of it. A self-hosted Linkwarden instance only talks to the sites you're saving and, optionally, an AI provider you choose. Nothing about your reading habits gets shared with a third party. If data privacy is part of why you're self-hosting in the first place, keeping your bookmark archive in-house fits that goal.

What you'll need

Linkwarden's requirements are modest. The developers tested it on a server with 4 GB of memory and it ran smoothly; the heaviest moment is the initial build, and after that it's fairly light. That said, archiving generates real work, since every saved link spins up a headless browser to capture the page, so giving it a little headroom helps if you save in bulk.

For a clean Docker deployment you'll want:

• A Linux server with root access, ideally 4 GB of RAM or more
• Docker and Docker Compose installed
• curl and a text editor like nano

A small VPS handles a single-user instance comfortably. If you plan to archive heavily or run it for a team, a plan with solid CPU and NVMe storage makes the capture process noticeably faster, since screenshot and PDF generation is disk and CPU bound. You'll also need full root access to install Docker and manage the stack, which rules out most shared hosting.

How to self-host Linkwarden with Docker

The official Docker setup is the fastest path, and the project keeps it well documented. The compose file brings up three services together: Linkwarden itself, a PostgreSQL database, and Meilisearch for search.

1. Download the compose and environment files

SSH into your server, then create a folder and pull down the two files you need:

mkdir linkwarden && cd linkwarden
curl -O https://raw.githubusercontent.com/linkwarden/linkwarden/refs/heads/main/docker-compose.yml
curl -L https://raw.githubusercontent.com/linkwarden/linkwarden/refs/heads/main/.env.sample -o ".env"

2. Set your secrets

Open the .env file:

nano .env

You'll see something like this:

NEXTAUTH_URL=http://localhost:3000/api/v1/auth
NEXTAUTH_SECRET=VERY_SENSITIVE_SECRET
MEILI_MASTER_KEY=VERY_SENSITIVE_MEILI_MASTER_KEY
POSTGRES_PASSWORD=CUSTOM_POSTGRES_PASSWORD

You must change three of these to your own secret values: NEXTAUTH_SECRET, MEILI_MASTER_KEY, and POSTGRES_PASSWORD. Each should be a different long, random string. An easy way to generate them is:

openssl rand -base64 32

Run that three times and paste in a fresh value for each. If a value contains special characters, wrap it in single or double quotes.

Leave NEXTAUTH_URL alone for now if you're testing locally. You'll only change it once you put the instance behind a domain, which we'll cover in a moment.

3. Start the stack

From inside the same folder, bring everything up:

docker compose up -d

The first run pulls the images and builds the app, so give it a few minutes. Once it settles, Linkwarden is listening on port 3000.

4. Create your account

Open http://your-server-ip:3000 in a browser and you'll land on the login screen. Click Sign Up to create the first user, using a password of at least eight characters. The first account you make is yours to manage; if this is a single-user setup, you'll likely want to disable open registration afterward in the settings so strangers can't create accounts on your instance.

At this point you have a working Linkwarden. Save a link and watch it generate the screenshot, PDF, and readable view automatically.

Putting it behind a domain

Reaching your instance by IP and port is fine for testing, but for daily use you'll want a real hostname with HTTPS. Run a reverse proxy like Caddy, Nginx, or Traefik in front of Linkwarden, point it at port 3000, and handle TLS there.

Once that's in place, update NEXTAUTH_URL in your .env to match your domain, for example https://links.yourdomain.com/api/v1/auth, then restart with docker compose up -d. If you don't already have a domain for this, you can register one and point an A record at your server. The official reverse proxy docs cover sample configs for the common proxies.

Setting up search and AI tagging

Search works out of the box because Meilisearch ships in the default compose file. As long as your MEILI_MASTER_KEY is set, full-text search across your saved pages just works, including the page content Linkwarden captured, not only titles and tags.

AI tagging is optional and turned off by default. When enabled, it reads the content of a page and suggests or auto-applies tags, which saves a lot of manual sorting once your library grows. You set it up by connecting an AI provider; Linkwarden supports hosted options like OpenAI and Anthropic, or a local model through Ollama if you'd rather keep everything on your own hardware. Running the model locally is the privacy-friendly choice and pairs naturally with a self-hosted setup. The AI tagging guide walks through the environment variables for each provider.

Backing up and updating your instance

Self-hosting means you're responsible for your own safety net, and Linkwarden stores its data in two places: the PostgreSQL database and a data volume holding all the screenshots, PDFs, and HTML captures. A complete backup needs both.

Dump the database with a one-liner you can drop into a cron job:

docker exec -t linkwarden-postgres pg_dump -U postgres postgres | gzip > linkwarden_$(date +%F).sql.gz

Then back up the Docker volume that holds the captured files, since the database alone won't restore your archives. If your captures grow large, copying that volume offsite on a schedule is worth setting up early. Running on infrastructure with daily backups gives you a second layer underneath your own dumps, which is reassuring for an archive you don't want to rebuild from scratch.

Updating is straightforward. From your Linkwarden folder, pull the latest image and recreate the containers:

docker compose pull
docker compose up -d

Check the release notes before a major version jump, but minor updates are usually painless.

Conclusion

Linkwarden turns a fragile pile of bookmarks into a durable, searchable archive you fully control. With Docker, getting it running is a short job: pull two files, set three secrets, and start the stack. From there, adding search, AI tagging, a reverse proxy, and a backup routine rounds it out into something you can trust with years of saved reading.

The main thing self-hosting asks of you is a reliable server with root access and enough resources to handle the archiving work, which is exactly where the right VPS makes the difference.

Thanks for reading! If you're looking for somewhere to host it, QDE offers high-performance VPS hosting in the Netherlands with NVMe storage, 10 Gbps uplinks, and full root access, which suits a self-hosted archiving app like Linkwarden well.

Ready to start or want advice on the right plan? Contact our team and we'll help you find the best fit for your project.

Frequently asked questions about self-hosting Linkwarden

Is Linkwarden free to self-host?

Yes. Linkwarden is open-source, and self-hosting gives you every feature found in the Cloud plan at no license cost. Your only expenses are the server it runs on and, if you use a hosted AI provider, that provider's usage fees.

How much server power do I need?

A VPS with 4 GB of RAM runs a personal instance comfortably. The build step and on-demand page archiving are the most demanding moments, so more CPU and fast NVMe storage speed up screenshot and PDF capture if you save links in volume or run it for a team.

Is Linkwarden a real alternative to the Wayback Machine?

For personal use, yes. It saves full local copies of every page you bookmark as a screenshot, PDF, HTML file, and readable view, so your captures survive even if the original site disappears. It can also push snapshots to the public Wayback Machine, but the local copies are yours regardless.

Do I need Meilisearch for search to work?

The default Docker setup includes Meilisearch, so full-text search works as soon as you set the MEILI_MASTER_KEY value. If search returns nothing, confirm the Meilisearch container is running and the key matches.

Can I keep the AI tagging fully private?

Yes. Instead of a hosted provider, point Linkwarden at a local model running through Ollama on your own server. Page content never leaves your infrastructure, which fits a privacy-focused self-hosted setup.

How do I back up everything?

Back up both the PostgreSQL database, using pg_dump, and the Docker volume that stores the captured screenshots, PDFs, and HTML. The database alone won't restore your archived pages, so you need both for a complete recovery.

Those details matter more than people expect. Where your server physically lives affects latency to your users, which legal framework governs your data, how takedown requests get handled, and what you'll pay each month. This article walks through how Amsterdam and Frankfurt compare on the things that actually move the needle, then helps you decide which one fits your project.

Why these two countries dominate European hosting

Amsterdam and Frankfurt are both part of the "FLAP-D" group, the cluster of cities (Frankfurt, London, Amsterdam, Paris, Dublin) that anchors most of Europe's internet infrastructure. They have the most data centers, the most network operators, and the most interconnection capacity on the continent.

That concentration creates a feedback loop. More networks in one place means lower-latency peering, which attracts more networks, which pulls in more hosting providers and cloud regions. Both cities have been riding that loop for nearly three decades, and it's the main reason a VPS in Amsterdam or Frankfurt tends to outperform one in a less-connected location.

The practical upshot for you: whichever you pick, you're getting access to world-class connectivity. The real question is which flavor of "world-class" suits your audience and your workload.

Network connectivity and peering

This is where the two diverge in an interesting way, and it comes down to their flagship internet exchanges.

Germany's DE-CIX in Frankfurt is the largest internet exchange in the world by peak traffic. Its Frankfurt platform regularly pushes past 18 Tb/s at peak, with roughly 1,100 networks connected at that single metro. Frankfurt is also the gateway for traffic heading into Eastern Europe and a magnet for cloud on-ramps and financial networks, which is part of why DE-CIX named it the world's leading digital hub in 2025.

The Netherlands runs on AMS-IX in Amsterdam, one of the oldest and most respected exchanges anywhere. AMS-IX hit a traffic peak of 14.2 Tb/s in early 2025 and moved more than 35 exabytes of data across the year, with around 900 connected parties. Amsterdam leans heavily toward content delivery, streaming, and gaming traffic, and it sits at the European landing point for several transatlantic cables.

Both exchanges are carrier-neutral and deliver low-latency reach across Europe, North America, and Asia. If you want to dig deeper into how Amsterdam earned its place, we covered it in detail in what AMS-IX is and why it matters.

Latency and geographic reach

Geography is subtle here because both cities are central, but they tilt in different directions.

Frankfurt's strength is reach into the DACH region (Germany, Austria, Switzerland) and onward into Central and Eastern Europe. If most of your users are German-speaking or sit east of the Rhine, Frankfurt usually shaves a few milliseconds off the round trip. It's also the default choice for anything latency-sensitive that touches European financial markets.

Amsterdam tends to win for transatlantic traffic, the UK, the Nordics, and Western Europe generally. The transatlantic cable landings make it a strong base if you serve a mixed European and North American audience from a single location.

In real terms, the gap between them across most of Western and Central Europe is small, often a single-digit millisecond difference. Unless you're running something where every millisecond counts, your audience map matters more than the raw numbers. You can always test real-world latency to a Dutch location yourself using QDE's network looking glass.

Data privacy and legal jurisdiction

Here's where a lot of buyers make their decision, and where the nuance is easy to miss.

Both countries enforce the GDPR, so the baseline for data protection is the same high European standard. Each also has its own national layer on top: Germany has the Federal Data Protection Act backed by a federal authority and 16 separate state-level data protection agencies, while the Netherlands implements GDPR through its own act overseen by the Dutch Data Protection Authority.

Germany has a particularly strong privacy reputation, rooted in a constitutional right to "informational self-determination." German courts have historically pushed back hard on government data collection; the Federal Constitutional Court struck down the country's transposition of the EU data retention directive for being disproportionate. That history gives Germany real credibility with privacy-conscious users.

The Netherlands holds an equally solid GDPR posture with a pragmatic, business-friendly regulator. One detail worth knowing: both Germany and the Netherlands are members of the 14 Eyes intelligence-sharing alliance.

Content rules and takedown culture

This is the difference people feel most in day-to-day operations.

Germany runs a stricter content environment. Its Network Enforcement Act (NetzDG) imposes fast takedown obligations and fines reaching €50 million, though it targets large social platforms rather than hosting providers directly. More relevant to most site owners is Germany's aggressive copyright enforcement and its "Abmahnung" warning-letter culture, where rights holders send formal cease-and-desist notices that can carry real legal cost. Germany also enforces strict rules around certain categories of speech and imagery.

The Netherlands takes a more measured approach. It operates under a well-established notice-and-takedown code of conduct, and Dutch hosts generally have a reputation for being even-handed about handling complaints rather than reflexively pulling content. For projects that need predictable, proportionate handling of abuse reports, that culture is a meaningful advantage.

Neither approach is "better" in the abstract. If your content is mainstream and you value Germany's privacy pedigree, the stricter regime may not affect you at all. If you want a host that won't overreact to a single complaint, the Dutch model tends to be the gentler one.

Pricing and market dynamics

Germany has long been associated with budget-friendly hosting, thanks partly to large domestic providers competing on price and the sheer scale of capacity around Frankfurt. If raw cost-per-gigabyte is your only metric, German bargain tiers can be hard to beat.

The Netherlands competes on a slightly different axis. Dutch hosting is priced competitively, but the country has carved out a strong identity around privacy-focused, crypto-friendly, and unmetered or high-bandwidth offerings. Providers there are more likely to accept anonymous-leaning payment methods and to position around data sovereignty rather than rock-bottom pricing alone.

So the trade-off often looks like this: Germany for maximum capacity at low cost, the Netherlands for a balance of performance, privacy positioning, and flexible payment. For most serious projects, the monthly difference between comparable specs is small enough that connectivity and jurisdiction should outweigh a few euros.

How to choose between the Netherlands and Germany

A few quick decision rules cover most situations.

Pick Germany if your audience is concentrated in the DACH region or Eastern Europe, you want the deepest interconnection at DE-CIX, or you're optimizing purely for the lowest possible cost on large capacity. It's also a natural fit if Germany's constitutional privacy reputation is a selling point for your users.

Pick the Netherlands if you serve a mixed European and transatlantic audience, you run content-heavy, streaming, or gaming workloads that benefit from Amsterdam's peering profile, or you want flexible and privacy-respecting payment options. The lighter-touch content culture is a bonus for anyone who wants predictable handling of complaints.

When the two are close, default to the Netherlands for general-purpose hosting and Germany only when its specific strengths (cost at scale, DACH latency, DE-CIX depth) clearly apply to you. And remember you can always run a short test on a monthly plan before committing, since neither choice locks you in.

Conclusion

The Netherlands and Germany are both excellent places to host, and the right pick depends on your audience, your workload, and how much weight you put on content culture versus raw cost. Germany leans toward unmatched interconnection and budget capacity; the Netherlands leans toward balanced performance, transatlantic reach, and a more flexible, privacy-minded environment.

If the Dutch side of that comparison fits your project, QDE runs unmanaged KVM VPS hosting from a Tier III data center in Amsterdam, with pure NVMe storage, 10 Gbps uplinks, direct AMS-IX peering, and crypto payment options for anyone who values privacy. RAM and storage are never oversold, so you get exactly what your VPS plan lists.

Not sure which location or spec fits best? Contact our team and we'll help you find the right setup for your project.

Frequently asked questions about Netherlands vs. Germany hosting

Is the Netherlands or Germany better for privacy?

Both enforce GDPR and have strong national data protection laws, so the baseline is equally high. Germany carries a stronger privacy reputation thanks to its constitutional protections, while the Netherlands pairs solid GDPR compliance with a pragmatic regulator and flexible, privacy-friendly payment options. Note that both countries belong to the 14 Eyes alliance.

Which has better network connectivity?

Germany's DE-CIX in Frankfurt is the world's largest internet exchange by peak traffic and the strongest gateway into Eastern Europe. The Netherlands' AMS-IX in Amsterdam is one of the largest globally and excels for transatlantic, streaming, and content delivery traffic. Both offer low-latency reach across Europe.

Is German hosting cheaper than Dutch hosting?

German hosting is often associated with lower budget pricing due to large domestic providers and heavy capacity around Frankfurt. Dutch hosting is competitively priced but tends to emphasize performance, privacy, and flexible payment rather than the absolute lowest cost.

Does Germany censor hosted content more than the Netherlands?

Germany has a stricter content environment, including fast takedown rules for large platforms and aggressive copyright enforcement. The Netherlands uses a notice-and-takedown code of conduct and is generally known for proportionate, even-handed handling of complaints.

Which should I choose for a European and US audience?

The Netherlands is usually the better default for a mixed European and transatlantic audience because of Amsterdam's transatlantic cable connections and content-friendly peering. Choose Germany if your users are concentrated in the DACH region or Eastern Europe.

Can I test latency before committing?

Yes. You can check real-world latency to a Dutch location using QDE's network looking glass, and since QDE bills monthly with no long-term contract, you can run a short trial before deciding.

By the end you'll have Immich running with Docker Compose, your phone backing up automatically in the background, and a plan for keeping the whole thing backed up properly. None of it is complicated, but a couple of steps are easy to get wrong, so it's worth following along carefully.

Why Immich is the best Google Photos alternative

Self-hosted photo managers have existed for years, but most asked you to give up the features that made Google Photos worth using. Immich doesn't. It ships polished iOS and Android apps with automatic background backup of your camera roll, a fast scrolling timeline, shared albums, a map view, and on-device machine learning for face grouping and natural-language search. You can type "dog on the beach" and actually get the right photos back, with all of that processing happening on your own server rather than in a data center you don't own.

The project is also one of the fastest-moving in the self-hosting world. It crossed 100,000 stars on GitHub, reached a stable 2.0 release in late 2025, and continues to ship regular updates. That pace is a feature, but it comes with one important caveat: things can change between versions, so pinning a release and reading the release notes before upgrading is part of the deal. More on that later.

The privacy math is the real draw. When you self-host, your photos never touch a third party. There's no scanning, no quotas beyond your own disk, and no policy change that can lock you out of a decade of memories. For anyone in the EU, you also become both the data controller and processor for your own library, which sidesteps a lot of the GDPR complexity that comes with handing personal media to a cloud provider.

What you'll need before you start

Immich runs on Linux only, and it expects a few things to be in place:

• A Linux server (Ubuntu 22.04/24.04, Debian, or Rocky all work fine) with Docker Engine and the Docker Compose plugin installed.
• At least 2 CPU cores and enough RAM that the machine learning container is comfortable. 4 GB is a workable floor, 6 GB is a better starting point, and 8 GB or more is sensible once your library grows.
• Storage with room to grow. Plan for the size of your raw photo library, plus 10 to 20% overhead for thumbnails and transcoded video, plus 1 to 3 GB for the PostgreSQL database.

NVMe storage makes a real difference here, since Immich does a lot of thumbnail generation and database work that benefits from fast random I/O. A VPS is a natural fit for Immich if you want your photos reachable from anywhere without leaving a machine running at home, which is exactly the kind of workload covered in our self-hosted apps use cases.

What's inside the Immich stack

Immich isn't a single container. The official Docker Compose file defines four services that work together, and it helps to know what each one does:

• immich-server handles the web interface, the API, and the endpoint your mobile apps talk to. It publishes port 2283.
• immich-machine-learning runs the face recognition and smart search models. It's a separate container so you can give it more resources or hardware acceleration independently.
• redis (actually a Valkey image) is the in-memory store for job queues and caching.
• database is a PostgreSQL image built by the Immich team with the VectorChord and pgvector extensions that power similarity search. Immich needs this specific image; a stock Postgres won't work.

You don't write any of these definitions yourself. You download a maintained Compose file from the project, which keeps everything wired together correctly even as the stack changes.

Step 1: Prepare a directory

Assuming Docker and the Compose plugin are already installed, make a dedicated directory for Immich and move into it:

mkdir -p ~/services/immich
cd ~/services/immich

Keeping each self-hosted service in its own directory makes backups and updates much easier to reason about later.

Step 2: Download the official compose file

Pull the two files Immich publishes with every release, the Compose file and the example environment template:

wget -O docker-compose.yml https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
wget -O .env https://github.com/immich-app/immich/releases/latest/download/example.env

These are the exact commands from Immich's official documentation. Downloading the maintained file rather than copy-pasting a snippet from a random blog post is the right move, because the released file is always internally consistent with the image versions it references.

Step 3: Configure your environment file

Open .env in your editor of choice and set the variables that matter:

# Where your uploaded photos and videos live on the host
UPLOAD_LOCATION=./library

# Where the Postgres database files live on the host
DB_DATA_LOCATION=./postgres

# Your timezone
TZ=America/Chicago

# Pin a specific version instead of tracking "release"
IMMICH_VERSION=release

# Database credentials, change the password to something random
DB_PASSWORD=postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

Two things deserve attention here. First, change DB_PASSWORD to a long random string before you ever start the stack. Changing it after the database is initialized means migrating data, which is a headache you can avoid entirely with thirty seconds of planning.

Second, pin IMMICH_VERSION to a specific tag, for example a value like v2.7.5, rather than leaving it on release. Immich moves quickly, and a major version such as the upcoming v3.0 can remove older features. Pinning means an update only happens when you decide it should, after you've read what changed.

UPLOAD_LOCATION is the single most important setting in the file. It's the directory that holds every photo you back up, so put it on a disk with plenty of headroom and make sure it's part of your backup plan from day one.

Step 4: Start Immich

From inside ~/services/immich, bring the stack up:

docker compose up -d

Docker pulls the four images and starts them in order. The first launch takes a few minutes while the database initializes, so don't panic if the web interface isn't immediately available. You can watch progress with:

docker compose logs -f immich-server

Once the server reports it's ready, open http://your-server-ip:2283 in a browser. You'll land on the admin registration page. The first account you create is the administrator, so set it up, log in, and you'll be looking at an empty timeline waiting for photos.

Step 5: Set up mobile backup

This is the feature that actually replaces Google Photos. Install the Immich app from the App Store or Google Play, then point it at your server.

On the login screen, enter your server URL. On your local network that's http://your-server-ip:2283. Once you've set up a reverse proxy with a real domain (covered below), you'll use the HTTPS address instead. Log in with the account you created, open the app's backup settings, choose the albums you want backed up (usually your camera roll), and enable background backup.

The app keeps track of which photos are already uploaded, so it's safe to let it run continuously. It uploads new photos in the background as you take them, which is exactly the behavior you're used to from Google Photos.

Step 6: Migrate your existing library

New photos are handled by the app, but you'll also want to bring over everything already sitting in Google's cloud. Use Google Takeout to export your existing library, then upload the export through the Immich web interface or the immich-cli bulk uploader. For large archives the command-line uploader is faster and easier to resume if it gets interrupted.

Step 7: Hardware acceleration (optional)

Two parts of Immich speed up with hardware acceleration: the machine learning container that handles face recognition and search, and the video transcoding that happens on the server container. Immich ships separate Compose override files for this, which you download alongside the main file. The exact configuration depends on whether you have Intel QuickSync, an NVIDIA GPU, or another accelerator, and it's documented in detail on the Immich hardware acceleration page.

If you're running on CPU only, Immich still works perfectly well. Machine learning jobs simply take longer to process, which matters during the initial import and then barely at all once your library is indexed and only keeping up with new photos.

Step 8: Put Immich behind a reverse proxy

To reach Immich from outside your network and to let the mobile app connect over HTTPS, put it behind a reverse proxy pointed at the server container's port 2283. Caddy, Traefik, and Nginx all handle this well. Photo and video uploads can be large, so make sure your proxy doesn't impose a small request-size limit; with Nginx you'll want to raise client_max_body_size, while Traefik has no default cap.

Because your entire photo history is sensitive, think carefully about exposure. If you don't actually need public access, keeping Immich reachable only over a VPN like WireGuard or Tailscale is the safer posture, and the mobile app connects to a private hostname just as happily as a public one. Either way, running it on infrastructure with strong privacy and data protection practices matters when the data in question is your family photos.

Step 9: Back up your library and database

This is the step you cannot skip. A complete Immich backup is two things, and you need both:

• The upload library, your UPLOAD_LOCATION directory, which holds the actual photo and video files.
• The database, which stores your faces, albums, metadata, and the mapping that makes the library navigable. Dump it on a schedule with pg_dump from the database container.

A library backup without the database leaves you with a folder of files and no organization. A database backup without the files leaves you with metadata pointing at nothing. Apply a real 3-2-1 backup strategy here above any other service you run, because the cost of getting it wrong is irreplaceable. Server-level daily backups are a good safety net, but they don't replace your own off-site copies of something this important.

Keeping Immich updated

Because you pinned IMMICH_VERSION, upgrading is a deliberate act rather than something that happens by surprise. Read the release notes for the version you're moving to, confirm your backup just ran, bump the version tag in .env, then pull and recreate:

docker compose pull
docker compose up -d

Database migrations run automatically on start. Reading the release notes and keeping the version pinned is what keeps Immich's fast development pace from catching you off guard.

Closing thoughts

Self-hosting Immich gives you a faster, private, ad-free photo timeline that does face recognition and smart search locally, backs up your phone automatically, and stores everything on disks you control. It's one of the most satisfying self-hosted swaps you can make, and also the one where good backups matter most.

Thanks for reading! If you're looking for somewhere to run it, QDE provides high-performance VPS hosting in the Netherlands with pure NVMe storage, 10 Gbps uplinks, and EU-based infrastructure, which is a solid match for a privacy-focused photo server. RAM and storage are never oversold, so the resources Immich needs are the resources you actually get, and crypto payment options make it easy to keep the whole setup private.

Ready to get started or want advice on sizing a VPS for Immich? Contact our team to find the best fit for your project.

Frequently asked questions about self-hosting Immich

Is Immich a good replacement for Google Photos?

Yes, for most people it's the closest self-hosted equivalent available. It offers automatic mobile backup, face recognition, natural-language search, shared albums, and a map view, all running on your own hardware with no scanning and no storage quotas beyond your own disk.

What are the system requirements for Immich?

Immich runs on Linux with Docker. Plan for at least 2 CPU cores and 4 GB of RAM as a floor, with 6 to 8 GB recommended once your library grows. Storage should cover your raw library plus 10 to 20% overhead for thumbnails and transcodes, plus 1 to 3 GB for the database.

Can I run Immich on a VPS?

Absolutely, and a VPS is a great fit if you want your photos reachable from anywhere without keeping hardware running at home. A plan with NVMe storage and enough RAM for the machine learning container will give you a smooth experience.

Do I need a GPU for Immich?

No. A GPU speeds up the initial machine learning indexing and video transcoding, but Immich works fine on CPU-only servers. The ML jobs just run more slowly, which mainly affects the first import rather than day-to-day use.

How do I back up Immich properly?

Back up two things: your upload library directory and the PostgreSQL database. The files are your photos, and the database holds the albums, faces, and metadata that organize them. You need both, plus off-site copies, following a 3-2-1 backup approach.

How do I move my existing Google Photos library into Immich?

Use Google Takeout to export your library, then upload it through the Immich web interface or the command-line bulk uploader. The CLI uploader is the better option for large archives because it's faster and easy to resume.

The part after the final dot, the top-level domain or TLD, does more work than it looks. .com, .net, and .org carry expectations that have built up over decades. This article explains why those classic extensions are still the safest default for most businesses and long-term projects, when an alternative makes sense, and why QDE protects its own brand across all three.

Why the classic extensions still matter

People trust what they recognize. .com, .net, and .org have been in front of users since the early commercial internet, so most people read them without a second thought. Someone who sees a .com address rarely stops to wonder whether it belongs to a real company or a disposable site. That absence of friction is the point.

The scale of these extensions reflects how established they are. According to the Domain Name Industry Brief for Q1 2026, .com and .net together held 176.1 million domain name registrations at the end of Q1 2026. That number matters for a practical reason beyond popularity: the infrastructure behind these TLDs is among the most mature and heavily operated parts of the global DNS system.

The authoritative name servers for .com and .net have operated at global scale for decades and sit close to the core of the internet. We will not call them the most reliable DNS on earth, because no one can prove that. But they are backed by long-running infrastructure that has handled enormous query volumes for a very long time. For projects where DNS stability matters, that track record counts.

This is where the choice stops being cosmetic for infrastructure teams. If you run hosting, a VPS fleet, an email service, a SaaS platform, a billing portal, or a support system, your domain is part of the service path. If it fails to resolve, customers cannot reach the app, mail does not deliver, invoices do not load, and tickets do not get opened.

There are two good reasons to take the classic extensions seriously: users trust what they recognize, and operators should care about the operational maturity behind the name.

.com: the default for businesses

For a company, .com is still the most natural choice. It is what people expect from a commercial site, a SaaS product, an online store, a hosting provider, or business email. When someone remembers your brand but not your exact address, example.com is the pattern they are likely to try first.

If you can only secure one extension for a serious business, .com is usually the safest. It is the version customers will guess, type, and trust by default.

The hidden cost of not owning your .com

This part is easy to underestimate. Because .com is so common, many people assume a brand lives at example.com whether or not that's true. If your business runs on another extension and someone else holds the .com, some of your traffic quietly goes to them.

There are two versions of this, and both are bad.

In the first, the .com belongs to another company in your industry. This is the clearest risk: a potential customer trying to find you lands on a competitor instead. You paid to build the recognition, and someone else receives the visit.

In the second, the .com belongs to an unrelated business. That sounds harmless, but it still costs you. Customers wonder whether they typed the wrong thing, whether your site is the real one, or why the obvious address points somewhere else. For anyone handling accounts, billing, servers, DNS, or support, that hesitation chips away at trust at the wrong moment.

Not owning the .com version of your brand means someone else may control the most obvious destination for your name. Even when you build on a different extension by choice, registering the matching .com is cheap insurance.

.net: a natural fit for networks and infrastructure

.net is not only a fallback when the .com is taken. It has its own meaning. The extension grew up around networks, and it is still widely read as a technical, infrastructure-oriented choice.

It fits hosting providers, VPS services, DNS platforms, network and monitoring tools, API services, and developer-facing projects. If your product lives close to the wire, a .net can read as credible rather than second-best. Plenty of well-known infrastructure companies use .net for exactly that reason.

.org: trusted for communities and organizations

.org carries a different association. People connect it with organizations, communities, open-source projects, documentation, foundations, and public-interest work.

Technically, .org is open to anyone. There is no requirement to be a nonprofit. But the perception is sticky, and that can work in your favor. If you run an open-source project, a community forum, a documentation site, a public knowledge base, or an industry group, .org signals the kind of project people already expect it to be.

Where unusual extensions create friction

New TLDs are not bad as a category. Some are genuinely useful, and we will get to where they fit. But a few practical risks are worth knowing before you put one on your main site.

Some users simply don't recognize the extension, and unfamiliarity invites doubt. A handful of TLDs have picked up a reputation for spam, throwaway sites, or aggressive advertising — unfair to legitimate users, but real. Pricing can also surprise you: a cheap first year sometimes hides a much higher renewal, and some registries carry premium fees or change their policies over time.

There is an operational angle too. A domain used for email, billing, or login pages should avoid anything that creates confusion. An address that looks strange can generate support tickets and lower conversion, and some corporate networks, mail filters, and anti-abuse systems treat unfamiliar or heavily abused TLDs more cautiously.

The simple test: a domain that needs extra explanation usually isn't the right domain for a main business website.

When an alternative extension is the right call

There are good reasons to pick something other than the classics, as long as it is a deliberate choice.

.ai has become a sensible fit for AI products. .io is well understood among developer audiences and works when that is who you are trying to reach. Country-code domains like .de, .nl, .jp, or .uk are often the right move when you serve a specific local market. Short extensions can be useful for URL shorteners, while campaign domains, landing-page domains, brand-protection registrations, and internal or secondary projects all have their place.

The deciding factor is strategy. Choose an alternative because it fits your audience and your plan, not only because the .com was unavailable or the first year was cheap.

Why we acquired qde.com, qde.net, and qde.org

This is also why we acquired and protect our own brand across all three classic extensions. For us, it is not about collecting domain names. It is about making sure customers can find the real QDE.

Owning qde.com, qde.net, and qde.org reduces confusion, keeps the brand consistent across the extensions people are most likely to try, and protects against traffic leakage, impersonation, and misuse. It is the same advice we would give any customer running a brand they care about.

QDE now offers .com, .net, and .org registration

With that in mind, QDE now offers .com, .net, and .org domain registration directly.

The practical benefit is keeping your domains and hosting in one place. You can register a name, point it at your VPS or website, manage DNS, and handle renewals from the same account you already use for your servers, without juggling a separate registrar login. It suits business sites, infrastructure projects, communities, and anything you plan to run for the long term.

Conclusion

A domain extension won't turn a weak project into a strong one. But the right one makes a good project easier to trust, remember, and find — and the wrong one quietly adds friction every time someone reads your address.

Unless you have a clear reason to choose something else, start with .com, .net, or .org. For most serious projects, the safest domain choice is still the one customers already understand.

If you are ready to register a name, QDE now offers .com, .net, and .org domains for €10.95 per year, managed from the same account as your VPS and hosting.

Have questions about domains, DNS, or pointing a name at your server? Reach out to our team and we will help you choose a practical setup.

Frequently asked questions about domain extensions

Is .com still the best domain extension for a business?

For most businesses, yes. .com is the extension people recognize, remember, and type by default, which makes it the safest choice for a commercial site, SaaS product, or business email. If you can only register one extension, .com is usually the one to secure first.

What's the difference between .com, .net, and .org?

All three are open for anyone to register, but they carry different associations. .com reads as commercial and is the general-purpose default. .net is widely read as technical and infrastructure-oriented. .org is associated with organizations, communities, and open-source or public-interest projects. The technical behavior is broadly the same; the difference is in how users perceive them.

Should I register more than one extension for my brand?

It's worth considering. Owning the .com version of your brand prevents traffic from leaking to whoever else holds it, even if you build on a different extension by choice. Many businesses register .com, .net, and .org together as basic brand protection.

Are new domain extensions like .io or .ai a bad idea?

No. Extensions like .io and .ai can be good choices when they fit your audience and strategy: .ai for AI products, .io for developer-facing tools. The caution is against choosing an unfamiliar extension only because the .com was taken or the first year was cheap, especially for a main business site.

Can I manage a domain and hosting in the same place?

Yes. QDE now offers .com, .net, and .org registration alongside its VPS and hosting, so you can register a domain, manage DNS, point it at your server, and handle renewals from one account. You can read more on the domains page.

This article breaks down each location across the factors that actually matter for hosting: network connectivity, latency profiles, legal and regulatory environment, and overall ecosystem maturity.

Why location matters more than most people think

Choosing a data center location isn't just about ping times, though those matter. It also determines which jurisdiction governs your data, which peering agreements your traffic benefits from, and how resilient your infrastructure is to regional events. Getting this right at the start saves a lot of headache later.

Amsterdam: the connectivity hub of Europe

Amsterdam has built its reputation on network infrastructure. AMS-IX, the Amsterdam Internet Exchange, consistently ranks among the top two or three internet exchanges in the world by traffic volume. What this means practically is that traffic originating in Amsterdam reaches most of Europe, North America, and large parts of Asia through very short paths, with minimal intermediate hops.

For hosting providers and their customers, this translates to consistently low latency across a wide geographic area, not just within the Netherlands. A server in Amsterdam often performs comparably to local servers for users across much of Western and Central Europe.

Amsterdam also has a strong history as a neutral, carrier-dense location. Dozens of major ISPs and cloud providers maintain a presence at AMS-IX, which makes it easy to find diverse connectivity options and competitive pricing on transit.

From a legal standpoint, the Netherlands is firmly within the EU and falls under GDPR. Dutch privacy law is generally considered robust, and the country has a track record of supporting digital rights. For businesses handling EU user data, Amsterdam is a clean, defensible choice.

Frankfurt: the financial and backbone hub

Frankfurt is Germany's network heart, anchored by DE-CIX, the Deutsche Commercial Internet Exchange. DE-CIX regularly competes with AMS-IX for the title of the world's highest-traffic internet exchange. The city is the primary interconnection point for much of Central and Eastern Europe, and it has deep redundancy thanks to Germany's extensive domestic fiber infrastructure.

For latency into Germany itself and neighboring countries like Austria, Switzerland, Poland, and Czech Republic, Frankfurt generally wins. If your primary user base is in the DACH region or Central Europe more broadly, it's hard to argue against Frankfurt as the anchor location.

Germany also benefits from some of the strictest data protection regulations in the EU. The combination of federal GDPR compliance and additional German state-level data protection laws (such as the BDSG) gives Frankfurt an edge for enterprises in regulated industries like finance, healthcare, and legal services. German courts and regulators have historically been aggressive about enforcing data protection, which is both a reassurance and an obligation depending on your perspective.

One consideration worth noting: German hosting providers tend to operate on stricter abuse policies, which can affect certain types of content. It's generally a non-issue for standard business and technical workloads, but worth knowing.

London: post-Brexit complexity with strong infrastructure

London's Docklands area, particularly the Equinix LD4/LD5 campus in Slough and the broader cluster in East London, is one of the most dense concentrations of hosting and financial infrastructure anywhere in the world. LINX (London Internet Exchange) is itself a major exchange with very high capacity and strong peering across UK and international networks.

The infrastructure quality in London is genuinely excellent. If your workload is primarily serving UK users, or if you need to be physically close to London's financial district for latency-sensitive trading or fintech applications, London delivers.

The complication is Brexit. Since the UK left the EU in 2020, it is no longer part of the European Economic Area. Data transfers between the UK and EU now rely on an adequacy decision granted by the European Commission, which provides a legal basis for transfers but introduces regulatory uncertainty that wasn't there before. The adequacy decision can, in principle, be challenged or revised. For businesses that need long-term certainty about EU data handling, this is a real risk to model.

UK data protection law (UK GDPR, derived from the EU original) is largely equivalent in practice today, but the divergence risk over time is real. London works well for UK-centric operations. For EU data sovereignty, it requires more care.

How the three compare side by side

Network performance across a broad European audience slightly favors Amsterdam, with Frankfurt a close second for Central and Eastern Europe. London leads for UK-specific traffic.

Latency to North America is broadly similar across all three, though Amsterdam's transatlantic cable connections and Frankfurt's backbone position both offer strong options.

Regulatory simplicity for EU operations goes to Amsterdam and Frankfurt, both of which sit squarely within EU jurisdiction without qualification. London requires additional legal structuring for strict EU data compliance.

Data center density and choice is very high in all three, though London's ecosystem is particularly deep in financial services infrastructure.

Cost varies by provider and configuration more than by city, but London tends to be somewhat more expensive on average due to real estate and power costs. Amsterdam and Frankfurt are competitive with each other.

Which one should you choose?

For most general-purpose hosting serving a broad European audience, Amsterdam is the strongest default. The combination of AMS-IX peering, straightforward EU legal standing, and competitive pricing covers the majority of use cases well.

If your workload is specifically targeting Germany, Austria, Switzerland, or Central Europe, Frankfurt's geography and DE-CIX connectivity make it the right call. It's also the better pick if you're in a regulated industry that benefits from Germany's rigorous data protection posture.

London is the right choice when your primary audience is in the UK, or when you're building something that needs to be adjacent to UK financial infrastructure. Just make sure your legal and compliance team has reviewed the post-Brexit data transfer implications before committing.

For teams that need low-latency access to multiple European regions from a single location, Amsterdam remains the most consistently strong choice. Its position at AMS-IX means fewer tradeoffs when you're trying to serve users across multiple countries from one server.

Conclusion

Amsterdam, Frankfurt, and London are all world-class hosting locations, but each has a distinct profile. Amsterdam wins on breadth of European connectivity and regulatory simplicity. Frankfurt is the right pick for Central Europe and regulated enterprise use cases. London is powerful for UK-focused infrastructure but adds legal complexity for EU data handling.

Thanks for reading! If you're looking for a well-connected European base for your server, QDE offers high-performance VPS in Amsterdam, hosted in a Tier III data center with direct peering at AMS-IX, NVMe storage, and 10 Gbps uplinks.

Ready to get started or want to talk through your setup? Contact our team and we'll help you find the right fit.

Frequently asked questions about EU hosting locations

Why is Amsterdam so popular for hosting?

Amsterdam sits at AMS-IX, one of the world's largest internet exchanges. This gives servers there low-latency access to a huge portion of European, North American, and Asian traffic through well-peered routes. The Netherlands also has a stable regulatory environment and a long history of neutral, carrier-diverse hosting infrastructure.

Is London still a good hosting location after Brexit?

London remains excellent infrastructure, particularly for UK-facing workloads and fintech applications. However, the UK is no longer part of the EU, so data transfers between UK-hosted servers and EU users now rely on an adequacy decision rather than automatic GDPR compliance. For businesses with strict EU data sovereignty requirements, Amsterdam or Frankfurt are cleaner options.

How does Frankfurt compare to Amsterdam for latency?

For users in Germany, Austria, Switzerland, and Central or Eastern Europe, Frankfurt often has an edge due to its geographic position and DE-CIX peering. For broader pan-European coverage, including Southern Europe and the UK, Amsterdam tends to be more consistently low-latency. The difference for most workloads is measured in single-digit milliseconds.

Does data center location affect GDPR compliance?

Yes, meaningfully. Servers in Amsterdam and Frankfurt are both within EU jurisdiction, meaning GDPR applies directly and there's no need for additional data transfer mechanisms. London, post-Brexit, requires a separate legal basis (currently an EU adequacy decision) for transferring personal data from EU users to UK infrastructure. The adequacy decision is valid for now but could change.

What should I prioritize when choosing a European hosting location?

Start with your primary user base. Match the server location to where the majority of your traffic comes from, since geographic proximity reduces latency. Then consider regulatory requirements: if EU data sovereignty is non-negotiable, stay within the EU. Finally, look at the connectivity profile of the specific data center and provider, not just the city.

This article walks through the key laws that apply, what they mean in practice for hosting customers, and how to think about your obligations whether you're running a SaaS product, a community forum, an internal business tool, or beyond.

The GDPR: the foundation everything builds on

The General Data Protection Regulation (GDPR) — known in the Netherlands as the AVG, short for Algemene Verordening Gegevensbescherming — is the baseline. It's an EU regulation, which means it applies directly in all member states without needing to be translated into local law. If you process personal data of EU residents, it applies to you, regardless of where your business is registered.

The GDPR rests on a handful of core principles: you need a lawful basis to process personal data, you should only collect what's necessary, you must store it securely, and you can't keep it indefinitely. It also grants individuals a set of rights — access, correction, deletion, portability — that you're obligated to support.

For hosting customers, the most relevant piece is the controller-processor relationship. If your hosting provider touches personal data on your behalf (which is common), you need a Data Processing Agreement (DPA) in place. This agreement must set out the subject matter and duration of the processing, the nature and purpose of the processing, the type of personal data involved, and the obligations and rights of the controller.

The UAVG: where Dutch law adds its own layer

The Dutch GDPR Implementation Act (Uitvoeringswet AVG, or UAVG) constitutes the local implementation of the GDPR in the Netherlands. It follows a policy-neutral approach, meaning the requirements of the previous Dutch Data Protection Act are maintained insofar as possible under the GDPR.

In practical terms, the UAVG fills in the gaps where the GDPR intentionally leaves room for member states to legislate. Among other things, the UAVG sets the age of digital consent at 16, refines GDPR provisions governing employment relationships, and adds further safeguards for processing special categories of personal data.

If your application processes data from Dutch users — especially minors — that age-of-consent rule matters. You can't rely on parental consent workarounds that might be acceptable in other jurisdictions.

The Autoriteit Persoonsgegevens: who enforces it

The Dutch Data Protection Authority (Autoriteit Persoonsgegevens, or AP) is the national regulatory authority on all things data protection. It handles enforcement, investigates complaints, and has the power to issue fines.

Those fines follow the GDPR's two-tier structure. Violations of organizational obligations — such as failing to appoint a Data Protection Officer, failing to maintain records of processing activities, or failing to conduct a Data Protection Impact Assessment — can result in fines up to EUR 10 million or 2% of global annual turnover. Violations of core data protection principles, such as processing data without a legal basis or violating data subject rights, can go up to EUR 20 million or 4% of global annual turnover.

The AP doesn't just sit idle. For 2024 and 2025, the AP identified four strategic enforcement priorities, including algorithms and artificial intelligence, addressing automated decision-making risks. That's worth noting if your application uses any form of profiling or automated decisions that affect users.

What counts as personal data

This is where a lot of hosting customers trip up. Personal data isn't just names and email addresses. It includes customer and personnel numbers, internet purchasing behaviour, trade union membership, religion, medical information, and video and sound recordings on which a person can be recognised.

IP addresses stored in server logs are also generally considered personal data under GDPR, which means your standard web server access logs could put you in scope if you're not careful about retention periods and access controls.

Lawful bases for processing

You cannot just process personal data — you must have at least one of six recognized reasons: it is necessary to carry out an agreement, it is necessary to fulfill a legal obligation, there is a legitimate interest, you have permission from the person in question, it is necessary to protect someone's life or health, or it is necessary to perform a task in the public interest.

For most commercial applications, the relevant bases are contract (processing data to deliver a service the user signed up for) and consent (for anything beyond that, like marketing). Legitimate interest can apply in some cases, but it requires a balancing test and can't be used as a catch-all.

Data breach notification rules

If something goes wrong — a breach, unauthorized access, accidental exposure — you have limited time to act. Under the GDPR, you must notify the AP within 72 hours of becoming aware of a breach that poses a risk to individuals. Depending on the severity, you may also need to notify the affected users directly.

This is one area where your hosting setup matters. If you're on an unmanaged VPS, you control the stack, which means breach response is your responsibility. Having monitoring in place, maintaining access logs, and knowing who can reach your data are all part of being prepared.

Transferring data outside the Netherlands

Transferring personal data outside the European Economic Area requires adequate safeguards under Chapter V of the GDPR. Data may flow freely to countries the European Commission has recognized as providing adequate protection, including Japan, the United Kingdom, and the United States under the EU-US Data Privacy Framework.

For any country without an adequacy decision, you'll typically need Standard Contractual Clauses (SCCs). If your application uses third-party services — analytics, CDN providers, email delivery — check whether those vendors process EU personal data and what transfer mechanisms they rely on. Many hosting customers overlook this when integrating external APIs.

What this means for your hosting setup

Choosing to host in the Netherlands carries a few practical advantages from a compliance standpoint. Your data stays in the EU, you're subject to well-defined GDPR enforcement, and there's no ambiguity about jurisdiction for most use cases. You don't need to worry about cross-border transfers for EU users as long as processing stays within the EEA.

That said, the server location doesn't do the compliance work for you. You still need to:

• Have a privacy policy that clearly states what you collect and why
• Implement a Data Processing Agreement with any processor handling personal data on your behalf
• Only collect data that's actually necessary for your service
• Have a process for handling data subject requests (access, deletion, correction)
• Maintain records of your processing activities if you're not a small business operating below GDPR thresholds

You should not keep personal data for longer than necessary. Only a very limited number of people in your company should have access to this data, and you may have to carry out a Data Protection Impact Assessment (DPIA) to assess the risks of data processing.

A note on the Dutch Telecommunications Act

Chapter 11 of the Dutch Telecommunications Act implements the requirements of the ePrivacy Directive, which provides a specific set of privacy rules for the processing of personal data in electronic communications. This is primarily relevant if you're operating a communications platform or if your site uses tracking technologies like cookies.

In November 2025, the Dutch Data Protection Authority updated Dutch cookie banner guidelines. Opt-in consent is required for non-essential cookies such as tracking or marketing cookies. Prior consent is mandatory. If your application or website runs any non-essential analytics or advertising, you need a properly structured consent mechanism — a banner that pre-checks consent boxes or makes refusal harder than acceptance won't cut it.

Conclusion

Hosting in the Netherlands means operating under one of the more clearly defined privacy frameworks in the world. GDPR provides the foundation, the UAVG adds Dutch-specific requirements, and the AP enforces both with real consequence. Understanding where your obligations lie — particularly around lawful bases, data processing agreements, breach notification, and cross-border transfers — is what keeps you on the right side of it.

Whether you're building a customer-facing product or running internal infrastructure, the fundamentals apply: collect less, document more, secure everything, and know how to respond when something goes wrong.

Thanks for reading! If you're looking for a compliant, privacy-conscious hosting base in the Netherlands, QDE provides high-performance VPS hosting in Amsterdam, backed by NVMe storage, 10 Gbps uplinks, and a GDPR-compliant infrastructure with minimal data collection and no third-party data sharing.

Ready to get started or have questions about your setup? Contact our team — we're happy to help you find the right plan for your project.

Frequently asked questions about Netherlands data privacy laws and hosting

Does Netherlands hosting automatically make me GDPR compliant?

No. Hosting your data in the Netherlands means it stays within the EU and avoids cross-border transfer issues for most use cases, but compliance is determined by how you collect, process, and manage personal data — not where the server sits. You still need lawful bases, processing agreements, a privacy policy, and breach response procedures in place.

What is the UAVG and how is it different from GDPR?

The UAVG (Uitvoeringswet AVG) is the Dutch law that implements and supplements the GDPR locally. The GDPR applies directly across all EU member states, but it leaves certain areas open to national legislation. The UAVG fills those gaps, including setting digital consent age at 16 and adding extra rules for special categories of data and employment contexts.

Who enforces data privacy law in the Netherlands?

The Autoriteit Persoonsgegevens (AP) is the Dutch Data Protection Authority. It handles enforcement of both the GDPR and the UAVG, investigates complaints, and can issue fines up to EUR 20 million or 4% of global annual turnover for serious violations.

Do I need a Data Processing Agreement with my VPS provider?

If your VPS provider processes personal data on your behalf — even incidentally, such as through log access or backup systems — yes, a DPA is required under GDPR Article 28. Check your provider's terms or ask them directly whether they offer a DPA. QDE can provide this.

What is a Data Protection Impact Assessment (DPIA) and when do I need one?

A DPIA is a formal risk assessment for processing activities that are likely to result in high risk to individuals — such as large-scale profiling, processing special categories of data, or systematic monitoring. If your application does any of these things, a DPIA may be mandatory before you go live.

What overselling means in VPS hosting

Overselling is when a hosting provider allocates more resources than the physical hardware actually has. The logic behind it is borrowed from the airline industry: not every passenger will show up, so you sell more seats than the plane holds. Applied to hosting, not every customer will use their full allocation at the same time, so you can theoretically fit more VPS instances on a single server than the specs would otherwise allow.

With traditional shared hosting, this is almost universally accepted. But with VPS hosting, the premise is different. Customers pay for dedicated, isolated resources, and overselling undermines that expectation entirely.

How RAM overselling works

RAM is the easiest resource to oversell, and it's extremely common. A provider might have a physical host with 256 GB of RAM but provision VPS instances that collectively add up to 512 GB or more. When usage is low, this works fine. When multiple tenants start consuming their allocated RAM simultaneously, the host runs out of physical memory and starts swapping to disk, or worse, starts killing processes via the OOM (out-of-memory) killer.

What this looks like on your end: your application suddenly crashes, services restart unexpectedly, or everything grinds to a near halt. These events can look like bugs in your software when the real cause is the host running out of physical memory.

Some providers use memory ballooning techniques in their hypervisors to dynamically reclaim unused RAM from idle VMs. This is slightly more honest than raw overselling, but it still means your allocated memory isn't guaranteed.

How CPU overselling works

CPU is a bit more nuanced. Modern hypervisors let providers assign more vCPUs to virtual machines than the physical host has logical cores. A server with 64 physical threads might have 200 vCPUs allocated across its VMs. As long as most VMs are idle, the scheduler can handle it.

The problem surfaces under load. If several tenants start running CPU-intensive workloads simultaneously, they're all competing for the same physical threads. The hypervisor scheduler has to time-slice aggressively, and your tasks get queued. This shows up as CPU steal time, which is the percentage of time your vCPU is waiting for physical CPU access that the hypervisor isn't giving it.

High steal time is a reliable signal that your host is overselling CPU. Tools like top, vmstat, or sar expose the "st" column in Linux, which shows steal directly. If you're seeing consistent steal above 5-10%, your VPS is sharing more than it should.

How storage overselling works

Storage overselling follows the same pattern. Providers provision more total disk space across VMs than their storage arrays physically hold, assuming that most customers won't fill their disks. This can work for a while, but when the underlying storage fills up, writes start failing or slow dramatically. With spinning disks this was historically common; with NVMe arrays it's less forgiving because the performance cliff is steep and usually unexpected.

Beyond raw capacity, storage performance can also be degraded through IOPS throttling or contention on shared arrays. Even if you have physically provisioned space, multiple VMs hammering the same SSD can saturate its write throughput.

The "noisy neighbor" problem

Whether it's RAM, CPU, or disk, overselling leads to what's commonly called the noisy neighbor problem. Your VPS shares a physical host with other tenants. If one of them starts running a backup job, compiling a large codebase, or serving a traffic spike, it can consume disproportionate resources and affect every other VM on the same host.

On an oversold host, a single heavy tenant can destabilize the entire machine. This is why VPS performance can seem wildly inconsistent, fast at 2am, sluggish at noon. The variability isn't random; it tracks how busy your neighbors are.

How to detect if your VPS is oversold

There are a few practical ways to check.

Watch CPU steal time. As mentioned, the st column in top is your clearest signal. Run a CPU-intensive task and monitor whether steal climbs.

Run memory pressure tests. Tools like stress-ng can allocate memory and expose whether your system starts swapping under the load you'd expect to handle easily.

Benchmark disk throughput consistently. Use fio to test sequential and random read/write speeds at different times of day. Wide variance between results suggests contention on a shared storage pool.

Monitor baseline latency. Unexplained latency spikes, especially under light load, often come from hypervisor scheduling delays on a busy host.

What a non-oversold VPS looks like

Providers who don't oversell guarantee that the resources you pay for are physically reserved for your instance. Your RAM is allocated exclusively to your VM, not shared from a pool. Your vCPUs map to actual threads that aren't being handed off to fifty other VMs. Your NVMe storage is provisioned from capacity that actually exists on the disk.

The practical difference shows up in consistency. Benchmarks taken at different times of day should return similar results. CPU steal stays low or at zero. Memory-intensive applications don't crash randomly. Disk throughput is predictable.

This also matters for sizing. If you're running a database or caching layer, oversold RAM means you can't trust your memory limits. You might tune your MySQL buffer pool to 80% of allocated RAM and find it's competing with other VMs for physical memory that was never actually yours.

Why providers do it

The honest answer is margin. Physical hardware is expensive, and a provider that provisions resources 1:1 has to charge more to cover costs than one that sells the same spec at a 2:1 or 3:1 overcommit ratio. For many workloads, especially low-traffic websites or development environments, overselling genuinely doesn't matter day to day. The problem is that customers buying oversold VPS for production workloads often don't find out until something goes wrong.

Some providers advertise "no overselling" or "guaranteed resources" explicitly. That's worth looking for. Others don't mention it at all, which is usually a sign to dig deeper before committing.

Conclusion

Overselling is a real performance risk, particularly for anyone running production services on a VPS. If your workload depends on predictable memory, CPU access, or disk throughput, understanding what your provider actually guarantees matters more than the listed specs.

Thanks for reading! If you're looking for a hosting environment where resources are never oversold, QDE offers unmanaged KVM VPS hosting with dedicated RAM, pure NVMe storage, and AMD EPYC and Ryzen processors — none of it shared from an overcommitted pool.

Ready to start or have questions? Contact our team and we'll help you find the right plan for your workload.

Frequently asked questions about VPS overselling

What is overselling in VPS hosting?

Overselling is when a hosting provider allocates more resources across its VMs than the underlying physical server actually has. This can affect RAM, CPU, and storage, and often results in inconsistent or degraded performance during peak usage.

How can I tell if my VPS is oversold?

The most direct signal is CPU steal time, visible in Linux via the st column in top or vmstat. Consistent steal above 5% under moderate load suggests your host is overcommitted. You can also benchmark disk throughput and memory at different times of day; wide variance is a red flag.

Does overselling always cause problems?

Not always. For light workloads like low-traffic sites or dev environments, an oversold VPS may perform fine most of the time. Problems become more visible under sustained load or when multiple tenants are active simultaneously.

What's the noisy neighbor problem?

It refers to the situation where one tenant on a shared physical host consumes a disproportionate share of resources, degrading performance for everyone else on the same machine. It's a direct consequence of overselling.

How do I avoid oversold VPS hosting?

Look for providers that explicitly state they don't oversell RAM or CPU. Check for benchmarks and independent reviews. Ask the provider directly about their overcommit ratios. Providers that refuse to answer or deflect are often overselling.

What resources are most commonly oversold?

RAM is the most commonly oversold resource, followed by CPU. Storage can also be oversold, though some providers use thin-provisioned storage pools which behave similarly in practice.

This article explains what KVM is, how it compares to alternatives, and whether it covers what you're trying to do.

What KVM actually is

KVM stands for Kernel-based Virtual Machine. It's a virtualization module built directly into the Linux kernel, and it turns the host machine into a hypervisor by taking advantage of hardware virtualization extensions built into modern CPUs (Intel VT-x and AMD-V).

Each KVM instance gets its own virtualized hardware: CPU cores, RAM, network interfaces, and storage controllers. From your VPS's perspective, it looks and behaves like a real physical machine. Your kernel runs directly on virtualized hardware rather than being abstracted away by a software layer.

This is different from container-based approaches like OpenVZ or LXC, where all containers share the host's kernel. With KVM, your VPS has its own kernel entirely.

KVM vs. OpenVZ: why the distinction matters

OpenVZ is the other common VPS virtualization technology, and it's worth understanding the tradeoff directly.

OpenVZ containers share the host kernel. This makes them lightweight and efficient, but it puts real constraints on what you can do. You can't run a different kernel, you can't load custom kernel modules, and some system calls are filtered or unavailable. Docker inside an OpenVZ VPS is often broken or restricted. Certain network configurations don't work. TUN/TAP support (required for VPNs) may or may not be available depending on the provider.

KVM has none of these limitations. Because you have a full virtualized machine with your own kernel, you can:

• Run any Linux distribution or kernel version
• Use Docker, Podman, or any other container runtime without restrictions
• Load custom kernel modules
• Configure TUN/TAP for VPN servers (WireGuard, OpenVPN)
• Use iptables and nftables with full functionality
• Run nested virtualization if the host CPU supports it

If you've ever had a workload fail or behave oddly on a cheap VPS and couldn't figure out why, there's a reasonable chance OpenVZ was the underlying cause.

What you can run on a KVM VPS

The short answer is: almost anything you'd run on a physical Linux server.

Linux distributions. Any standard distro works — Debian, Ubuntu, Rocky Linux, AlmaLinux, Fedora, Arch, Gentoo. You can also install your own custom ISO if the provider supports it.

Docker and containers. Docker runs natively without workarounds. You can run Docker Compose stacks, build images, use multi-stage builds, and expose container networks without fighting the host kernel.

VPN servers. WireGuard, OpenVPN, and other VPN software rely on TUN/TAP kernel support. This works on KVM out of the box.

Custom kernels. If you need a specific kernel version for a driver, a patch, or a performance configuration, you can compile and boot it. This isn't something most people need, but it's available.

Game servers. KVM gives game server software the consistent CPU scheduling and dedicated RAM it needs. Source engine servers, Minecraft, Valheim dedicated servers — all work without the resource contention issues that can occur in container-based environments.

Development environments. Full-stack dev environments, CI runners, build servers, and database clusters all benefit from predictable resource allocation and kernel-level access.

Resource allocation and what "dedicated" actually means

One of the most important properties of KVM is how resources are allocated. Because each VM is a fully isolated environment, RAM is reserved, not shared. If your plan says 8 GB RAM, those 8 GB are committed to your instance and unavailable to others on the host.

This is meaningfully different from OpenVZ providers who oversell RAM based on the assumption that most tenants won't use their full allocation simultaneously. On an oversold host, a spike in neighbor activity can compress your available memory or degrade your CPU performance.

On KVM, vCPU allocations are also more predictable, though the host's physical CPU scheduler still determines how time is distributed across VMs. The degree of CPU contention depends on the provider's overcommit ratio; reputable hosts keep this conservative.

Storage on KVM is typically backed by dedicated disk partitions or logical volumes rather than shared filesystems. Combined with NVMe drives, this means your disk I/O isn't competing with neighbor reads and writes in the same way it can on container-based hosts.

Limitations worth knowing about

KVM is excellent, but it's not the right fit for everything.

Overhead compared to containers. A KVM VM uses more memory and CPU at baseline than an equivalent OpenVZ container, because it's emulating a complete hardware environment and running a full kernel. If you're trying to pack a large number of minimal workloads onto cheap hardware, containers are more efficient. For most serious workloads, this overhead is irrelevant.

No Windows support from all providers. KVM supports Windows as a guest OS in principle, but most Linux VPS providers don't license or offer it. If you specifically need Windows Server, you'll need a provider that explicitly supports it.

Not magic hardware. KVM guarantees your allocated resources and removes kernel-level restrictions, but it doesn't change the underlying physical hardware. If the host machine has aging CPUs or HDDs instead of NVMe, that will still affect your performance.

Who KVM is right for

KVM works well for essentially any serious hosting workload. If you're running a web app, a database, a self-hosted service, a VPN, a game server, or a CI environment — KVM will handle it cleanly.

It's particularly the right call if you:

• Need to run Docker or container runtimes
• Are setting up a VPN server (WireGuard, OpenVPN)
• Want to install or update the kernel independently
• Are moving workloads from a physical server or cloud VM
• Have had unexplained issues on OpenVZ in the past
• Need reliable, non-oversold resource guarantees

If you're building something minimal — a tiny static site, a single cron job, a lightweight proxy — a container-based VPS might technically cost less. But for anything beyond the simplest use case, the predictability and flexibility of KVM is worth it.

Choosing a KVM provider

Not all KVM VPS offerings are equivalent. The virtualization layer is only one part of the equation. When comparing providers, it's worth checking:

• CPU generation. AMD EPYC and Ryzen processors have excellent single-thread performance and are common in modern VPS infrastructure. Older Intel Xeon generations can be slower per core.
• Storage type. NVMe makes a significant difference for database workloads and anything with frequent reads and writes. SATA SSDs are acceptable; HDDs are not worth it for a primary VPS in most cases.
• RAM overselling policy. Ask directly or check the docs. "Guaranteed RAM" should mean the allocation is reserved, not that it's your maximum in a shared pool.
• Network throughput. A 10 Gbps uplink means your VPS can fully utilize burst bandwidth without the host being a bottleneck.
• Control panel features. OS reinstalls, snapshot management, VNC console access, and rDNS configuration are the baseline you should expect.

Summary

KVM is the right virtualization choice for any workload that requires real kernel access, consistent resource allocation, or Docker compatibility. It removes the constraints that make OpenVZ frustrating for serious work, and it behaves like a proper Linux machine rather than a restricted container environment.

For the vast majority of developers, sysadmins, and self-hosters, a KVM VPS covers everything they need without the cost or complexity of bare metal.

Thanks for reading! If you're looking for a KVM VPS that doesn't oversell RAM or storage, QDE offers unmanaged KVM VPS hosting in Amsterdam on AMD EPYC and Ryzen 7950X hardware, with pure NVMe storage, 10 Gbps uplinks, and daily remote backups on every plan.

Ready to get started or have questions about which plan fits your setup? Reach out to our team — we're happy to help.

Frequently asked questions about KVM VPS hosting

What does KVM mean in VPS hosting?

KVM stands for Kernel-based Virtual Machine. It's a Linux kernel module that enables full hardware virtualization, giving each VPS its own isolated kernel, CPU, RAM, and storage — rather than sharing the host kernel with other tenants.

Is KVM better than OpenVZ?

For most workloads, yes. KVM gives you a full virtualized machine with no kernel-level restrictions, which means Docker, VPNs, custom kernels, and most system-level tools work without issues. OpenVZ is lighter but heavily restricts what you can run.

Can I run Docker on a KVM VPS?

Yes, Docker runs natively on KVM without any workarounds. You get full access to Docker's networking, volume management, and build system just as you would on a physical machine.

Can I set up a VPN server on a KVM VPS?

Yes. WireGuard and OpenVPN both require TUN/TAP kernel support, which is available on KVM. Container-based VPS providers sometimes restrict or disable this.

Does QDE oversell RAM?

No. QDE's KVM VPS plans use dedicated RAM allocations — what your plan lists is what's reserved for your instance. Storage is also never oversold.

What operating systems can I run on a KVM VPS?

Any standard Linux distribution works, including Debian, Ubuntu, Rocky Linux, AlmaLinux, and more. QDE supports one-click reinstalls across the most common distros from the control panel.

What's included with every QDE VPS plan?

Every plan includes pure NVMe storage, a 10 Gbps uplink, a dedicated IPv4 address, a /64 IPv6 subnet, daily automatic offsite backups via Proxmox Backup Server, and on-demand manual backups you can trigger from the control panel.

This article breaks down the architectural differences between Ryzen and EPYC, how those differences play out in hosting environments, and which processor class is likely the better fit depending on your workload.

Background: what Ryzen and EPYC actually are

AMD Ryzen is a consumer and prosumer processor line. It spans desktop chips, laptop CPUs, and some workstation-class hardware. Ryzen processors are built around the Zen architecture and are designed with a balance of single-threaded performance, power efficiency, and price in mind. They're the chips in gaming PCs and enthusiast workstations.

AMD EPYC is AMD's server processor line, also built on Zen but designed from the ground up for data center workloads. EPYC chips prioritize core count, memory bandwidth, PCIe lane availability, and reliability features that consumer chips simply don't have — like support for registered ECC RAM, more NUMA nodes, and multi-socket configurations.

Both are competitive AMD silicon, but they target completely different markets.

Core count and threading

EPYC processors offer substantially higher core counts than Ryzen. Current-generation EPYC chips go up to 96 cores per socket, while Ryzen tops out in the 16-core range for desktop chips and around 24 cores on higher-end Ryzen Threadripper Pro models (which are themselves more server-oriented).

For VPS hosting, core count matters because a physical host server needs to support dozens of virtual machines simultaneously. A server running 40 or 50 VPS instances needs raw parallelism — more cores means more tenants can be served without contention.

Ryzen's lower core count doesn't disqualify it from hosting use, but it's better suited to smaller node deployments or environments where single-threaded performance is the priority.

Single-threaded performance

This is where Ryzen can have an edge. Consumer-grade Ryzen chips — particularly the Ryzen 9 7950X and similar — boost to very high clock speeds compared to EPYC. EPYC is built to sustain performance across many cores simultaneously, so individual core clock speeds tend to be more conservative.

For workloads that are heavily single-threaded — like certain PHP applications, game servers, or older software that doesn't parallelize well — a high-clock Ryzen chip can outperform an EPYC on a per-core basis in burst workloads.

This is part of why some hosting providers offer Ryzen-based VPS plans specifically for latency-sensitive or single-threaded workloads, while using EPYC for general-purpose hosting fleets.

Memory: ECC, bandwidth, and channel count

EPYC supports registered ECC (Error-Correcting Code) memory across all configurations. ECC RAM detects and corrects single-bit memory errors in real time, which matters for servers running continuously under load. A memory error on a desktop chip might cause a crash or data corruption; on a server, that's unacceptable.

Consumer Ryzen chips have inconsistent ECC support — some support it in a limited capacity, but it's not a first-class feature the way it is on EPYC. Ryzen Threadripper Pro is an exception, with full ECC support, but standard Ryzen desktop chips aren't reliable for ECC-dependent workloads.

EPYC also supports significantly more memory channels and higher total RAM capacity per socket. A current EPYC server can be configured with terabytes of RAM; a Ryzen system is limited to far less.

PCIe lanes and I/O

EPYC provides an enormous number of PCIe lanes per socket — often 128 or more on current-generation chips. This matters for servers with multiple NVMe drives, high-speed NICs, or GPU accelerators.

Ryzen provides enough PCIe lanes for a desktop or a small workstation, but not nearly enough for a densely-configured server. If a storage node needs 8 NVMe drives and a 25 GbE network card, Ryzen will run out of lanes.

For NVMe-heavy VPS hosting — where fast storage is a key selling point — EPYC's I/O capacity is a significant practical advantage.

Reliability and server-class features

EPYC includes a range of features that don't exist on consumer chips: multi-socket support, Secure Memory Encryption (SME), Secure Encrypted Virtualization (SEV), and hardware-level virtualization isolation. SEV in particular is relevant for VPS environments — it allows each VM's memory to be encrypted independently so that even a compromised hypervisor can't read guest VM memory.

Ryzen lacks most of these features outside of the Threadripper Pro tier. This isn't a knock on Ryzen as a product category; consumer CPUs aren't designed for these use cases.

Virtualization performance

Both Ryzen and EPYC support AMD-V (AMD Virtualization), so hypervisors like KVM run well on either. The difference shows up at scale.

EPYC's NUMA (Non-Uniform Memory Access) topology, higher core count, and memory architecture make it more predictable under high VM density. When dozens of VMs are competing for CPU time and memory bandwidth, EPYC's design handles that workload more gracefully.

For small-scale or single-purpose hosts — a home lab, a private server, or a VPS node running a handful of VMs — Ryzen can work well and cost less to build.

Power efficiency

Ryzen chips generally consume less power than EPYC at equivalent loads, which matters for smaller deployments where electricity cost is a factor. EPYC's higher TDP is a tradeoff for its expanded feature set and core count.

At data center scale, power is always a concern, but the cost per core on EPYC usually justifies the power draw when running high-density workloads.

Which is better for VPS hosting?

For large-scale commercial VPS hosting — the kind a provider runs with dozens of nodes and hundreds of customers — EPYC is the right choice. The combination of core count, ECC memory, PCIe bandwidth, SEV support, and sustained multi-threaded performance is hard to beat.

For use cases where single-threaded burst performance is the priority — such as a high-frequency game server, a low-latency trading application, or software that simply doesn't parallelize well — a high-clock Ryzen node can be a deliberate and sensible choice. Some providers offer Ryzen-based VPS specifically for this segment.

For self-hosted environments or home labs where budget matters and workloads are lighter, Ryzen is often the more practical option. You get strong performance at a lower hardware cost, with the understanding that you're trading away ECC reliability, core density, and some server-class features.

How QDE approaches processor selection

QDE uses both AMD EPYC and AMD Ryzen 7950X hardware across its VPS fleet. The processor varies by plan tier. EPYC handles the workloads where memory reliability, core density, and VM isolation are priorities; Ryzen 7950X covers scenarios where high single-threaded performance is the better fit.

RAM and storage are never oversold on any configuration — every plan reflects actual allocated resources, not oversubscribed pools.

Conclusion

Ryzen and EPYC are both excellent AMD processors, but they solve different problems. EPYC is built for the data center: high core counts, ECC memory, deep I/O, and reliability features designed for always-on server workloads. Ryzen is built for performance at a price point, with strong single-threaded speed that can make it the right fit for specific hosting use cases.

Knowing which one you're running on — and why — helps you match your workload to the right environment.

Thanks for reading! If you need reliable VPS hosting backed by AMD EPYC and Ryzen 7950X hardware, QDE offers high-performance VPS in the Netherlands with pure NVMe storage, 10 Gbps uplinks, and no resource overselling.

Ready to get started or have questions? Reach out to our team.

Frequently asked questions about AMD Ryzen vs. EPYC for VPS and servers

What's the main difference between AMD Ryzen and EPYC?

Ryzen is a consumer and prosumer processor line optimized for single-threaded performance and cost efficiency. EPYC is AMD's server-grade line, built for high core counts, ECC memory support, more PCIe lanes, and reliability features suited to data center workloads.

Is AMD EPYC better than Ryzen for VPS hosting?

For large-scale, high-density VPS hosting, EPYC is generally the better choice. It supports more simultaneous virtual machines, provides ECC memory, and includes hardware virtualization isolation features like AMD SEV. Ryzen can be a valid choice where high single-threaded performance matters more than density.

Does Ryzen support ECC memory?

Standard consumer Ryzen chips have limited or no ECC support. Ryzen Threadripper Pro supports ECC, but mainstream Ryzen desktop CPUs aren't reliable for ECC-dependent server workloads. EPYC supports full registered ECC across all configurations.

What is AMD SEV and why does it matter for VPS?

AMD Secure Encrypted Virtualization (SEV) encrypts each virtual machine's memory independently using unique keys. This means even if a hypervisor were compromised, it couldn't read the memory of guest VMs. It's a hardware-level isolation feature available on EPYC, not standard Ryzen.

Can Ryzen be used in a server or VPS environment?

Yes, and it is — some providers deploy Ryzen hardware specifically for workloads that benefit from high single-core clock speeds. It's not the ideal general-purpose hosting chip due to lower core counts, limited ECC, and fewer PCIe lanes, but for the right workload it's a deliberate and reasonable choice.

What processors does QDE use for its VPS plans?

QDE's VPS infrastructure uses AMD EPYC and AMD Ryzen 7950X processors depending on the plan. All configurations use pure NVMe storage with no RAM or storage overselling.

Most mainstream hosts either prohibit adult content outright or bury vague restrictions in their terms of service that leave you one complaint away from a suspension.

What you actually need is a provider that explicitly permits adult content, respects your privacy, accepts crypto payments, delivers the performance to handle bandwidth-heavy media, and takes abuse handling seriously.

That last point matters more than most operators realize: a host with a real abuse process protects both you and them, and signals they're running a legitimate operation built for the long term. This guide covers 11 providers that check enough of those boxes to be worth considering.

What to look for in an adult-friendly VPS

Before jumping into the list, it helps to know what separates a genuinely useful provider from one that just technically "allows" adult content:

• TOS clarity — Does the provider explicitly permit adult content, or are you reading between the lines?
• Legal content only — Any reputable host will require that content involves consenting adults and complies with applicable law. This isn't a restriction — it's a baseline that protects everyone.
• Abuse handling — A provider with a proper abuse response process is a good sign. It means they're serious about operating cleanly, and it reduces the risk of your server being caught up in someone else's problems.
• Privacy and anonymity — Minimal data collection, no ID verification, crypto payment options.
• Performance — Adult sites are bandwidth-heavy. NVMe storage and fast uplinks matter.
• Location — US-based hosting is a perfectly valid choice; adult content is legal there. EU and offshore providers offer different jurisdictional profiles, but legality isn't the differentiator — TOS permissiveness and infrastructure quality are.
• Payment flexibility — Crypto/Monero acceptance is a strong signal of a privacy-respecting provider.

The 11 best VPS providers for adult content hosting

1. QDE

QDE is a Netherlands-based unmanaged KVM VPS provider that checks every box for adult content operators: explicit TOS support, privacy-respecting practices, crypto payment acceptance (Bitcoin, Litecoin, USDT, and Monero), and infrastructure that can handle bandwidth-heavy workloads. Plans start at just €3.95 with pure NVMe storage, 10 Gbps uplinks, and daily automatic offsite backups via Proxmox Backup Server with on-demand manual backups from the control panel. The Amsterdam data center peers directly at AMS-IX, delivering low-latency connectivity across Europe, North America, and Asia. RAM and storage are never oversold, which matters when your site traffic spikes.

QDE permits adult content involving consenting adults in compliance with applicable law, and operates a proper abuse handling process — both of which matter if you want a host that's built for sustainable, long-term operation rather than looking the other way until a complaint forces their hand. For adult content operators who want a privacy-first, high-performance Netherlands host with no surprises, QDE is the strongest all-around option on this list.

2. OVHcloud

OVHcloud is a large European provider based in France with a permissive TOS, massive infrastructure, and entry-level VPS plans starting at $6.46/month. It accepts crypto payments, offers high traffic allowances, and delivers consistent performance across its global network. For operators who want scale and the backing of a major provider, OVHcloud is a reliable choice.

3. HostSailor

HostSailor is one of the few providers that actively markets itself toward privacy-focused and adult content users. Based in the Netherlands, it doesn't require ID verification and accepts Bitcoin alongside other crypto. Plans start at $5/month. It's purpose-built for this use case, which makes it a strong pick if you want a provider that won't suddenly get skittish about your content category.

4. Ultahost

Ultahost offers a solid combination of NVMe storage, DDoS protection, and crypto payment support. Plans start at $5/month across US and EU locations. It scores well for privacy and performance, and its TOS is permissive toward adult content. Good for operators who want a capable technical stack without paying a premium.

5. dmzhost.co

dmzhost.co is specifically built for privacy and anonymity use cases, including adult content. Prices start at €5/month with crypto-only payments accepted, and it positions itself as an offshore option for operators who want minimal exposure. Good for those prioritizing anonymity over brand recognition.

6. AbeloHost

AbeloHost operates out of the Netherlands with explicit adult content support, no ID checks required, and Bitcoin/crypto acceptance. Plans start at €10/month. It's in a similar tier to HostSailor — offshore Netherlands, privacy-first, no unnecessary friction.

7. RackNerd

RackNerd covers US and EU locations starting at $5/month with crypto payment support and an explicitly adult-friendly TOS. It's a solid budget-tier pick for operators who need flexible US-accessible infrastructure at a competitive price point.

8. Owrbit Adult Hosting

Owrbit is purpose-built for adult hosting, based in the Netherlands, with Bitcoin payment support and plans starting at $12/month. The branding leaves no ambiguity about the target market, and the Netherlands location provides a solid jurisdictional base for European operators.

9. HostingB2B

Bulgaria-based HostingB2B offers budget-friendly plans starting at €11/month with crypto acceptance and adult-friendly TOS. Offshore Eastern European hosting offers a different jurisdictional profile for operators who want geographic diversity.

10. InterServer

InterServer is a US-based provider offering VPS starting at $3/month with customizable plans, and Bitcoin acceptance. It's explicitly adult-friendly with no TOS ambiguity, making it a straightforward budget option for operators who need US infrastructure without the guesswork of checking fine print.

11. SSD Nodes

SSD Nodes is geared toward technical users comfortable managing their own stack. US/EU locations, starting at around $6/month (only annual billing available, though), crypto payments, and an adult-friendly TOS. A solid pick for developers and sysadmins who want capable infrastructure at a budget price point without paying for hand-holding they don't need.

Picking the right fit

Your best choice comes down to a few factors:

• Best overall pick: QDE — Netherlands-based, crypto payments including Monero, NVMe + 10 Gbps, no overselling
• Budget-focused: Ultahost, or RackNerd at $5–$10/month
• Maximum privacy: QDE (Monero accepted), AbeloHost (Monero accepted), or dmzhost.co
• Purpose-built adult hosting: HostSailor, Owrbit, or AbeloHost
• Best large-scale infrastructure: OVHcloud
• Netherlands jurisdiction: QDE, HostSailor, AbeloHost, or Owrbit

For most operators, the Netherlands is the sweet spot — permissive legal environment, high-quality infrastructure, and several providers explicitly built for this use case.

Provider comparison at a glance

Thanks for reading!

If you're looking for a high-performance VPS with privacy-respecting practices and crypto payment support, QDE offers unmanaged KVM VPS hosting in the Netherlands with NVMe storage, 10 Gbps uplinks, and daily backups — backed by direct peering at AMS-IX.

Ready to get started or have questions? Contact the QDE team to find the right plan for your project.

Frequently asked questions about VPS hosting for adult content

Is adult content actually legal to host?

Yes — adult content involving consenting adults is legal in the United States, the Netherlands, and most EU countries. The legal question is usually settled; the practical question is finding a host whose TOS reflects that. Always ensure your content meets applicable regulations in both your jurisdiction and your host's.

Which countries are best for adult content hosting?

The Netherlands and the US are both strong choices with well-established legal frameworks for adult content. Romania and other EU jurisdictions are also used. The location decision is less about legality and more about infrastructure quality, network performance, and TOS permissiveness.

Why does abuse handling matter for adult hosting?

A host with a real abuse process — one that investigates complaints rather than just pulling the plug — is a better long-term partner. It means you're protected from bad-faith takedown requests, and it signals the provider is running a legitimate operation. Hosts that ignore abuse entirely tend to attract problematic neighbors on shared infrastructure, which creates headaches for everyone.

Do I need to verify my identity with adult-friendly VPS providers?

It varies. Providers like HostSailor and AbeloHost specifically advertise no ID checks. More mainstream providers may require standard account verification. If anonymity matters to you, look for hosts that accept crypto and don't require documentation.

Can I pay anonymously for adult hosting?

Yes, if you choose the right provider. Bitcoin is widely accepted across almost all providers on this list. For stronger privacy, Monero is the gold standard — QDE and AbeloHost both confirm acceptance. Providers like dmzhost.co accept crypto exclusively, making them a strong option for operators who want minimal payment trails.

What kind of performance should I expect for video-heavy adult sites?

Adult sites, especially those serving video content, are bandwidth-intensive. Look for providers offering 10 Gbps uplinks, NVMe storage for fast I/O, and generous traffic allowances. QDE and OVHcloud both perform well on these metrics.

Is offshore hosting necessary for adult content?

Not necessarily. US hosting is a legitimate option — adult content is legal there and several reputable providers explicitly support it. Offshore hosting in the Netherlands or EU can offer different jurisdictional benefits, but the more important factors are TOS clarity, infrastructure quality, and whether the provider has experience handling adult content accounts professionally.

This guide breaks down what a VPS is, how the technology works under the hood, and how it compares to other hosting types, so you can decide if it's the right fit for your workload.

What a VPS actually is

A VPS, or virtual private server, is a virtualized environment running on a physical host machine. The host is divided into multiple isolated instances using a hypervisor — software that sits between the hardware and the virtual machines, allocating CPU, RAM, and storage to each one independently.

Each VPS behaves like its own server. You get root access, your own OS, your own networking stack, and resources that aren't shared with other tenants. From your perspective, it looks and feels like a dedicated machine — even though the underlying hardware is shared.

How virtualization works

The magic behind a VPS is the hypervisor. There are two common types:

Type 1 (bare-metal): Runs directly on the hardware with no host OS in between. Examples include KVM, VMware ESXi, and Hyper-V. These offer better performance and isolation.

Type 2 (hosted): Runs on top of an existing OS, like VirtualBox on a desktop. You won't see this in production hosting environments — it's mostly for development and testing.

Most VPS providers use KVM (Kernel-based Virtual Machine), which is a Type 1 hypervisor built into the Linux kernel. KVM gives each VM its own virtualized CPU and memory, making it one of the most performant and well-supported options available. It's the industry standard for a reason.

VPS vs. shared hosting vs. dedicated servers

Understanding the tradeoffs helps you pick the right tool.

Shared hosting puts multiple customers on the same server with the same OS, using software like cPanel or Plesk to carve out isolated spaces. It's cheap, but noisy neighbors are a real problem — if another account on the box spikes CPU, your site slows down too. You also have no root access, so you're limited to what the host allows.

VPS hosting gives you guaranteed resources and a fully isolated environment. Your RAM is your RAM, your CPU allocation is yours, and you're running your own OS. You can install packages, configure the kernel, run Docker, set up custom firewall rules — anything a root user can do.

Dedicated servers hand you the entire physical machine. No virtualization overhead, maximum raw performance. The tradeoff is cost and provisioning time. For many workloads, a well-resourced VPS is indistinguishable from a dedicated server in practice.

What "unmanaged" means

VPS plans are typically sold as either managed or unmanaged.

With a managed VPS, the provider handles OS updates, security patches, monitoring, and sometimes application-level configuration. You pay a premium for that hands-off experience.

With an unmanaged VPS, the provider is responsible for the hardware and hypervisor layer — you handle everything above that. This means you're installing your own OS, managing your own updates, and configuring your own security. It's more work, but you get complete control and typically a better price-to-resource ratio.

Most developers and sysadmins prefer unmanaged, since the whole appeal of a VPS is doing things your way.

What you can run on a VPS

The short answer: anything that runs on Linux (or Windows, if you go that route). Common use cases include:

• Web servers (Nginx, Apache, Caddy)
• Application backends (Node.js, Python, PHP, Go, Rust)
• Databases (PostgreSQL, MySQL, MongoDB, Redis)
• Self-hosted tools (Nextcloud, Gitea, Vaultwarden, Jellyfin)
• Game servers
• VPN endpoints (WireGuard, OpenVPN)
• CI/CD runners and build agents
• DNS servers and mail servers

A VPS is especially popular in the self-hosting community because it gives you the infrastructure flexibility of a home server without the uptime and connectivity concerns of running hardware at home.

How to choose a VPS

A few things worth evaluating before you sign up:

CPU architecture and hardware. AMD EPYC and Ryzen processors have become the default choice for VPS providers who care about performance. Avoid providers that don't disclose their hardware.

RAM and storage guarantees. Many providers oversell resources — advertising 4 GB RAM but running dozens of VMs on a host with less total capacity than the sum of allocations. Look for providers that explicitly guarantee no overselling and use NVMe storage rather than HDDs or SATA SSDs.

Network quality. Bandwidth caps and uplink speed matter. A 1 Gbps uplink is fine for most workloads; 10 Gbps becomes relevant for high-throughput applications or servers serving traffic across multiple regions. Peering at major internet exchanges (like AMS-IX) also affects real-world latency.

Location. Pick a data center geographically close to your users. Latency adds up, especially for interactive applications.

Control panel features. At minimum, you want OS reinstall, reboot controls, VNC access for emergencies, snapshot management, and rDNS configuration. These should be self-service — not a support ticket.

KVM vs. OpenVZ

You'll occasionally see OpenVZ-based VPS plans, which use container-level virtualization rather than full hardware virtualization. OpenVZ VMs share the host's kernel, which limits what you can do — you can't load custom kernel modules, run Docker in some configurations, or always guarantee resource isolation.

KVM is almost always the better choice. Full hardware virtualization means your VM has its own kernel, complete isolation, and no restrictions on what you install.

Conclusion

A VPS sits at the right intersection of control, performance, and cost for most serious workloads. Once you've hit the limits of shared hosting or you need a proper environment for development, staging, or production — a VPS is usually the next move.

Thanks for reading! If you're looking for a VPS with guaranteed resources and no overselling, QDE offers high-performance KVM VPS hosting in Amsterdam backed by NVMe storage, 10 Gbps uplinks, and direct peering at AMS-IX.

Ready to get started or have questions? Contact our team to find the right plan.

Frequently asked questions about VPS hosting

What's the difference between a VPS and a cloud server?

The terms are often used interchangeably, but "cloud server" usually implies infrastructure spread across multiple physical nodes with live migration or high-availability features. A traditional VPS runs on a fixed host. In practice, both use virtualization — the difference is mostly in the underlying architecture and how the provider manages failover.

Do I need a VPS or a dedicated server?

For most workloads — web apps, databases, game servers, self-hosted services — a well-resourced VPS is plenty. Dedicated servers make sense when you need maximum raw I/O performance, specific hardware configurations, or complete physical isolation for compliance reasons.

What OS can I install on a VPS?

Any OS with a supported installer image. Most providers offer Debian, Ubuntu, Rocky Linux, AlmaLinux, and CentOS Stream at minimum. QDE's control panel supports one-click reinstall across all supported distributions.

Is a VPS suitable for beginners?

An unmanaged VPS assumes you're comfortable with Linux administration — SSH, package management, firewalls, and basic system maintenance. If that's new territory, managed hosting or a managed VPS plan is a better starting point.