Object Storage

Object Storage stores data as objects in a flat namespace (buckets), where each object consists of the payload, freely definable metadata, and a unique identifier. Access is provided via a RESTful API (S3). Block Storage, on the other hand, provides data as blocks that are used like a local hard drive — ideal for databases and virtual machines. Object Storage is particularly suited for backups, media, archiving, and cloud-native applications.

Yes, our Object Storage offers full S3 API compatibility. Existing tools and SDKs such as AWS CLI, Boto3, s3cmd, rclone, and all common S3 libraries work without modification. You can use our Object Storage as a drop-in replacement for AWS S3 — or operate it as a sovereign alternative alongside your existing cloud solutions.

All objects are automatically encrypted server-side with SSE-S3 (Server-Side Encryption) — without you having to manage your own keys. Additionally, we support SSE-C (Customer-Provided Keys) if you want to retain full control over your encryption keys. Data is replicated across multiple nodes in our ISO 27001-certified data center in Munich.

We offer transparent, usage-based billing: you pay per TB of storage and per TB of outbound traffic. All prices are monthly, with no minimum contract term and no hidden costs for API calls. Optional features such as WORM or Multi-AZ replication are billed separately.

Yes, migration is straightforward thanks to full S3 API compatibility. With tools like rclone or s3cmd, you can transfer your buckets and objects directly. We support both path-style and virtual-hosted-style URLs. On request, we can personally assist you with the migration.

Yes. Once written, objects cannot be deleted or overwritten for a defined retention period — not even by administrators. This is the most effective protection against ransomware attacks on your backup infrastructure and meets compliance requirements for audit-proof archiving.

Your data is stored exclusively in our ISO 27001-certified data centers in Munich, Nuremberg, Frankfurt, Amsterdam, and Toronto — never in the USA. INGATE is an owner-managed German company — exclusively German law and GDPR apply. There is no data transfer to US corporations.

Egress costs are fees that cloud providers charge for outbound data traffic — that is, for data leaving the data center toward the internet or other networks. Every API response, every download, every video stream, and every backup replication generates egress traffic. Most hyperscalers charge these costs per GB, which can quickly become a significant and hard-to-predict cost factor. Especially with data-intensive applications, these fees add up rapidly.

No. At INGATE, outbound data traffic is already included in the price — no per-GB fees, no hidden surcharges. This makes your costs fully predictable and transparent. Especially with data-intensive applications such as CDN, streaming, large APIs, or backup replication, this results in a massive cost advantage over the major hyperscalers.

AWS charges approx. $0.09/GB (first 10 TB), Azure approx. $0.087/GB, and Google Cloud approx. $0.12/GB. A company transferring 10 TB per month pays approx. $900–1,200/month for outbound traffic alone. At 100 TB, that already rises to $8,000–9,000+/month. These costs are hard to predict as they depend on user behavior, API call volume, and traffic patterns — making TCO calculation difficult and often leading to unexpectedly high bills (so-called "bill shock"). At INGATE, traffic is included, making total costs fully predictable from day one.