Skip to content
OS Domains
Infrastructure · Single-tenant compute

Dedicated servers for teams who outgrew Hetzner self-service and never wanted AWS in the first place

A dedicated server is a single-tenant physical machine you rent whole, with no hypervisor and no neighbors competing for CPU, disk or network. OS Domains provides bare-metal dedicated servers across seven datacenters in the UK, Netherlands, Germany, France, Sweden, the US and Panama — self-managed by default, with managed operations as an add-on — for email infrastructure, databases and workloads where a cloud VM's shared I/O and noisy-neighbor variance get in the way.

Bare metal, single tenant, ECC RAM, NVMe storage, in seven datacenter PoPs across the EU plus optional US and Panama. Operated by the engineering team that has been running infrastructure since 2008. Self-managed by default with the option to add a managed operations layer when you want sleep instead of pagers. From €299 per month for a single node, up to multi-region HA clusters for production workloads that cannot tolerate a noisy Tuesday.

In short

  • Single-tenant bare metal in seven PoPs — UK, Netherlands, Germany, France, Sweden, US and Panama — so you choose the jurisdiction your data sits under.
  • Three tiers (Single Node, Performance Node, HA Cluster), self-managed as the base price, with managed operations at +€199/mo per node.
  • No per-CPU or per-GB surcharge: what is on the spec sheet is what you pay, and annual contracts save 15%.
  • Honest comparison built in — Hetzner and OVHcloud are cheaper at the same specs, and we tell you when they are the better call.
  • Suited to workloads a cloud VM handles badly: high-throughput MTAs, sustained CPU and heavy disk I/O without noisy-neighbor variance.
Bare metal vs cloud VM

What does single-tenant hardware actually change?

A cloud VM shares a physical host through a hypervisor, so its neighbors can contend for CPU cycles and disk I/O — the variance that hurts a high-throughput mail queue. A dedicated node hands you the whole machine: every core, all the RAM and NVMe, and a network interface no one else touches. The diagram contrasts the two.

Cloud VM (shared host) hypervisor shared with other tenants CPU and disk I/O contention noisy-neighbor variance a fraction of the box vs Dedicated bare metal single tenant, no hypervisor full CPU, RAM and NVMe dedicated NIC and IPs the whole machine

What a provisioned node looks like on login — full core count, dedicated memory, reverse DNS already set for the sending IP, and the MTA running:

$ ssh [email protected]
$ nproc
16
$ free -g | grep Mem
Mem:            64          12          52
$ dig +short -x 203.0.113.45
mail.yourdomain.com.
$ systemctl is-active kumomta
active
Where this product fits

Bare metal sits in a strange middle, too serious for cloud VMs, too operational for cheap dedicated

Most workloads should run on cloud VMs. The economics are good, the operational burden is light, the autoscaling story is genuine. Most teams running bare metal in 2026 have a specific reason: a database that needs predictable I/O, a CPU-bound workload that cannot tolerate noisy neighbors, a compliance requirement that forces single-tenant hardware, or a cost profile where cloud markup stops being worth the convenience. If you do not have one of those reasons, you are probably better served by a cloud VPS and the rest of this page is not for you.

For the workloads that do need bare metal, the European market has two main shapes. The first shape is low-cost commodity, like Hetzner, OVHcloud Eco, the auction tier on most providers. You get strong hardware at remarkable prices, you handle every operational concern yourself, and the support is best-effort. This works well for teams with strong systems engineering capacity and a tolerance for the occasional weekend escalation. It works less well for teams whose systems engineers are also expected to ship features.

The second shape is high-touch managed bare metal, like IBM Cloud, AWS Bare Metal, the enterprise tier on most providers. You get hardware in a managed environment, the operations layer is mostly handled, and the price is high enough that the savings versus virtualization are not always compelling. This works well for enterprises with clear budget and limited operational maturity. It works less well for SaaS teams at €5 to €50M ARR who want better than Hetzner self-service without paying enterprise rates.

We sit in the middle. Hardware is single-tenant, ECC RAM, NVMe by default, deployed across seven PoPs in the EU and EU-adjacent regions. Self-managed is the default. You have root, you tune the box, you run the workload. Managed operations is an add-on for teams that want monitoring, patching, and incident response handled for them. The pricing reflects the positioning: more than Hetzner, less than IBM, with EU sovereignty and operational support that neither of those gives you for the same number.

And worth saying once: we are not the cheapest. If raw cost per gigaherz is your evaluation metric, Hetzner will win. We compete on the operational layer, the EU jurisdiction story, and the multi-PoP footprint that lets us put a database in Vienna and a worker pool in Frankfurt without going through a different vendor for each.

Two things this product is not. It is not a cloud VPS replacement for workloads that genuinely need elastic scaling. If your workload routinely shifts by 10x within a single day, cloud is the right answer and we will tell you so on the discovery call. It is also not a hyperscale alternative for teams running thousands of nodes. At that scale you have negotiated AWS or GCP pricing that we cannot match, and the operational tooling those clouds provide for fleet management is genuinely useful. Where we fit is the middle ground: dozens to low hundreds of nodes, steady to moderately variable workloads, EU jurisdiction priorities, and a team that values operational support without paying hyperscaler markup.

When a single-tenant box is the right answer

When does dedicated bare metal beat a cloud VM?

Dedicated bare metal pulls ahead in a handful of shapes — sustained CPU, heavy disk I/O, and high-throughput sending where noisy-neighbor variance hurts. Cloud VMs win most of the time; the exceptions tend to share a few common shapes. Below are the patterns where dedicated bare metal at our pricing point is the obvious choice, and the patterns where it is not.

Use case 01

Databases with predictable I/O requirements

PostgreSQL, MySQL, ClickHouse, MongoDB at the volumes where cloud-managed databases get expensive and noisy. NVMe storage on dedicated hardware gives you consistent IOPS without the burst credits and throttling games that AWS RDS or DigitalOcean Managed Database play under load. The cost crossover usually happens around 500GB of data or 2,000 sustained IOPS. Past that, dedicated wins on every dimension except backup automation, which we provide separately.

Use case 02

CPU-bound workloads that need consistent performance

Video encoding, scientific computing, ML inference at scale, anything where vCPU contention on shared hosts hurts your latency story. A dedicated 16-core or 24-core node gives you predictable cycles for the duration of your workload. The reservations-versus-on-demand math on cloud rarely beats this for sustained workloads, and the burst-capacity argument that justifies cloud usually does not survive a cost audit.

Use case 03

EU-jurisdiction compliance for application infrastructure

Your application data has to stay inside the EU because your customers are regulated, your auditor flagged Cloud Act exposure, or your DPO refuses to sign off on anything else. Most cloud regions are an asterisk: the data is in EU but the parent company is US, the support staff might be reading logs from anywhere, and the failover destinations are documented in fine print. Single-tenant hardware in our datacenters with our (EU-only) operations team is a clean answer that survives a serious DPA review.

Use case 04

Hosting your own Kubernetes cluster

If you want managed Kubernetes, use GKE or EKS. They are excellent products. If you want to run your own — for cost reasons, control reasons, or because your stack does not fit the managed shape — bare metal is what you provision. Our 3-node HA Cluster plan is sized to run a production Kubernetes control plane plus initial worker capacity, with private network between nodes for cluster-internal traffic and dedicated public IPs per node for ingress.

Use case 05

Game servers, voice servers, real-time collaboration backends

Workloads where 10 milliseconds of latency is the difference between a good experience and a bad one. Cloud VMs add jitter from the virtualization layer that is hard to characterize and harder to remove. Bare metal removes a class of latency variance entirely. Our PoPs in Vienna, Frankfurt, Amsterdam and London cover most of Western Europe within 25ms.

Use case 06

CI/CD runners that have outgrown shared platforms

GitHub Actions and GitLab Runners on shared infrastructure work fine until they do not. The patterns where shared CI breaks: heavy compilation jobs (C++, Rust, large monorepos), workloads with secrets that should not leave your network, builds that need persistent caches between runs. Self-hosted runners on dedicated bare metal solve all three. The economics break even versus GitHub-hosted around 200 build-minutes per day for a single team, less for organizations with multiple teams sharing a runner pool.

Use case 07

Storage-heavy workloads where cloud egress fees hurt

Backup repositories, log archives, video transcoding pipelines, anything where you regularly read or write hundreds of gigabytes a day. Cloud egress fees on AWS or GCP for these workloads add up fast: a single backup pull of 500GB from S3 to your office costs around $45, and most teams do that weekly. On dedicated bare metal with our included bandwidth allowance, the same operation costs nothing extra until you hit the (generous) included quota. For storage-heavy use cases the cost-of-egress crossover often happens within the first three months of running on cloud.

How we stack against the obvious alternatives

Honest comparison with Hetzner, OVHcloud and AWS at the same node specs

A direct comparison at roughly equivalent hardware (16-core / 64GB ECC / NVMe RAID 1) for a single dedicated node. Pricing reflects published list prices in early 2026. We checked each one before publishing.

Attribute OS Domains Hetzner OVHcloud AWS Bare Metal
Monthly price for 16-core / 64GB / NVMe €299 (Single Node) €80-€120 (AX line, varies by SKU) €140-€180 (Advance Gen4) €650+ equivalent (m5.metal on demand, EU region)
EU sovereign, no US parent in chain Yes, Austrian GmbH Yes, German company Yes, French company No, Amazon US (Cloud Act applies)
Multi-PoP availability 7 PoPs (5 EU + UK + US + Panama) 4 (Germany x2, Finland, US) 32+ globally 30+ regions globally
Managed operations available Yes, +€199/mo add-on No, self-managed only Limited, pro-managed services tier Yes, but at AWS-tier pricing
Single-tenant always (no virtualization on top) Yes Yes (dedicated lines) Yes (dedicated lines) Yes (Bare Metal instances) — but VPC overhead remains
Provisioning time, common OS 24-48 hours 1-4 hours (auto-provisioned SKUs) 15 minutes - 4 hours Minutes
Engineer-level support response Yes, no first-line tier Best-effort, basic support Tiered support (basic free, paid for engineer) Paid Premium Support tier required
Custom hardware configurations Yes, build to spec on Cluster and Custom tiers Limited to published SKUs Limited customization Fixed instance types
Hardware specifications

What is in the rack, by tier

The hardware below is what we deploy by default. Single-tenant always, no virtualization between you and the metal. ECC RAM throughout. NVMe storage. Redundant power supplies. If you want a different config, we build to spec on Cluster and Custom tiers — talk to us during onboarding.

T1

Single Node

Workhorse box for general-purpose workloads up to mid-volume

  • CPU Intel Xeon Silver 4314 (16 cores / 32 threads) or AMD EPYC 7313P (16 cores / 32 threads)
  • RAM 64 GB DDR4 ECC, expandable
  • Storage 2x 1.92 TB NVMe in RAID 1, hot-swappable
  • Network 2x 10 Gbps redundant uplinks, full duplex
  • IPs /29 dedicated block (5 usable IPs), IPv6 /64
  • Location Choice of any of our 7 PoPs
T2

Performance Node

For database servers, CPU-heavy workloads, production application infrastructure

  • CPU Intel Xeon Gold 6342 (24 cores / 48 threads) or AMD EPYC 7443 (24 cores / 48 threads)
  • RAM 128 GB DDR4 ECC, expandable to 256 GB
  • Storage 4x 3.84 TB NVMe in RAID 10, hot-swappable, with NVMe over Fabrics option
  • Network 4x 10 Gbps with active-active LACP, BGP-capable
  • IPs /28 dedicated block (13 usable IPs), IPv6 /64
  • Location Multi-region available (primary + DR)
T3

HA Cluster

Three-node clusters for HA application stacks, Kubernetes, distributed databases

  • CPU 3+ nodes, each Xeon Gold or EPYC class
  • RAM 128-256 GB per node
  • Storage NVMe with optional shared storage (NFS or Ceph) for clustered workloads
  • Network 4x 10 Gbps per node, plus dedicated private network between cluster nodes
  • IPs /27 across cluster, IPv6 /56
  • Location Single-PoP cluster default, multi-PoP option for geographic redundancy
Two ways to consume this

Self-managed by default, managed operations as an add-on

Most customers start self-managed. They have systems engineers in-house, they know their workload, they want root access and the ability to tune things their way. A subset of customers — usually after a 3 AM incident or two — decide they would rather sleep and add the managed operations layer. Both are valid. The price difference is €199 per month per node, fixed regardless of tier.

Lane 1

Self-managed (default)

You get the box. Operations are yours.

Bare metal provisioned to spec, OS installed (Debian 12, Ubuntu 24.04, AlmaLinux 9, RHEL 9, your choice), root credentials handed over, KVM-over-IP for emergency access. Network and hardware support are ours: if a disk fails or a NIC dies, we replace it. Anything above the OS is yours: patching, monitoring, incident response, application stack. This is the right choice for teams with capable systems engineers and a clear ownership model.

Ideal for

Engineering teams with in-house DevOps capacity, anyone who wants root and the freedom to configure exactly the way they want.

From €299 / month

Lane 2

+ Managed operations

You get the box and the operations team.

Everything in self-managed, plus we operate the OS layer for you. 24/7 monitoring across host metrics and application metrics you give us hooks into. OS patching on a documented monthly schedule with maintenance windows. Incident response within the SLA window when something goes wrong. Backup orchestration to our object storage (or yours). For most teams under €20M ARR with a small engineering team, the managed add-on pays for itself in the engineering hours you stop losing to ops fire drills. The price is €199 per month per node, on top of the base tier.

Ideal for

Engineering teams who would rather ship features than run pager duty. SaaS companies under €20M ARR. Customers who tried self-managed and found out they did not actually want the responsibility.

+€199 / month per node

Where the boxes live

Where are the datacenters located?

The seven PoPs sit in the UK, Netherlands, Germany, France, Sweden, the US and Panama. Datacenter location matters for general-purpose dedicated hosting in two ways. First, latency to your users: the network distance from your server to the recipient affects everything from web page load to game responsiveness. Second, jurisdiction: where the box physically sits determines whose laws apply to the data on it. Below are the seven locations available, with what each is good for.

Vienna

HQ

Austria · Tier 3+

Default for EU customers. Best latency to Nordic and Baltic users. Sub-processor of choice for Schrems II compliance.

Frankfurt

Germany · Tier 4

Central European location, default for German-market customers and DACH-targeted services.

Amsterdam

Netherlands · Tier 3+

Low latency to UK and Western Europe, popular for SaaS targeting BeNeLux.

London

United Kingdom · Tier 4

For UK customers post-Brexit who need UK-jurisdiction hosting. Low latency to UK consumer ISPs.

Strasbourg

France · Tier 3+

French market services, France-data-only compliance scenarios, low latency to Free.fr and Orange networks.

Dallas

USA · Tier 3+

For US-targeted services, North American latency optimum from a single PoP, out of EU jurisdiction for non-EU workloads.

Panama

Panama · Tier 3+

Workloads with specific jurisdiction requirements outside EU and US. LATAM market services, predictable due-process workflow.

Four plans, fixed monthly pricing in euros

How much does a dedicated server cost?

Pricing tracks the hardware tier: self-managed is the base price across the Single Node, Performance Node and HA Cluster tiers, with managed operations at +€199 per month per node, available on every tier. There is no per-CPU or per-GB surcharge: what is on the spec sheet is what you pay. Annual contracts save 15%. Setup fee waived on annual commitments.

Single Node

One bare-metal box, your choice of OS, your choice of PoP.

€299 / month

Provisioned in 24 to 48 hours

Ideal for

Application servers, dev and staging environments, single-server databases, CI runners.

  • Single Node hardware tier (16-core, 64GB ECC, 2x NVMe RAID 1)
  • Choice of any of our 7 PoPs
  • Choice of OS (Debian, Ubuntu, AlmaLinux, RHEL)
  • /29 dedicated IP block (5 IPs), IPv6 /64
  • 2x 10 Gbps network with 50 TB/mo bandwidth
  • KVM-over-IP for emergency access
  • Hardware replacement SLA included
  • Self-managed by default (managed +€199/mo)
Order Single Node
Most chosen

Performance Node

For databases, production apps, CPU-heavy workloads. The tier most customers settle on.

€549 / month

Provisioned in 48 to 72 hours

Ideal for

PostgreSQL/MySQL production databases, Kubernetes control plane single-node, video encoding pipelines, ML inference servers.

  • Performance Node hardware tier (24-core, 128GB ECC, 4x NVMe RAID 10)
  • Everything in Single Node
  • /28 dedicated IP block (13 IPs)
  • 4x 10 Gbps network with 100 TB/mo bandwidth
  • BGP-capable network for advanced routing
  • Optional NVMe over Fabrics for cluster storage
  • Multi-region DR option available
  • Self-managed by default (managed +€199/mo)
Order Performance Node

HA Cluster

3-node cluster with private network. The starting point for production HA.

€1,499 / month

Provisioned in 5 to 7 business days

Ideal for

Self-hosted Kubernetes, distributed databases (Cassandra, CockroachDB), HA application stacks, anything that requires real redundancy.

  • 3x Performance Node tier hardware
  • Dedicated private network between cluster nodes (10 Gbps)
  • Public /27 IP block across cluster
  • 300 TB/mo aggregate bandwidth
  • Single-PoP by default, multi-PoP option available
  • NVMe shared storage option (NFS or Ceph)
  • Cluster-aware monitoring on managed add-on
  • Self-managed by default (managed +€199/mo per node)
Order HA Cluster

Custom

Multi-region, custom hardware, GPU, anycast, signed SLA.

Custom annual

Onboarding 10 to 20 business days

Ideal for

Production infrastructure with formal SLA needs, GPU workloads (ML training), multi-region distributed systems, regulated industries.

  • Build-to-spec hardware (custom CPU, RAM, storage configurations)
  • GPU options (NVIDIA L4, L40S, H100 — case by case)
  • Multi-region clusters with anycast announcements
  • /26 or /25 IP allocations across geographies
  • Custom log retention up to 7 years
  • Signed SLA with service credits
  • Named technical account manager
  • Slack Connect direct line
  • 1-hour incident response SLA, 24/7
Talk to sales

Bandwidth above the included quota is billed at €0.02 per GB. IPv4 additional blocks at €2.50 per IP per month above the included allocation. Anti-DDoS protection (volumetric) included on all tiers; layer 7 mitigation available as add-on. Backup orchestration to our object storage available at €0.02/GB-month. Annual prepay saves 15% across all tiers.

What you actually get with us

Seven operational details the cheap providers skip

Below are seven structural differences in how we operate the dedicated hosting product. Most are invisible until something breaks. The cheap-provider model assumes you handle these yourself, and most teams underestimate how much time that takes until they live through it.

ECC RAM in every node, no exceptions

Some budget providers ship non-ECC memory in their entry tiers because it cuts hardware cost by around 8%. The trade is silent bit flips that corrupt data and crash workloads weeks after deployment, with no error trail. Every node we deploy has ECC RAM and ECC reporting enabled at the OS level, so when something does go wrong you see it in the logs instead of debugging mystery crashes.

Volumetric DDoS protection included on every tier

Network-level DDoS mitigation up to 100 Gbps included by default on every node. If your service is large enough to attract the kind of attacks that get past 100 Gbps mitigation, we coordinate with our upstream provider for additional capacity at no surprise cost. Layer 7 mitigation (application-layer, requires inline inspection) is available as an add-on for customers with public web endpoints under regular attack.

Hardware replacement SLA documented in writing

When hardware fails, and over enough nodes it eventually does, we replace it within the SLA window. 4 hours during business hours, 8 hours after-hours and weekends. The clock starts from the moment the failure is detected, not the moment a ticket is opened. This is the difference between a maintenance event and an outage.

Engineer-level support, no first-line tier

When you open a ticket, the response comes from an engineer who has root on the boxes and knows what every Linux subsystem does. Average first-response time on dedicated tickets in 2025 was 26 minutes during business hours. We use this as differentiator copy because it is a real differentiator. The cheap providers route you through a tiered support structure where the first three responses are from someone reading a script.

Real multi-PoP networking with private interconnect

When you provision nodes in multiple PoPs (Vienna primary, Frankfurt secondary, for instance), the cross-PoP traffic goes over our backbone, not the public internet. Private interconnect means consistent latency and no surprise charges for cross-region data transfer. Most cheap providers either do not offer multi-PoP or charge bandwidth for cross-region traffic the way the cloud hyperscalers do.

EU sovereign by construction, not by Frankfurt-region wash

OS Domains GmbH is a Austrian entity. The infrastructure runs on EU sub-processors only. There is no US parent that can be served a Cloud Act warrant. There is no "EU region" that fails over to North Virginia under load. For regulated EU buyers in financial services, healthcare, public sector, EU enterprise, this is often the deciding factor over the technical features.

Predictable maintenance windows, never surprise reboots

Every planned maintenance event gets 7 days of advance notice and is scheduled inside a documented window (Sunday nights, 02:00 to 06:00 UTC by default, or your preferred window if you tell us during onboarding). We do not roll out kernel updates that require reboots without notice. We do not do silent infrastructure upgrades that affect customer workloads. We have not had an unplanned reboot caused by our maintenance in the last 18 months and we are not going to start now. The only customer-facing reboots we cause are documented, scheduled, and visible on the status page in advance.

Real questions from systems engineers and CTOs

What technical buyers ask before they sign

Why would we host with you instead of Hetzner at half the price?

Honest answer: for many teams, you would not. Hetzner is excellent at what it does, the hardware is solid, the price-to-performance is unbeatable in Europe. We win in three specific scenarios. First: when you need EU sovereignty stronger than "German company" — Hetzner is a strong German operator, but their group structure has less clean separation from US partnerships than ours, and our Austrian GmbH structure with EU-only sub-processors is sometimes the easier audit answer. Second: when you want operational support, not pure self-service — Hetzner does not offer managed operations and does not pretend to. Third: when you need multi-PoP coverage beyond Hetzner's footprint, particularly the UK or Panama options. If none of those scenarios apply, Hetzner is genuinely a fine choice and we will tell you that on a discovery call.

How does the managed operations add-on work in practice?

You give us monitoring hooks (or we set up Prometheus and Grafana for you), you tell us which alerts you want us to action, and we set up an on-call rotation. When an alert fires, an engineer investigates within the SLA window (15 minutes for critical, 1 hour for warning). For incidents that require action — failed disk, runaway process, network issue, OS crash — we execute the remediation. We do not touch your application code or your data; the boundary is "everything OS-level and below". For application-level incidents, we escalate to your team. The €199/month per node covers a typical workload. If your environment is unusually noisy (more than 5 high-priority incidents per month sustained), we may have a conversation about adjusting the contract.

What operating systems do you support?

Debian 12, Ubuntu 24.04 LTS, AlmaLinux 9, Rocky Linux 9, and RHEL 9 with valid Red Hat subscription that you bring. Windows Server is available on request but we do not actively recommend it for the workloads our customers typically run. FreeBSD and other niche OSes can be installed on request for an extra setup fee. The default is Debian 12 unless you specify otherwise during onboarding. Custom OS images can be provided via our deployment API or as ISO upload.

How do backups work?

You have three options. First: bring your own backup solution (Restic, BorgBackup, Duplicacy, your existing offsite backup target) — most customers do this. Second: use our managed backup add-on at €0.02 per GB-month, which orchestrates daily snapshots to our EU-based object storage with point-in-time recovery up to 30 days. Third: integrate with cloud object storage of your choice (we recommend Backblaze B2 EU region for cost, or Wasabi EU region for predictable pricing). The managed backup add-on includes restore testing once per quarter and documented restore procedures. We are not a backup company — we just provide enough hooks to do this right.

Can we run our own hypervisor on top of bare metal?

Yes, that is a common pattern. KVM, Proxmox VE, VMware vSphere, and ESXi all run cleanly on our hardware. Customers who run their own hypervisors typically do so for one of three reasons: cost optimization across multiple workloads on a single physical box, license-driven requirements (Windows licensing in particular is much cheaper if you control the underlying hardware), or VM-density use cases that do not fit neatly into cloud pricing. Our hardware is virtualization-friendly: ECC RAM, AMD-V or Intel VT-x enabled in BIOS by default, IOMMU support for PCI passthrough.

What about GPUs for ML workloads?

Available on Custom tier with case-by-case pricing. We have stock of NVIDIA L4 (cost-effective inference, around €1,200/month per node), L40S (heavier inference and lighter training, around €2,400/month), and H100 (training, around €4,500-€5,500/month depending on configuration). We do not stock A100 anymore because L40S has displaced it for most workloads. For customers who need a single GPU node for evaluation, we can do month-to-month. For ongoing GPU capacity (training pipelines, persistent inference workloads), annual contracts come with better pricing.

Do you provide DDoS mitigation strong enough for game servers or high-profile public services?

Volumetric mitigation up to 100 Gbps is included by default on every node and handles the vast majority of attacks against typical web applications. For services that attract bigger attacks — public game servers, popular SaaS apps, anything political — we have arrangements with our upstream for additional capacity, and we offer a layer-7 mitigation add-on (€99/month per node) that handles application-layer attacks (HTTP floods, slow loris, request smuggling). The combination handles real-world attacks well, but if your threat model includes nation-state-level adversaries we are not the right vendor — that level requires specialized DDoS providers (Cloudflare Magic Transit, Akamai Prolexic) and we will tell you that.

Can we get dedicated network connectivity to our office or another datacenter?

Yes. We support cross-connects within our PoPs (we have presence at major colos in each city), VPN concentrator setups for IPsec or WireGuard tunnels back to your office, and dedicated layer-2 transport between our PoPs and any other datacenter that has a presence in the same exchange. The cross-connect option is most common for customers who already colocate elsewhere and want our boxes integrated into their existing network. Talk to us during onboarding for the specific arrangement.

What happens if your Vienna datacenter has a major incident?

Vienna is our primary PoP and the one we operate ourselves; the others are colocated with reputable third-party datacenter operators where we have racks. If Vienna has an incident, customers with multi-PoP setups (HA Cluster across PoPs, or workloads replicated to Frankfurt as DR) keep running with minimal impact. Customers running in Vienna only would experience an outage during the incident. We document incident history publicly on the status page; the worst event in the last 5 years was a 47-minute regional network issue in Q3 2025, no hardware loss. We are not promising no incidents will ever happen — we are promising they will be rare and we will be honest about them when they do.

How does pricing work for a workload that needs to scale up and down?

Bare metal does not flex the way cloud VMs do — that is the trade-off. For workloads that need genuine elasticity, cloud is the right answer and we will tell you that. For workloads that are mostly steady with occasional bursts, the right pattern is dedicated baseline + cloud spillover for peaks. Many customers run their steady workloads with us and burst into AWS/GCP/Azure for peaks via a hybrid setup. We can help configure this during onboarding. If your workload is genuinely elastic with 10x daily peaks, you should probably stay on cloud and revisit when the steady baseline grows enough.

Is there a way to test the infrastructure before committing?

Yes, two options. First: month-to-month billing on every tier with no setup fee for the Single Node tier — you can run for 30 days and cancel if it does not work. Second: for the Performance Node tier, we offer a 14-day evaluation at half price for first-time customers, no commitment. The Custom tier requires more upfront discovery but we structure the first 90 days as a structured evaluation period with milestones. We do not offer free trials — the hardware cost is real and free trials in dedicated hosting tend to attract customers who never convert.

How does compliance work for regulated workloads (HIPAA, PCI DSS, ISO 27001)?

For HIPAA, we offer a BAA addendum to the standard DPA on Performance Node and above. For PCI DSS, our infrastructure is in scope as a "service provider" in your audit, and we provide the documentation needed for your QSA — control mappings and audit logs covering the controls relevant to PCI Section 12. We do not currently hold SOC 2 or ISO 27001, but we provide pre-certification control evidence on request. For specific compliance scenarios that are not covered by these standards (DORA, NIS2, sector-specific requirements), we have a compliance contact who works with your team during onboarding to design the appropriate contractual structure.

What is your stance on customers running questionable content?

We have an Acceptable Use Policy and we enforce it. We do not host child sexual abuse material, terrorism content, malware command-and-control infrastructure, or anything illegal under Austrian or EU law. Beyond that, we are jurisdiction-aware: hosting decisions sometimes depend on which PoP your workload sits in. Content that is legal in Panama may not be legal in Frankfurt and vice versa. We work with customers to put workloads in the right jurisdiction. We do not host phishing infrastructure, scam operations, or cryptocurrency mining as a primary business model. We do host adult content (legal and consensual), cryptocurrency exchanges with proper KYC, gambling operators with valid licenses, and political content (across the spectrum) that is legal in the relevant jurisdiction. The AUP is on the legal page; read it before signing if there is any doubt.

Can we move our existing infrastructure to you in stages, or does it have to be all at once?

Stages, almost always. Most customers migrate one workload at a time over 4 to 12 weeks. The typical pattern: start with a single non-critical workload (a CI runner, a staging environment, a development database) on the new infrastructure, run it for 2 to 4 weeks to validate the setup, then move a production workload, then another. By the time you cut over the last critical workload, you have months of operational experience with us and the migration risk is much lower than a big-bang switchover. For customers migrating off cloud, we offer a hybrid setup option where your old cloud infrastructure and our new dedicated infrastructure coexist in a single VPC via VPN tunnel during the transition. This costs nothing extra on our side; you just keep paying the cloud provider until you fully cut over.

What is the network setup for dedicated servers?

Each server gets redundant high-capacity uplinks with DDoS protection at the edge, dedicated IPs, and the option on Enterprise to announce your own IP allocation. Datacenter locations are EU-resident plus North America and Panama, and you choose where your server sits during configuration. We keep the internal routing and addressing detail private, but we are happy to walk through the setup relevant to your use case under NDA.

How do you handle hardware end-of-life and refresh cycles?

Standard refresh cycle is 3 to 4 years from initial deployment. Hardware that has been in service longer typically gets retired or moved to lower-tier roles (development, internal use, lower-priority workloads). When a customer is on hardware approaching end-of-life, we contact them 90 days before the planned retirement and offer either a free migration to newer hardware in the same tier or, for customers running stable workloads on amortized hardware that does not need to move, the option to stay on the existing hardware at the same price for an extended period. We do not force migrations as a revenue tactic. Hardware refreshes are operationally expensive for us too and we coordinate them around your maintenance windows when possible.

Three ways to start

Most decisions on this page get made on a discovery call

Dedicated infrastructure decisions are not the kind that gets made off a pricing page. The right configuration depends on your workload profile, your team capacity, your compliance constraints, your existing investments. The discovery call is 45 minutes and you walk away with a written architecture proposal whether or not you become a customer.

Phone +43 1 205 11 80 Mon–Fri · 9–18 CET
Email [email protected] Avg response 4h business
Office Fleischmarkt 1, 1010 Wien By appointment