Storage billed by
usage

Name: Object, block and archive storage from ENTRONYX CLOUD
Brand: ENTRONYX CLOUD

Eight storage classes, from NVMe volume to tape archive. You are billed for the average capacity used per month, not the provisioned capacity. Egress — the traffic leaving our network — remains unbilled within ENTRONYX CLOUD and between our regions.

Configure storage Calculate costs

Reference values

Cheapest class: €0.0024$0.0028 per GB
Object Storage Standard: €0.0070$0.0081 per GB
Egress to the internet: €0.0000$0.0000 per GB
Egress in the ENTRONYX network: €0.0000$0.0000
Largest single object: 5 TB
Object Storage durability: 11 nines

All prices net. Billed hourly pro rata based on the bytes used.

Storage classes: 8; Object, block, file, archive, backup
Maximum capacity: 20 PB; per account in Cold Archive
IOPS per volume: 30,000; Block Storage NVMe
Locations: 4; with at least one storage class

Storage chassis pulled out on rails with open cover, containing rows of drives in a grid pattern.

Eight classes, three questions

Who needs access at the same time, how often data is read and how long it stays — that is all you need to choose. First, you choose between the three basic types, then between the classes within them.

First the basic type, then the class

The table below lists each class individually. The decision before that is a different and much smaller one: object, block or archive. All three answer the same three questions, which is why they are side by side here and in the same order in each card.

Vertically from above into an extended storage drawer: identical drives stand upright in metal carriers and form a continuous grid. — Per terabyte 2.9 times the archive — but every file is ready in milliseconds instead of hours.

A single storage drive caddy pulled halfway out of the slot, the backplane connector with golden contact rows visible at the rear end. — The most expensive of the three ways: 12.3 times the Object Storage per terabyte. You are not paying for space, but for proximity.

A closed tape cartridge made of matte black plastic on a grey surface, a milled recessed grip in grazing light. — The cheapest storage at ENTRONYX CLOUD — and the one with the fewest locations: a tape library is available at 1 of 4 locations.

All classes compared

The table compares each class with capacity range, price and durability, and links to the corresponding section. Outbound traffic is uncharged in 7 of the 8 classes; only the tape archive charges for it, because only the recovery touches the medium.

All storage classes at a glance. The TB price is the GB price multiplied by 1,024 and is for comparison only — billing is per occupied gigabyte.
Class	Section	Capacity	Price per GB	Price per TB	Egress per GB	Durability
Object Storage Standard	Object Storage	1 GB – 4882.8 TB	€0.0070$0.0081	€7.17$8.31	without charge	99.999999999% (11 nines)
Object Storage Performance	Object Storage	1 GB – 1953.1 TB	€0.0180$0.0209	€18.43$21.38	without charge	99.999999999% (11 nines)
Cold Archive	Cold Archive	1000 GB – 19531.3 TB	€0.0024$0.0028	€2.46$2.85	€0.0100$0.0116	99.999999999% (11 nines)
Block Storage NVMe	Block storage	10 GB – 64 TB	€0.0860$0.0998	€88.06$102.15	without charge	99.9999%
Block Storage High Speed	Block storage	10 GB – 12 TB	€0.0860$0.0998	€88.06$102.15	without charge	99.9999%
Block Storage Capacity	Block storage	100 GB – 128 TB	€0.0420$0.0487	€43.01$49.89	without charge	99.9999%
Shared File Storage	File storage	100 GB – 256 TB	€0.0518$0.0601	€53.04$61.53	without charge	99.9999%
Backup Vault	Backup Vault	100 GB – 9765.6 TB	€0.0110$0.0128	€11.26$13.07	without charge	99.999999999% (11 nines)
Storage Box	Storage Box	1 TB – 40 TB	Flat rate	from €2.82$3.27	without charge	Snapshots instead of durability commitment

Two S3 classes, one endpoint

Both classes speak the same API and reside in the same namespace. Switching between them is not a migration, but a lifecycle rule: a policy on the bucket that automatically moves objects to the other class after a specified period.

Object Storage Standard

Object Storage

S3-compatible object storage, retrieval and API calls free of charge.

Storage per GB/month

€0.0070$0.0081

€7.17$8.31 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 1 GB
Maximum capacity: 4882.8 TB
Durability (annual basis): 99.999999999% (11 nines)
Redundancy: 3 copies across 2 fire zones
API requests: without charge
Price factor compared to Cold Archive: 2.9-fach

Protocols

S3 API
Swift
HTTPS
rclone

Locations (4)

Frankfurt am Mainfra1
Frankfurt am Mainfra2
Berlinber1
Munichmuc1

Object Storage Performance

Object Storage

Pure NVMe backend for media delivery and training datasets.

Storage per GB/month

€0.0180$0.0209

€18.43$21.38 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 1 GB
Maximum capacity: 1953.1 TB
Durability (annual basis): 99.999999999% (11 nines)
Redundancy: 3 copies, NVMe, 2 fire zones
API requests: without charge
Price factor compared to Cold Archive: 7.5-fach

Protocols

S3 API
HTTPS
S3 Select

Locations (2)

Frankfurt am Mainfra1
Frankfurt am Mainfra2

Consistency model

Every PUT is immediately readable, including overwriting an existing key. LIST operations are strongly consistent within a region.

Cross-region replication is asynchronous; the typical delay is under 30 seconds for objects under 100 MB.

Read-after-write consistency, without delay

Limits per bucket

No upper limit for the number of objects per bucket. An account can create up to 1,000 buckets, and names are unique per region.

Keys can be 1,024 bytes long, metadata per object 2 KB. Prefixes are automatically partitioned, a hash prefix is not necessary.

5 TB per object · 10,000 parts per upload

Throughput and latency

The standard class delivers up to 350 MB/s per connection, the performance class up to 1.4 GB/s. Parallel connections scale almost linearly up to the instance's uplink limit.

The performance class is relevant for datasets with many small objects: it keeps metadata entirely on NVMe.

Standard: 42 ms · Performance: 9 ms (p50, first byte)

What does it cost per month?

Enter capacity and egress, and the bill appears alongside — broken down by storage, egress and requests. The break-even between archive and standard is derived from the catalogue prices, not estimated.

Input

Used capacity

Average used storage in the billing month.

Egress to the internet

Only outbound traffic outside the ENTRONYX network is billed.

API requests per month

GET, PUT, LIST and HEAD combined, in millions. Only the performance class charges for requests.

million

Capacity in GB: 20,480
Egress in GB: 2,048
Request: 5,000,000

Monthly invoice comparison

All amounts net

Itemised monthly costs per storage class with 20 TB capacity and 2 TB egress
Class	Storage	Egress	Request	Total / month	Δ Standard
Object Storage Standard€0.0070$0.0081/GB · 20 TB billed	€143.36$165.89	—	—	€143.36$165.89	Reference
Object Storage Performance€0.0180$0.0209/GB · 20 TB billed	€368.64$428.03	—	—	€368.64$428.03	+€225.28$262.14
Cold Archivecheapest€0.0024$0.0028/GB · 20 TB billed	€49.15$57.34	€20.48$23.76	—	€69.63$81.10	−€73.73$84.79
Backup Vault€0.0110$0.0128/GB · 20 TB billed	€225.28$262.14	—	—	€225.28$262.14	+€81.92$96.26

Object Storage Standard€143.36$165.89
Object Storage Performance€368.64$428.03
Cold Archive€69.63$81.10
Backup Vault€225.28$262.14

Break-even archive vs standard

Cold Archive remains cheaper as long as monthly egress stays below 9,2 TB — this corresponds to 0.46 times the used capacity. Above this, the advantage flips because archive egress costs €0.0100$0.0116 instead of €0.0000$0.0000 per GB.

Annual total of the cheapest class

€835.58$973.21

Cold Archive · €994.34$1,158.12 incl. 19 % VAT. Compared to Object Storage Standard, this is a difference of €884.74$1,017.45 per year.

Cold Archive bills a minimum storage period of 90 days; objects deleted earlier are billed until the 90th day. First bytes after retrieval request typically after 3 to 5 hours.
Egress between ENTRONYX regions and to instances in the same location is free of charge in all classes. Only traffic leaving the network is billed.

Volumes attached to the instance

Network block storage, replicated three times within the location. To the instance, a volume is an ordinary drive. It can be enlarged while in use and moved between instances in the same region.

Block Storage NVMe

Block storage

Network block storage with up to 30,000 IOPS per volume.

Storage per GB/month

€0.0860$0.0998

€88.06$102.15 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 10 GB
Maximum capacity: 64 TB
Durability (annual basis): 99.9999%
Redundancy: 3-way replicated in the location
API requests: without charge
Price factor compared to Cold Archive: 35.8-fach

Protocols

iSCSI
NVMe-oF
CSI driver

Locations (4)

Frankfurt am Mainfra1
Frankfurt am Mainfra2
Berlinber1
Munichmuc1

Block Storage High Speed

Block storage

Fixed performance cap of 3,000 IOPS, independent of volume size.

Storage per GB/month

€0.0860$0.0998

€88.06$102.15 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 10 GB
Maximum capacity: 12 TB
Durability (annual basis): 99.9999%
Redundancy: 3-way replicated in the location
API requests: without charge
Price factor compared to Cold Archive: 35.8-fach

Protocols

iSCSI
NVMe-oF
CSI driver

Locations (4)

Frankfurt am Mainfra1
Frankfurt am Mainfra2
Berlinber1
Munichmuc1

Block Storage Capacity

Block storage

Affordable block storage for volumes that need space instead of IOPS.

Storage per GB/month

€0.0420$0.0487

€43.01$49.89 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 100 GB
Maximum capacity: 128 TB
Durability (annual basis): 99.9999%
Redundancy: 3-way replicated in the location
API requests: without charge
Price factor compared to Cold Archive: 17.5-fach

Protocols

iSCSI
CSI driver

Locations (3)

Frankfurt am Mainfra1
Frankfurt am Mainfra2
Berlinber1

Performance profile of block storage classes. IOPS are input and output operations per second; they scale at 3 operations per GB, minimum 100, capped at the class maximum. Latency p99: 99 out of 100 accesses are faster than the stated value.
Class	IOPS (4 K, random)	Throughput	Latency p99	Typical use
Block Storage NVMe	up to 30,000	1,200 MB/s	0.4 ms	Databases, container volumes, build caches
Block Storage Capacity	up to 500	180 MB/s	6 ms	Media libraries, log sinks, secondary copies

Connection

Volumes are connected via a separate storage network and do not consume the instance's uplink bandwidth. The Kubernetes CSI driver supports volume expansion and snapshots according to the specification.

iSCSI, NVMe-oF and CSI drivers

Snapshots

Snapshots are incremental and block-based. The first snapshot corresponds to the used capacity, each subsequent one only to the changed blocks.

Recovery creates a new volume, the original remains untouched.

Stored in Object Storage at €0.0070$0.0081 per GB

Limits

A volume always belongs to exactly one instance. Simultaneous access by multiple instances requires file storage or a cluster file system.

Increasing size is possible online, decreasing is not — a new volume is created for this.

16 volumes per instance · 64 TB per NVMe volume

Retention obligation instead of availability

Two tape copies at separate locations, managed by robots. Intended for data that must be kept for ten years and is usually never read.

WriteWriteIngestion via the S3 endpointObjects initially land on an NVMe buffer and are considered stored once the PUT is confirmed. The transfer to tape takes place in 40 GB blocks, usually within four hours.
StorageStorageMinimum storage period of 90 daysObjects deleted earlier will continue to be billed until the 90th day. For data with a shorter lifecycle, the standard class is cheaper, even though its per-GB price is higher.
ReviewReviewIntegrity check every 180 daysEach cartridge is read cyclically and compared against the stored checksum. In the event of a discrepancy, it is rewritten from the second copy and the medium is retired.
RetrievalRetrievalRestore in three to five hoursA RestoreObject call makes the object available in the standard class for a selectable number of days. Only then is a GET possible. Mass retrievals over 50 TB are scheduled with operations.

Cold Archive

One share, many instances

NFS 4.1 and SMB 3.1.1 on the same share, operated as a managed service. Intended for shared upload directories, media libraries and applications that expect a standard file system with paths, permissions and locks (POSIX) instead of an API.

The difference to a self-managed NAS is the operations: replication, drive replacement, kernel maintenance and snapshot schedules are handled by us. You define capacity, export rules and quotas — everything else is no longer a process that reaches you.

Concurrent mounts: up to 2,000 clients per share
Simultaneous protocols: NFS 4.1 and SMB 3.1.1 on the same path
Throughput per share: up to 1.0 GB/s
IOPS per share: up to 12,000
Capacity: 100 GB to 256 TB
Maximum file size: 16 TB
Snapshots: 24 hourly, 14 daily, included
Access control: POSIX-ACL, NTFS-ACL, Kerberos
Redundancy: 3-way replicated, snapshots included
Encryption: AES-256 at rest, TLS in transit

Shared File Storage

File storage

NFS and SMB shares, usable simultaneously by many instances.

Storage per GB/month

€0.0518$0.0601

€53.04$61.53 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 100 GB
Maximum capacity: 256 TB
Durability (annual basis): 99.9999%
Redundancy: 3-way replicated, snapshots included
API requests: without charge
Price factor compared to Cold Archive: 21.6-fach

Protocols

NFS 4.1
SMB 3.1.1
CSI driver

Locations (3)

Frankfurt am Mainfra1
Frankfurt am Mainfra2
Munichmuc1

Size classes

There are no package tiers: the monthly price is the used capacity times €0.0518$0.0601 per gigabyte. The following sizes are therefore reference points, not plans — throughput and IOPS are capped per share and do not grow with capacity.

Size classes of file storage. The monthly price is the capacity in gigabytes times the catalogue price per gigabyte, net.
Capacity	Gigabyte	Price / month	Typical use
100 GB	100	€5.18$6.01	Smallest bookable share — configurations, shared scripts
1 TB	1,024	€53.04$61.53	Upload directory of an application behind multiple web nodes
5 TB	5,120	€265.22$307.65	Media library of a content management system
20 TB	20,480	€1,060.86$1,230.60	Shared workspace for rendering or build nodes
64 TB	65,536	€3,394.76$3,937.93	Image archive, measurement data storage, raw scientific data
256 TB	262,144	€13,579.06$15,751.71	Largest share per location — beyond that, multiple shares

How it differs from block storage and Storage Box

All three classes store files. They differ in a single question: who is allowed to write concurrently — and who manages the locks.

File storage, block storage and Storage Box in comparison — access, protocols, billing and limits
Feature	Shared File Storage	Block Storage NVMe	Storage Box
Concurrent access	many instances on the same directory tree	exactly one instance per volume	many sessions, but no shared lock management
Protocols	NFS 4.1, SMB 3.1.1, CSI driver	iSCSI, NVMe-oF, CSI drivers	SFTP, Rsync, SMB/CIFS, WebDAV, S3 via gateway
Accessible from	private network (vRack), no public access	separate storage network of the instance	the internet, with separate access credentials
Billing	per used gigabyte and month	per used gigabyte and month	Flat rate per package, regardless of usage
Comparative price per TB	€53.04$61.53	€88.06$102.15	from €1.92$2.22 per TB in the largest package
Snapshots	24 hourly, 14 daily, included	incremental to Object Storage, billed separately	10 to 30 per package, included
Not intended for	Database files and anything requiring sub-millisecond latency	shared access by multiple instances	production application data with constant write access

Mounting

The share is only accessible from the private network. The export is restricted to IP ranges, public access is not intended.

Mount without reboot, also via vRack

Locks

Lock management is handled by the service, not your application. If two nodes write to the same file, the server decides — not the order of the packets.

NFSv4 leases, SMB oplocks

Quotas

With a soft limit, a notification is sent; with a hard limit, the write operation fails with the error ENOSPC (“no space left”).

Quota per subdirectory, hard or soft

Kubernetes

The CSI driver provisions the share as a ReadWriteMany volume — the access mode that a block volume cannot offer by design.

CSI driver, ReadWriteMany

Storage that even you cannot delete

Geo-redundant across two regions, with Object Lock in compliance mode — a write lock per object version that rejects any overwriting and deletion until the retention period ends. A compromised access key can therefore neither overwrite nor remove backups.

Compliance mode

The retention period is set upon writing and can only be extended. Until it expires, the object is immutable — regardless of permissions, roles or support requests.

Cannot be lifted, not even by the account holder

Governance mode

For test runs and retention rules that should remain reversible. The removal of the lock is logged and kept as a separate entry in the audit log.

Can be lifted with special permission

Retention: 1 day to 10 years
Legal hold: indefinite, regardless of the retention period
Versioning: mandatorily active
Secondary region: freely selectable from 3 locations
Tested backup tools: Restic, Veeam, Borg, Duplicati
Egress: without charge

Backup Vault

Backup

Immutable storage with WORM lock and ransomware protection.

Storage per GB/month

€0.0110$0.0128

€11.26$13.07 per TB/month

Egress per GB

€0.0000$0.0000

Outbound traffic free of charge

Minimum capacity: 100 GB
Maximum capacity: 9765.6 TB
Durability (annual basis): 99.999999999% (11 nines)
Redundancy: Geo-redundant across 2 regions
API requests: without charge
Price factor compared to Cold Archive: 4.6-fach

Protocols

S3 Object Lock
Restic
Veeam
Borg

Locations (3)

Frankfurt am Mainfra1
Frankfurt am Mainfra2
Munichmuc1

Flat-rate storage without API

Fixed sizes at a fixed price, accessible via classic transfer protocols. Designed for backups, offloading and everything that doesn't need to speak S3.

Sizes, prices and limits of the Storage Box packages. The “Effective per TB” column converts the package price to one terabyte and makes the tiers comparable.
Package	Capacity	Price / month	Effective per TB	Subaccounts	Snapshots
Storage Box 1 TB	1 TB	€2.82$3.27	€2.82$3.27	100	10
Storage Box 5 TB	5 TB	€12.80$14.85	€2.56$2.97	100	20
Storage Box 10 TB	10 TB	€21.21$24.60	€2.12$2.46	100	30
Storage Box 20 TB	20 TB	€39.80$46.17	€1.99$2.31	100	40
Storage Box 40 TB	40 TB	€76.69$88.96	€1.92$2.22	100	50

Supported protocols

SFTP
SCP
FTPS
HTTPS
Rsync
Rclone
BorgBackup
Restic
SMB/CIFS
WebDAV
S3 (Gateway)

Each subaccount receives its own directory, its own access credentials and optionally its own quota. S3 access runs via a gateway and supports basic operations, but neither versioning nor Object Lock — the Backup Vault is intended for this.

Billing

The price is independent of usage. Traffic is unlimited and is not charged as long as the box is not used as a delivery target for public downloads.

Switching between packages is possible at any time, data is retained.

Monthly, no setup fee

What the API can do — and what it can't

The object storage is verified against the test suite of the official S3 SDK. In practice, the following four areas determine whether an existing tool will work without modification.

S3 compatibility

Supported are bucket policies, ACLs, presigned URLs, CORS configuration, versioning, server-side encryption with managed and customer-provided keys (SSE-S3, SSE-C), event notifications to webhooks, and S3 Select in the performance class.

Not supported: S3 Batch Operations, Requester Pays, Intelligent Tiering, and Transfer Acceleration. If you need these features, you should remove them from the tool before migrating.

Endpoint per region: s3.<region>.entronyx.cloud — for example s3.fra1.entronyx.cloud

Signature Version 4 · Path and virtual host style

Object Lock and WORM

WORM — Write Once, Read Many — means: once written, it cannot be changed until the deadline. Object Lock sets a retention date for each object version. As long as this is in the future, the storage rejects DELETE and PUT on the same version — with HTTP 403, regardless of the caller's permissions.

The prerequisite is a bucket with versioning enabled; Object Lock cannot be turned on retrospectively. A Legal Hold acts additionally and indefinitely until it is explicitly removed.

For the retention obligation according to GoBD and the tax code, compliance mode with a term of ten years is the usual configuration.

S3 Object Lock, compliance and governance mode

Lifecycle rules

Rules move objects between classes, delete expired versions, and clean up aborted multipart uploads. Evaluation happens once a day; the class change is transparent for applications, the key remains the same.

A rule consists of a filter (such as a key prefix) and one or more actions with deadlines. The example below the four cards shows what this looks like in practice.

Up to 1,000 rules per bucket, daily evaluation

Multipart upload

Large objects are uploaded in parts, which can be transferred in parallel and in any order. Aborted transfers can be resumed at the last confirmed part number.

Incomplete uploads take up storage and are billed until they are completed or aborted. Therefore, every bucket configuration should include a rule with AbortIncompleteMultipartUpload — in the example below after seven days.

From an object size of about 100 MB, parallel upload is measurably faster; below that, the administrative overhead of the part operations outweighs the benefits.

5 MB to 5 GB per part · 10,000 parts · 5 TB per object

Example of a lifecycle rule

Three actions in one rule: objects under the prefix logs/ move to the Cold Archive after 90 days, outdated versions are deleted after 30 days, aborted multipart uploads are cleaned up after 7 days.

{   "Rules": [     {       "ID": "logs-nach-90-tagen-ins-archiv",       "Filter": { "Prefix": "logs/" },       "Status": "Enabled",       "Transitions": [         { "Days": 90, "StorageClass": "COLD_ARCHIVE" }       ],       "NoncurrentVersionExpiration": { "NoncurrentDays": 30 },       "AbortIncompleteMultipartUpload": { "DaysAfterInitiation": 7 }     }   ] }

Checksum per part: SHA-256; in addition to MD5 (ETag)
Encryption at rest: AES-256; always active, at no extra cost
Rules per bucket: 1,000; Lifecycle and replication
Buckets per account: 1,000; Increase on request

Which class is available where

Not every storage class is available at every location. Tape archive and backup vault require separate infrastructure and are therefore available at selected locations.

Availability of storage classes per location
Storage class	fra1Frankfurt am Main	fra2Frankfurt am Main	ber1Berlin	muc1Munich	hel1Helsinki
Object Storage Standard	available in Frankfurt am Main	available in Frankfurt am Main	available in Berlin	available in Munich	not available in Helsinki
Object Storage Performance	available in Frankfurt am Main	available in Frankfurt am Main	not available in Berlin	not available in Munich	not available in Helsinki
Cold Archive	available in Frankfurt am Main	not available in Frankfurt am Main	not available in Berlin	not available in Munich	not available in Helsinki
Block Storage NVMe	available in Frankfurt am Main	available in Frankfurt am Main	available in Berlin	available in Munich	not available in Helsinki
Block Storage High Speed	available in Frankfurt am Main	available in Frankfurt am Main	available in Berlin	available in Munich	not available in Helsinki
Block Storage Capacity	available in Frankfurt am Main	available in Frankfurt am Main	available in Berlin	not available in Munich	not available in Helsinki
Shared File Storage	available in Frankfurt am Main	available in Frankfurt am Main	not available in Berlin	available in Munich	not available in Helsinki
Backup Vault	available in Frankfurt am Main	available in Frankfurt am Main	not available in Berlin	available in Munich	not available in Helsinki

availablenot offeredThe allocation of locations can be found under Data centres.

Bucket, volume, share or vault in a few minutes

The configurator guides you through class, location, capacity and retention and shows the monthly invoice before ordering. Billed hourly pro rata based on the bytes used — with no minimum term and no setup fee.

Configure storage Full price overview

Storage classes: 8
from: €0.0024$0.0028 / GB
Egress in the network: €0.0000$0.0000
Durability: 11 nines

Storage billed byusage

Eight classes, three questions

First the basic type, then the class

Object Storage

Block storage

Archive

All classes compared

Two S3 classes, one endpoint

Consistency model

Limits per bucket

Throughput and latency

What does it cost per month?

Input

Monthly invoice comparison

Volumes attached to the instance

Connection

Snapshots

Limits

Retention obligation instead of availability

One share, many instances

Size classes

How it differs from block storage and Storage Box

Mounting

Locks

Quotas

Kubernetes

Storage that even you cannot delete

Compliance mode

Governance mode

Flat-rate storage without API

Supported protocols

Billing

What the API can do — and what it can't

S3 compatibility

Object Lock and WORM

Lifecycle rules

Multipart upload

Which class is available where

Bucket, volume, share or vault in a few minutes

Storage billed by
usage