Managed modules without managing servers

Managed data services and Kubernetes in one SaaS catalog

Choose a supported data service or explore Kubernetes. Data modules use their verified checkout, while Kubernetes follows a separate cluster lifecycle and security contract.

Choose a moduleOpen customer panel
SaaS+
managed data services
managed Kubernetes
Choose a managed module

A dedicated page for every managed service

Compare verified data services and managed Kubernetes before choosing the right product.

DatabaseMySQL

Run MySQL without operating database servers. Receive a protected endpoint, explicit limits and a service isolated from your application hosting.

Explore module DatabasePostgreSQL

Run PostgreSQL as an isolated managed service with a protected endpoint, quota visibility and a customer panel for access and lifecycle operations.

Explore module CacheMemcached

Use a managed in-memory cache for fast, ephemeral data without maintaining cache servers or exposing their infrastructure to your application team.

Explore module CacheValkey

Use Valkey as a managed cache with a protected endpoint, explicit limits and an isolated, verified Single topology.

Explore module Object storageS3

Store objects through an S3-compatible API while the platform manages gateways over durable Ceph and exposes only the protected service endpoint.

Explore module Compute platformKubernetes

Managed Kubernetes for customer workloads uses a separate cluster lifecycle, node pools, upgrades and protected access. Plans are published independently from data modules.

Explore module
Independent managed services

Services with product-specific boundaries

MySQL / PostgreSQL

Single managed database instance with an isolated RWO Cinder volume.

Memcached / Valkey

Single managed cache instance with explicit prepaid quotas.

S3

Single stateless S3 gateway backed by external Ceph RGW.

Kubernetes

Managed Kubernetes uses a separate cluster lifecycle, node pools and protected access.

Prepaid and predictable

Available data-service plans

Every published data plan shows CPU, RAM, storage, bandwidth, transfer and operation limits before payment. Kubernetes plans use a separate catalog and checkout.

The catalog is being prepared

Modules are advertised here, but checkout stays disabled until an administrator publishes prices and the platform reports fresh capacity.

Secure by default

TLS, mandatory IP allowlist and one-time credentials

Every endpoint requires TLS where supported and a mandatory IP allowlist. Credentials are revealed only once.

  • Default-deny network policy
  • One-time secret reveal
  • Backups and controlled patching
  • Usage sampled every five minutes