Production data layouts for business-critical workloads

Database access

Your database lives on your cluster's private network

Your team owns the schema. Asergo runs the database server and keeps your cluster wired to it.

  • Dedicated database server
  • Up to 25 Gbps over PrivateLAN
  • No public endpoint, no VPC peering
Timescale
Cassandra

High availability (HA)

A second database, always current, ready to take over

What if a server dies?

Replicas keep your database serving+

Is my replica actually current?

Replicas stay in sync, in real time+

Do I have to handle the failover?

Automated failover with Asergo on call+

Object storage

Your files and backups live on your cluster's private network

You decide what to keep. Asergo runs the storage and the restore.

  • S3-compatible API
  • Standard, Backup, and Archive tiers
  • Private inter-datacenter replication

Common use cases

App files

Store every file your database shouldn't+

.pdf
.doc
.docx
.txt
.odt
.rtf
.md
.xls
.xlsx
.csv
.ods
.tsv
.ppt
.pptx
.odp
.jpg
.jpeg
.png
.gif
.bmp
.tiff
.svg
.webp
.heic
.ico
.raw
.mp3
.wav
.aac
.ogg
.flac
.m4a
.wma
.aiff
.amr
.mp4
.mov
.avi
.mkv
.flv
.webm
.wmv
.mpeg
.mpg
.m4v
.zip
.rar
.7z
.tar
.gz
.bz2
.xz
.iso
.tgz
.cab
.arj
.json
.xml
.yaml
.yml
.html
.js
.ts
.py
.java
.c
.cpp
.go
.rb
.sh
.php
.css
.scss
.rs
.swift
.db
.sqlite
.sql
.mdb
.accdb
.log
.bak
.ldif
.stl
.obj
.fbx
.dwg
.dxf
.step
.iges
.3ds
.blend
.epub
.mobi
.azw
.azw3
.fb2
.djvu
.ttf
.otf
.woff
.woff2
.eot
.exe
.msi
.app
.apk
.dmg
.bat
.sh
.bin
.jar
.img
.dmg
.vhd
.vmdk
.eml
.msg
.ost
.pst
.mat
.h5
.hdf5
.nc
.cdf
.grib
.fits
.ics
.psd
.ai
.indd
.sketch
.torrent

Backups

Restore from any night in your history+

2026-05-21 02:00
2026-05-20 02:00
2026-05-19 02:00
2026-05-18 02:00
2026-05-17 02:00
2026-05-16 02:00
2026-05-15 02:00
2026-05-14 02:00

Persistent storage

Your stateful pods get disk that stays attached across restarts

You define the workload. Asergo provides the disk and reattaches it whenever the pod moves.

  • Stable storage per workload instance
  • Kubernetes-managed persistent volumes
  • NVMe-backed worker-node storage

Cache and state

Memory-speed reads next to your application

You decide what to cache. Asergo runs Redis — in-cluster or on dedicated memory-heavy hardware.

  • In-cluster or dedicated Redis
  • Memory-heavy server options
  • Persistence and snapshots

What it costs

Every layer above, priced. Some lives inside your monthly cluster fee; some is billed per GiB you store. No per-request fees, no cross-zone surcharges — the rate you see is the rate you pay.

Database access

Dedicated server hardware, on PrivateLAN

Dedicated database server
From € 125 / month
PrivateLAN to your cluster
Included

Object storage

S3-compatible API, billed per GiB stored and egressed

Standard — for data your app reads live

€ 0.02 / GiB

Egress
€ 0.01 / GiB

Backup — for scheduled snapshots and disaster recovery

€ 0.015 / GiB

First 250 GiB
Included in core
Egress
€ 0.015 / GiB

Archive — for data kept but rarely touched

€ 0.01 / GiB

Egress
€ 0.04 / GiB
Minimum retention
180 days

Persistent storage

Kubernetes persistent volumes on NVMe drives inside your worker nodes

2 × 480 GB up to 2 × 3.84 TB per node
Included in node price
Larger drives on request
Up to 30 TB per drive

Cache

In-cluster Redis on your worker nodes

In-cluster Redis
Included in node price
Memory-heavy server options
Available on dedicated nodes

Plan your database and storage setup with Asergo