Skip to content
View from space of the night side of the Earth: the globe fills the lower half of the image as a broad arc, Europe is in the middle — Italy, the Iberian Peninsula, the British Isles and Scandinavia can be recognised by the golden dot networks of city lights, the seas remain black. Above the horizon is a narrow, purple-glowing atmospheric arc, above it a deep purple sky with fine stars. Stylised clouds glowing purple-white from the inside float above the globe: two small ones one above the other on the left, a large one on the right. Thin bright arcs run down from the clouds to the globe and end there in small green glowing dots, further arcs stretch high up between the clouds. The centre of the image remains empty.

Public Cloud from data centres in Germany and Finland: cloud servers in 39 instance types and 11 product groups, configure them here, add them to the cart and manage them in your account after checkout. The term is tracked by the second, billed by the hour, capped monthly.

Entry
€5.99$6.95
NX2, monthly net
Delivery
under 60 s
on average 35 seconds, guaranteed under 60 seconds
Instance types
39
7 series in 6 families
Locations
3
in Germany and Finland

Project, size, location, image (the operating system of the instance) and backup — the amount is updated next to it after every decision, calculated just like in the configurator and checkout. One click adds the instance to the cart; egress, the outbound traffic to the internet, is included per instance.

Always included

  • at least 20 TB egressper instance and month
  • IPv4 and IPv6 /64included in the instance price
  • no setup feewith every instance type
  • billed per hourcapped at the monthly price
  • Deliveryon average 35 seconds, guaranteed under 60 seconds

What should run on it? optional

Content management system or shop including database on one instance — shared x86 cores are sufficient as long as the load comes in peaks and is not constant. NX3 is the smallest size in the NX series with at least 8 GB memory.

Family and size

€8.99$10.43net / month

Cost-optimised for development, small services and bursty workloads. CPU time is shared fairly.

Series

Size in vCPU, i.e. virtual processor cores

2 vCPU · NX216 vCPU · NX5

NX38 GB RAM80 GB NVMe20 TB traffic

Location

Location factor 1.00 in Düsseldorf: the catalogue price applies. The milliseconds are the median latency from Frankfurt.

Image Operating system

The image is the operating system with which the instance starts; on the first boot, cloud-init sets up users, SSH keys and the network. Ubuntu 24.04 LTS requires no licence.

Backup

You are responsible for backups yourself. The amount applies per instance and is the same at every location.

Public network

included

The primary IPv4 address is included in the instance price. If you deselect it, you will only be reachable inbound from IPv6 networks — and you can add it later at any time.

Quantity

1 to 20 identical instances; the balance calculates all amounts with the quantity.

Expected traffic outbound, per month

1 TB200 TB

20 TB outbound is within the included volume of NX3 — nothing is added. Included: 20 TB. Every additional terabyte of outbound traffic (egress) costs €1.09$1.26 net, without zone pricing; inbound traffic is free.

NX3 · Net per month€8.99$10.43€10.70$12.41 incl. VAT€0.0123$0.0143/hSummary

From order to first connection

Three steps in the order they occur: order, scale, stay within the EU legal framework. Every instance runs in data centres in Germany and Finland.

  1. Three identical server cabinets stand frontally next to each other in a dark, purple-lit room; further cabinets behind them to the left and right, unlit. The left cabinet is dark except for a single small glowing dot in the middle of its door. In the middle one, the slots in the lower half glow purple, the upper half is still dark. The right one is occupied from top to bottom and glows in three blocks from purple to almost white; the light falls forward through the perforated panels and lies as a soft reflection on the smooth dark floor.

    Ordered — and ready in seconds

    You configure your instance on this page, add it to the cart and proceed to checkout. Your account is created there — an email address and password are sufficient, and the billing address follows with the first order. There is no minimum term, nor is there a setup fee.

    After payment, the instance transitions via BUILD and BOOT to the ACTIVE state — on average 35 seconds, guaranteed under 60 seconds. You access it via SSH key, in the console or with an API token; every transition is recorded with a timestamp in the project's activity log.

    Configure instance

  2. A straight row of identical server cabinets runs diagonally from the front left to the right into the depth of a dark, purple-lit room. The foremost one stands large and close: a perforated door, behind which the slots glow purple to almost white, a small green status dot at the top of the door. Behind it, the same cabinet follows again and again at equal distances, each slightly smaller and glowing more faintly, until the rearmost ones are just purple blocks of light. The smooth floor reflects its light under each cabinet.

    Scale when the load comes

    A scaling group — an instance template with a capacity range and rules — comprises 1 to 200 instances; its rules are evaluated every 30 seconds. The shortest cooldown, the lockout period after an adjustment during which no further adjustment is triggered, is 60 seconds.

    Where a share of a server is no longer sufficient, an entire node without a hypervisor is available in the same project and in the same private network, i.e. without the virtualisation layer between hardware and operating system. The “Metal” section draws the line row by row.

    Auto scaling in detail

  3. A heavy, almost square vault door is set frontally into a dark wall. It protrudes a hand's breadth from the wall, its chamfered edge catching a narrow rim of light all around; on the left sit three massive hinge cylinders, on the right five extended locking bolts engage with the frame. Set into the door surface is a square, internally illuminated area in pale lilac. On it, at the top, is the flag of the European Union — twelve golden stars in a circle on a blue background — and below it, in dark lettering, the ENTRONYX CLOUD wordmark. The light from this surface falls as a broad, bright spot on the polished floor in front of it and illuminates the wall on both sides. Set into the wall is Europe at night, as a fine, warm network of city lights. On this map, three location points shine significantly brighter than the cities around them: one near Frankfurt am Main, one near Düsseldorf and, far off in the northeast, one near Helsinki.

    Stay within EU jurisdiction

    The cloud runs at 3 locations in Germany and Finland, 2 of which are in Germany. Not every family is available at every location: storage and GPU models require special chassis, i.e. specially designed enclosures.

    Outbound traffic has no zone tariff, i.e. no separate rate per destination region. At least 20 TB are included per instance, above which a single rate of €1.09$1.26 per terabyte applies — regardless of where the recipient is located. Inbound traffic is always free of charge.

    Availability per location

View across the full width along a row of black server racks. A busbar runs on galvanised brackets above the rack heads: a straight aluminium housing, from whose open underside two bare copper bars are visible, with evenly clipped-in grey tap-off boxes, from each of which a short hose leads into a rack. On the left, two racks are open and completely filled with identical 1U servers, each with a green status light. In the centre of the image, the smooth flank of a rack is turned towards the camera; on it sits a large transverse brushed aluminium plaque with four countersunk screws and the embedded inscription ENTRONYX CLOUD. On the right, the row ends at a light wall above a light raised floor.

All product groups in this area run in the same rows, on the same device family and on the same power rail. They are separated by allocation and guarantee, not by location — which is why traffic between them in the private network incurs no transit costs. The badge on the side of the rack bears the ENTRONYX CLOUD brand.

The entire section, sorted by tasks

11 groups from compute to developer tools. All are billed according to the same model, all can be controlled via the same API, and all are located in the same projects.

Choose the load profile first, then the size

The series identifier tells you how CPU time is allocated and what core-to-memory ratio you get. The number after it is just the size.

NXNP

Shared vCPU

Cost-optimised for development, small services and bursty workloads. CPU time is shared fairly.

NX runs on Intel/AMD x86, NP on AMD EPYC with twice as much local NVMe per vCPU.

For services that are rarely under full load for long: Web frontends and blogs with low traffic · Development and staging · Cron jobs and short build runs

Types
10
vCPU
1–16
RAM max.
32 GB
from
€5.99$6.95
ND

Dedicated vCPU

A physical core belongs exclusively to your instance. Constant performance without steal time — and from 64 vCPU, it is worth looking at TITAN bare metal.

A physical core is strictly assigned via cpuset: no neighbour, no quota, no steal time — the waiting time during which the core belongs to a neighbour.

For consistent continuous load without neighbours on the core: Production databases · API backends with latency requirements · Kubernetes-Worker and CI-Runner

Types
7
vCPU
2–128
RAM max.
512 GB
from
€38.80$45.01
NM

Memory-optimised

8 GB RAM per vCPU for in-memory databases, caches and analytics.

8 GB memory per vCPU, on dedicated cores.

For data that must reside entirely in memory: In-memory databases · Caches with a large working set · Analyses across entire datasets

Types
5
vCPU
2–32
RAM max.
256 GB
from
€48.40$56.14
NS

Storage-optimised

Up to 7.68 TB local NVMe directly attached to the instance — without network latency.

NVMe is attached directly to the instance's PCIe bus. No network storage, but bound to the instance.

For workloads that depend on local NVMe: Search indices · Delivery nodes with local cache · Replicated databases with a high write ratio

Types
3
vCPU
4–16
RAM max.
64 GB
from
€220.00$255.20
NA

ARM / Ampere

Shared Ampere Altra cores for ARM64 workloads built and tested on ARM. Windows Server does not run on this series.

Shared Ampere-Altra cores for arm64 software, from €6.49$7.53 net per month.

For software available as arm64: Container fleets · Horizontally scaled web services · Build nodes for arm64 images

Types
4
vCPU
2–16
RAM max.
32 GB
from
€6.49$7.53
NG

GPU

RTX PRO 4000 (24 GB GDDR7) up to H200 cluster (8 × 141 GB HBM3e) for inference, fine-tuning and distributed training — single cards plus NVLink scaling for H100/H200.

Training costs, allocation model and availability are on the GPU page.

For computing on the GPU: Inference · Fine-tuning · Distributed training

Types
10
vCPU
8–128
RAM max.
2 TB
from
€214.00$248.24

Six profiles, seven series: NX and NP share the “Shared vCPU” profile, because both are scheduled according to the same fair use policy — they differ in platform and local storage, not in the allocation model. The graphics cards of the NG family range from RTX PRO 4000 to H200.

Hardware per series and images — processor, clock speed, memory, operating systems

One row per series: processor, ranges and the amounts you can use to calculate without a calculator. List prices for Frankfurt, net and without a fixed term; the quick configurator at the top of the page adds the location factor and traffic.

  • NXShared vCPU

    from €5.99$6.95

    Intel/AMD x86vCPU shared

    vCPU
    2–16
    RAM
    4–32 GB
    NVMe
    40–320 GB
    per hour
    €0.0082$0.0095
    per vCPU per month
    from €1.87$2.17

    Generation · clock speed · connection: — · — · —

    Configure — series NX, from NX2
  • NPShared vCPU

    from €11.99$13.91

    AMD EPYCvCPU shared

    vCPU
    1–16
    RAM
    2–32 GB
    NVMe
    40–640 GB
    per hour
    €0.0164$0.0191
    per vCPU per month
    from €8.16$9.46

    Generation · clock speed · connection: — · — · —

    Configure — series NP, from NP1
  • NDDedicated vCPU

    from €38.80$45.01

    AMD EPYCvCPU Dedicated

    vCPU
    2–128
    RAM
    8–512 GB
    NVMe
    80 GB – 2.4 TB
    per hour
    €0.0532$0.0617
    per vCPU per month
    from €16.69$19.36

    Generation · clock speed · connection: — · — · —

    Configure — series ND, from ND2
  • NMMemory-optimised

    from €48.40$56.14

    AMD EPYCvCPU Dedicated

    vCPU
    2–32
    RAM
    16–256 GB
    NVMe
    80–960 GB
    per hour
    €0.0663$0.0769
    per vCPU per month
    from €24.16$28.02

    Generation · clock speed · connection: — · — · —

    Configure — series NM, from NM2
  • NSStorage-optimised

    from €220.00$255.20

    AMD EPYCvCPU Dedicated

    vCPU
    4–16
    RAM
    16–64 GB
    NVMe
    1.92–7.68 TB
    per hour
    €0.3014$0.3496
    per vCPU per month
    from €55.00$63.80

    Generation · clock speed · connection: — · — · —

    Configure — series NS, from NS3
  • NAARM / Ampere

    from €6.49$7.53

    Ampere AltravCPU shared

    vCPU
    2–16
    RAM
    4–32 GB
    NVMe
    40–320 GB
    per hour
    €0.0089$0.0103
    per vCPU per month
    from €2.59$3.01

    Generation · clock speed · connection: — · — · —

    Configure — series NA, from NA2
  • NGGPU

    from €214.00$248.24

    AMD EPYC · Intel Core i5-13500 (14 cores, 20 threads) · Intel Xeon Gold 5412U (24 cores, 48 threads)vCPU Dedicated

    vCPU
    8–128
    RAM
    48 GB – 2 TB
    NVMe
    400 GB – 30.72 TB
    per hour
    €0.2932$0.3401
    per vCPU per month
    from €10.70$12.41

    Generation · clock speed · connection: — · — · —

    Configure — series NG, from NG-RTX4000

“—” means: the catalogue does not list the value per series. The vCPU series run on hosts without a fixed processor model; a model with cores and threads is only listed where the hardware of a node is fixed. We state generation, clock speed and connection as soon as they are documented per series.

Images

12 operating systems are available for cloud instances in the configurator. Without a licence specification, an image costs nothing extra.

  • Ubuntu24.04 LTS
  • Ubuntu26.04 LTS
  • Debian13 (Trixie)
  • Debian12 (Bookworm)
  • Rocky Linux10
  • AlmaLinux10
  • Fedora Server43
  • openSUSE Leap16.0
  • Talos Linux1.14· from 4 GB RAM
  • Flatcar Container Linuxstable
  • FreeBSD15.1
  • Windows Server2025 Standard· from 8 GB RAM· licence €28.00$32.48 per month

All instance types compared

Prices apply to Frankfurt. The hourly rate is the monthly price divided by 730 hours and rounded to four decimal places. The chips change the family, “All families” shows the entire catalogue; “Configure” transfers the size of a row into the configurator above.

The table is wider than the screen and can be scrolled horizontally.

10 Instance types displayed· cheapest row €5.99$6.95 per month

All cloud instance types with vCPU, CPU type, memory, local NVMe, included traffic, and hourly and monthly price
InstanceFamilyvCPUCPU typeRAMLocal NVMeTrafficPrice / hourPrice / monthSelect in the configurator
NX2EntryNX2Intel/AMD x86 (shared)4 GB40 GB20 TB€0.0082$0.0095€5.99$6.95
NX3NX4Intel/AMD x86 (shared)8 GB80 GB20 TB€0.0123$0.0143€8.99$10.43
NX4NX8Intel/AMD x86 (shared)16 GB160 GB20 TB€0.0226$0.0262€16.49$19.13
NX5NX16Intel/AMD x86 (shared)32 GB320 GB20 TB€0.0411$0.0477€29.99$34.79
NP1NP1AMD EPYC (shared)2 GB40 GB20 TB€0.0164$0.0190€11.99$13.91
NP2NP2AMD EPYC (shared)4 GB80 GB20 TB€0.0274$0.0318€19.99$23.19
NP3BestsellerNP4AMD EPYC (shared)8 GB160 GB20 TB€0.0493$0.0572€35.99$41.75
NP4NP8AMD EPYC (shared)16 GB320 GB20 TB€0.0959$0.1112€69.99$81.19
NP5NP12AMD EPYC (shared)24 GB480 GB20 TB€0.1383$0.1604€100.99$117.15
NP6NP16AMD EPYC (shared)32 GB640 GB20 TB€0.1788$0.2074€130.49$151.37

Shared or dedicated — the difference is measurable

A vCPU is a time share of a physical core. How it is allocated determines your latency under load, not when idle.

With the shared families NX and NP, the hypervisor schedules multiple instances on the same physical core: each vCPU gets a quota, and whoever does not exhaust it passes the share to their neighbours. If your instance waits for a neighbour, the guest system shows this steal time as %st in top, vmstat or mpstat.

Instead of hard throttling, a shared vCPU works with credits: up to 20 minutes per hour of full core performance, then the base share of 25% per vCPU for NX and 40% for NP; unused credits are saved for up to eight hours. The rule of thumb from operations: if the average utilisation of a vCPU over a week is permanently above 20%, a dedicated instance is cheaper per unit of work done.

Allocation models compared: shared vCPU, dedicated x86 cores and shared ARM cores
FeatureNX / NPShared vCPUND / NM / NSDedicated x86 coresNAShared ARM cores
CPU allocationHow the core is allocatedQuota in the scheduler, core is sharedcpuset, core permanently assignedCore is shared
Steal time%st in the guest systemAverage < 3%, peaks up to 12%0% by designvisible, no measured value shown
Recommended continuous loadup to 20% per vCPU on weekly average100%, permanentlyno base share shown
Price per vCPU / monthFrankfurt, no commitment€1.87$2.17 – €11.99$13.91€16.69$19.36 – €19.40$22.50€2.59$3.00 – €3.25$3.77
Instruction setx86-64 (Intel or AMD)x86-64 (AMD EPYC)arm64 — custom images required
Typical useDevelopment, staging, web frontends, cronjobsDatabases, API backends, CI runners, Kubernetes workersCloud-native services, container fleets, horizontal scaling
Not suitable forContinuous load, real-time, licensed core countingCost-optimised test environmentsSoftware without arm64 build, Windows

If you want the machine all to yourself

Dedicated servers without a hypervisor — in the same project, in the same vRack and with the same access credentials as your instances. Four series, 17 configurations, from €65.54$76.03 per month.

  • COREDedicated hardware at an entry-level price4 models · from €65.54$76.03
  • FORGEThe server platform that grows with you4 models · from €90.75$105.27
  • TITANCore density6 models · from €299.99$347.99
  • VAULTStorage density3 models · from €165.54$192.03

The models with processor, memory configuration, drives and connection are listed in full on the dedicated servers page. This just explains when switching is actually worthwhile.

Dedicated vCPU (ND series, largest expansion stage ND8 with 128 vCPU) compared to the dedicated server
FeatureDedicated vCPUMetal
What you renta share of a serverthe server
Hypervisorpresent, you see a virtual machinenone, you boot on the metal
Core allocationfixed vCPU via cpusetall cores of the processor
Billinghourly, capped per monthMonthly rent; setup fee only with monthly term
Deliveryon average 35 seconds, guaranteed under 60 secondsusually 90 minutes for stock items, up to 24 hours for build to order
Hardware accessnoneIPMI, RAID control, BIOS
Licences by core countcounted per vCPU, evidence complexcounted per socket and core, unambiguous
Private networkvRack, shared with the instancesvRack, shared with the instances

Scaling groups instead of gut feeling

A scaling group consists of an instance template, a capacity range and rules. The evaluation runs every 30 seconds against metrics we collect anyway.

Metrics

CPU and memory average across the group, active connections and requests per second at the Load Balancer, as well as any custom values via the Prometheus-compatible endpoint.

Response time

Evaluation every 30 seconds, shortest cooldown 60 seconds. Provisioning a new instance from a standard image takes on average 35 seconds, guaranteed under 60 seconds.

Capacity

1 to 200 instances per group, up to 25 groups per project. A warm pool keeps prepared, stopped instances ready for load spikes with short notice.

Scale down

When scaling in, instances are first deregistered, then drained for 120 seconds, then deleted. Instances with scale-in protection remain, such as the leader of a consensus algorithm.

scaling-group.yaml
name:   web-tier
region: fra1
template:
  flavor:      np3
  image:       ubuntu-2404
  private_net: vrack-prod
capacity: { min: 2, max: 12, desired: 3 }
 
policies:
  - name:       scale-out-cpu
    metric:     cpu_avg      # Average across all instances in the group
    comparison: ">"
    threshold:  65           # percent
    periods:    3            # 3 × 30 s must be exceeded
    change:     +2
    cooldown:   180
  - name:       scale-in-cpu
    metric:     cpu_avg
    comparison: "<"
    threshold:  25
    periods:    6
    change:     -1
    cooldown:   300
health_check: { type: http, path: /healthz, interval: 15, unhealthy_after: 3 }
drain_seconds:    120
scale_in_protect: ["web-tier-leader"]
Apply with entronyx compute autoscale apply -f scaling-group.yaml. Changes to the template only affect newly created instances; existing ones are replaced by a rolling replacement.

Functions on demand — in preparation

This service does not exist yet. It is in progress, but we are not giving a date because we cannot commit to one. What is possible in its place today already covers most cases.

What the service should be able to do

In preparation · no date
  • Triggers via HTTP, queue and schedule — without your own listener in front
  • Scaling to zero, so a service without requests costs nothing
  • Billing by execution time instead of the runtime of a machine
  • Custom container image instead of predefined runtime environments
  • The same API, the same CLI and the same Terraform provider as for instances

5 points as an intention, not a commitment, without pre-ordering. We will only quote a price once the service is available — then per execution second, with cold start time and limits per project.

What is possible here today

Peak loads: scaling groups

Rule-based between 1 and 200 instances, evaluation every 30 seconds, warm pool for short warning times. This covers the most common reason people ask for serverless — load that does not occur evenly.

View Auto Scaling

Tasks without continuous operation: Kubernetes

Jobs and CronJobs start a container, process it and terminate it. The control plane of the managed cluster is included in the standard plan at no extra charge; you pay for the nodes underneath.

Managed Kubernetes

Short-lived compute time: instances via the API

Provisioning takes on average 35 seconds, guaranteed under 60 seconds; the runtime is recorded to the second and billed by the hour. For tasks that run for minutes to hours, this is a cheaper calculation than any execution fee.

API and Terraform

Billed hourly, capped monthly

We log the start and stop of every instance to the second. The invoice still shows an hourly figure — because an item that no one can verify is not transparent.

  1. 01

    Ingestion

    per second

    The term is logged to the second. Start, stop, resize and deletion are timestamped in the project's activity log and can be retrieved via the API.

  2. 02

    Rating

    per started hour

    Billing is at the hourly rate. The hourly rate is the monthly price divided by 730 — the average month length, not that of the respective calendar month.

  3. 03

    Cap

    Upper limit

    If the sum of an instance's hours in the calendar month reaches the monthly price, the counting stops. A 744-hour month never costs more than a 720-hour month.

  4. 04

    Term discount

    optional

    A 12-month commitment reduces the monthly price by 5%, a 24-month commitment by 8%; the committed instance is paid in advance for the term. Without a commitment, hourly billing remains.

Region factor

The catalogue price applies to Frankfurt. Every other location carries a factor that reflects the electricity price, network connection and local taxes. Example NP3 (4 vCPU, 8 GB):

  • Frankfurt am Mainfra1

    €35.99$41.75

    Factor 1.00 · 3 ms

  • Düsseldorfdus1

    €35.99$41.75

    Factor 1.00 · 4 ms

  • Helsinkihel1

    €33.83$39.24

    Factor 0.94 · 21 ms

Actual billed amount per term — the penultimate column shows a month with 744 hours in which the cap applies
InstanceHourly rate24 h100 h400 h744 hCap
NX22 vCPU · 4 GB€0.0082$0.0095€0.20$0.23€0.82$0.95€3.28$3.80€5.99$6.95€5.99$6.95
NP34 vCPU · 8 GB€0.0493$0.0572€1.18$1.37€4.93$5.72€19.72$22.88€35.99$41.75€35.99$41.75
ND34 vCPU · 16 GB€0.1063$0.1233€2.55$2.96€10.63$12.33€42.52$49.32€77.60$90.02€77.60$90.02
NM48 vCPU · 64 GB€0.2648$0.3072€6.36$7.38€26.48$30.72€105.92$122.87€193.30$224.23€193.30$224.23
NS34 vCPU · 16 GB€0.3014$0.3496€7.23$8.39€30.14$34.96€120.56$139.85€220.00$255.20€220.00$255.20

One interface for console, command line and Terraform

No reduced functionality for machines: what works in the console should work via REST, command line and Terraform provider. The interface is described as a draft in the documentation, command line and provider are in preparation. You can already create tokens in the console under Account today — bound to projects and restrictable to individual actions.

POST /v2/compute/instances — draft
# Draft of the future API. The base path is intentionally omitted: it is only stated once it resolves.
POST /v2/compute/instances
Authorization: Bearer <Token>
X-Entronyx-Project: prj_4c81f0
Idempotency-Key: 8f2c-web-01-2026-08
Content-Type: application/json
 
{
  "name":                  "web-01",
  "flavor":                "np3",
  "region":                "fra1",
  "image":                 "ubuntu-2404",
  "ssh_keys":              ["ops-2026"],
  "private_network":       "vnet_prod",
  "backup_retention_days": 14
}
 
HTTP 201
x-request-id: req_4c81f0a9
 
{
  "id":     "inst_4c81f0",
  "state":  "building",
  "flavor": "np3",
  "region": "fra1",
  "price":  { "hourly_net": 0.0493, "monthly_cap_net": 35.99 }
}
Draft: the response carries 201 and the instance ID. The state changes via building to running; it takes on average 35 seconds, guaranteed under 60 seconds until the first SSH connection.
Command line — draft
# Draft of the future command line — in preparation.
 
# Filter catalogue — same data as in the table above
entronyx compute flavor list --family dedicated --region fra1
 
# Create instance and wait until ACTIVE state
entronyx compute instance create nd3-prod-01 \
  --flavor nd3 --image ubuntu-2404 --region fra1 \
  --ssh-key ops-2026 --private-net vrack-prod --wait
 
# Running costs of the current billing period
entronyx billing usage --since month-start --group-by flavor --output table
The command line is in preparation. It is planned to read the same tokens from ENTRONYX_TOKEN and pass every output to scripts with --output json.
main.tf — draft
terraform {
  required_providers {
    entronyx = {
      # Draft: the provider is in preparation; its release will state source and version.
      source  = "<Quelle>"
      version = "<Version>"
    }
  }
}
 
provider "entronyx" {
  region = "fra1" # Token comes from ENTRONYX_TOKEN
}
 
resource "entronyx_vrack" "prod" {
  name = "vrack-prod"
  cidr = "10.42.0.0/16"
}
 
resource "entronyx_instance" "web" {
  count       = 3
  name        = "web-${count.index + 1}"
  flavor      = "np3"
  image       = "ubuntu-2404"
  ssh_keys    = ["ops-2026"]
  private_net = entronyx_vrack.prod.id
  backup      = "bk-snap"
}
Rate limit
3,000 requests/min
planned per project and token, header X-RateLimit-Remaining
Versioning
v2 in the path
older versions deprecated twelve months in advance
Idempotency
Idempotency-Key
a repeated call only takes effect once; valid for 24 hours
Terraform provider
in preparation
source and version stated in the release

Not every family is available at every location

Storage and GPU families require special chassis and are therefore only located where the corresponding racks are installed. The table shows how many of the 39 instance types can be ordered at each location.

Cloud locations with number of bookable instance types, price factor compared to Frankfurt, connection latency, PUE and current occupancy
LocationDescriptionTypesFactorLatencyPUEOccupancy
Frankfurt am Mainfra1Location Rhein-Main39 / 391.003 ms1.1471%
Düsseldorfdus1Location Rhein-Ruhr39 / 391.004 ms1.1248%
Helsinkihel1Location Uusimaa39 / 390.9421 ms1.0836%

Occupancy above 80% does not mean that no more instances will start — it means that large types are temporarily unavailable there. For planned capacity from 50 instances or for GPU nodes, we recommend a reservation via sales.

Six points that can be verified

Every point carries a value from the catalogue or from a section of this page. An advantage without a number would be just as true on any competitor's page and is therefore not listed here.

  • One tariff for thirty-nine sizes

    Entry per month€5.99$6.95 net

    The term is recorded to the second, billed at the hourly rate and capped at the monthly price: a month with 744 hours never costs more than one with 720.

  • Outbound traffic without zone tariff

    Excess usage€1.09$1.26 per TB

    At least 20 TB of outbound traffic is included per instance. Above that, a single rate per terabyte applies, regardless of the destination.

  • Deployment in seconds

    Until ACTIVE stateunder 60 s

    From the call to the ACTIVE state, it takes on average 35 seconds, guaranteed under 60 seconds for standard images. The same order of magnitude applies to instances that a scaling group pulls in.

  • Everything via one interface

    InterfaceREST · CLI · Terraform

    No reduced functionality for machines: what works in the web interface works via REST, command line and the Terraform provider with the same calls. A p95 response time of the control plane — the time that 95 out of 100 calls do not exceed — is only shown here with the measurement period, endpoint and location. Without these three details, such a number is arbitrary.

  • Guaranteed availability

    Class B per month99.95%

    Cloud instances are in class B of the availability commitment. It is measured at the network connection and the control plane, not by the state of your application.

  • Processing without third-country transfer

    Locations outside the EUnone

    The cloud runs exclusively in Germany and Finland. No location is outside the EU; a third-country transfer within the meaning of the GDPR therefore does not take place. The data processing agreement according to Art. 28 is part of the main contract and not an addendum.

Three recurring situations

No company names, no quotes, no logos. Instead, each case names the starting situation, the chosen approach and a metric that you can look up in the tables on this page.

  • E-commerce

    Peak load on campaign day without permanent provisioning

    Initial situation

    Delivery ran on a fixed number of permanently running instances, designed for the busiest day of the year. On all other days, a large part of them was idle and was paid for anyway.

    Decision

    A scaling group of NP3 instances with evaluation every 30 seconds and 120 seconds of drainage during teardown — open connections are served to the end before an instance is deleted. The base load remains, the peak is paid by the hour and ends when the group is scaled down.

    Result

    €0.0493$0.0572

    Hourly rate per node of the group (NP3, Frankfurt, net)

    How it's built — Peak load on campaign day without permanent provisioning

  • Research and evaluation

    A dataset that must fit entirely into memory

    Initial situation

    The evaluation kept the entire dataset in memory. On shared cores, the runtime fluctuated depending on the neighbourhood on the same host: waiting time for the core arrived as steal time in the guest system — the time during which the core currently belongs to a neighbour.

    Decision

    The memory-optimised series with dedicated cores and 8 GB memory per vCPU. Steal time is zero there by design; the large models are only available at locations with the corresponding rack density.

  • Media delivery

    Outbound traffic as the largest item on the invoice

    Initial situation

    The previous provider charged outgoing traffic per target region with its own rate. The invoice could not be estimated in advance because it depended on the origin of the requests.

    Decision

    Delivery nodes of the storage-optimised series with local NVMe. The included volume grows with the model; above this, a single rate per terabyte applies, regardless of the destination.

    Result

    40 TB

    Outbound traffic included (NS3, per month)

    How it's built — Outbound traffic as the largest item on the invoice

What needs to be clarified before the first invoice

Questions from sales conversations and from the first month of operations — not the ones that are easy to answer.

What is a cloud server?

A cloud server is a virtual instance in the ENTRONYX CLOUD Public Cloud that runs in data centres in Germany and Finland: you choose from 39 instance types in 6 families, order with no setup fee and manage the instance after checkout in the account, via the API or the command line.

The entry-level NX2 costs €5.99 net per month; the term is tracked by the second, billed by the hour, capped monthly. A commitment of 12 or 24 months is optional and reduces the price by 5% and 8% respectively.

Do I need an account to order?

Not for prices, the configurator and the cart — all three are open without signing in. The account is created at checkout with account type, contact, email address and password; the billing address follows with the first order.

An account with ENTRONYX CLOUD is free of charge and does not tie you to a minimum term.

What happens after the order?

After payment, the instance appears under “Account › Services” and changes via BUILD and BOOT to the ACTIVE state — on average 35 seconds, guaranteed under 60 seconds.

You access it via SSH key, in the console or with an API token; the invoice is also in the account.

Cloud instance or VPS — what is the difference?

Both run on the same platform and are billed the same way: per hour, capped at the monthly price. The difference lies in the allocation of the core.

As a VPS you book the series with shared cores, NX, NP and NA, from €5.99 net per month. The series with dedicated cores, ND, NM and NS, start at €38.80.

The rule of thumb from operations: if the average load of a vCPU over a week is permanently above 20%, the dedicated series is cheaper per unit of work performed.

How fast is an instance ready?

From the call to the first SSH connection, standard images take on average 35 seconds, guaranteed under 60 seconds. The state changes via BUILD and BOOT to ACTIVE, with each transition timestamped in the project's activity log.

Instances pulled by a scaling group are ready in the same timeframe.

What does an instance cost if it only runs for a few hours?

Billing is per started hour at the hourly rate. The hourly rate is the monthly price divided by 730 — the average month length, not that of the respective calendar month.

The count is capped at the top: if the sum of an instance's hours in a calendar month reaches the monthly price, it stops. A month with 744 hours therefore never costs more than one with 720.

Do I continue to pay for a stopped instance?

Yes. A shut-down instance continues to occupy CPU quota, memory and local NVMe on the host and is therefore still billed.

Only deleting ends the billing. If you want to keep the state, create a snapshot beforehand, an image of the instance at that point in time. Snapshots appear on the invoice as a separate item.

What counts as egress, and what does it cost above the included volume?

Outbound traffic to the public internet counts as Egress. Inbound traffic, traffic between instances via the private network — even between locations — and access to Object Storage from instances in the same region are not counted.

Depending on the instance type, 20 TB to 200 TB of outbound traffic per month are included. Above this, we charge €1.09 per terabyte, without a zone tariff: a terabyte to a recipient on the other side of the world costs the same as one within Germany. The exception: NG-RTX4000, NG-RTX6000, NG-RTX6000-512 and NG-RTX6000-768 do not count outbound traffic at all — traffic is unlimited there.

How do I cancel an instance?

Without a minimum term, you delete the instance in the console, via the API or the command line. There is no notice period; billing ends at the time of deletion (Section 11 (3) of the Terms and Conditions). Stopping it is not enough.

Contracts with a 12 or 24-month term can be cancelled with a notice period of 30 calendar days to the end of the term, otherwise they are extended by twelve months (Section 11 (2) of the Terms and Conditions). Cancellations require text form; the cancellation function in the customer area fulfils this.

What is the difference between shared and dedicated vCPUs?

In the shared families, the hypervisor, the virtualisation layer of the host, schedules multiple instances on the same physical core. If you do not use your quota, you pass the share on to the neighbours — in return, the price per vCPU is lower.

Waiting time caused by neighbours is visible in the guest system as steal time — the time during which the core currently belongs to a neighbour. The monthly average on shared families is below 3%, and up to 12% during peak loads on individual hosts. On dedicated families, it is zero by design.

Is data retained on the local NVMe?

The specified capacity is physically located in the same server as the instance and is tied to its lifespan. It survives reboots, but not the deletion of the instance.

For data that must outlast an instance, Block Storage or Object Storage belong underneath. Both are separated from the compute node and can be attached to a new instance.

Can I resize an instance later?

Yes. Resizing is a logged action like start, stop and deletion and is recorded with a timestamp in the project's activity log. From this timestamp, the hourly rate of the new size applies.

A change of family is not covered by this, because the local NVMe is tied to the instance. The intended way for this is via a snapshot and a new instance.

Is every instance type available at every location?

No. 39 instance types are distributed across 3 locations in Germany and Finland. Storage and GPU designs require special chassis and power density and are therefore only located where the corresponding racks are installed.

The catalogue price applies to Frankfurt. Every other location carries a factor that reflects the electricity price, network connection and local taxes; the table in the "Billing" section calculates it using an example.

Do I have to commit to get the entry price?

No. €5.99 net is the monthly price without any commitment, and hourly billing applies unchanged.

A voluntary commitment lowers the price: 5% for 12 months, 8% for 24 months. The term is then paid in advance, at the discounted monthly price.

Can everything be controlled without the web interface?

That is the goal, but not yet the current status: no reduced functionality for machines — what works in the console should work via REST, via the command line and via the Terraform provider. The interface is described as a draft in the documentation, command line and provider are in preparation.

Authentication is done with project-bound tokens that can be restricted to individual actions; you can already create them in the console today. The plan is for 3,000 requests per minute and project. Write requests accept an idempotency key — a key that ensures a repeatedly sent request only takes effect once.

How fast does support respond, and how do I reach them?

Via ticket in the account: The price includes the basic support of the SLA with an initial response in 8 hours for critical incidents (P1), available Monday to Friday from 08:00 to 18:00. Initial response means: A human has accepted the report, classified it and reported back the processing status — the SLA does not guarantee a resolution time. In addition to basic support, it offers three further support levels; the highest responds to P1 in 15 minutes.

from · per month, net€5.99$6.95

Configure

Configure instance or query catalogue via API

The quick configurator adds your instance to the cart with one click; your ENTRONYX CLOUD account is created at checkout. You can add a block storage volume and extras in the configurator, which carries over your selection with all values. If you prefer automation, you can use the Terraform provider directly.

Delivery
under 60 s
Traffic included
20 TB
Excess usage
€1.09$1.26 / TB
SLA
99.95%