Dedicated KaaS lifecycle
Kubernetes uses a separate lifecycle for clusters, node pools, versions, networking, storage and access instead of the data-module flow.
Managed Kubernetes for customer workloads uses a separate cluster lifecycle, node pools, upgrades and protected access. Plans are published independently from data modules.
Kubernetes uses a separate lifecycle for clusters, node pools, versions, networking, storage and access instead of the data-module flow.
Plans and checkout will be published after the dedicated KaaS lifecycle and capacity gates are verified.
No customer cluster or kubeconfig is issued today. Sales will open only after the dedicated lifecycle, access model, capacity gates and recovery procedures pass verification.
Kubernetes will use a dedicated KaaS contract instead of the database, cache or object-storage provisioning flow. The panel will not store raw kubeconfig content, and sales remain blocked until isolation, credentials, upgrades, recovery and capacity are verified.
Run MySQL without operating database servers. Receive a protected endpoint, explicit limits and a service isolated from your application hosting.
Explore module DatabasePostgreSQLRun PostgreSQL as an isolated managed service with a protected endpoint, quota visibility and a customer panel for access and lifecycle operations.
Explore module CacheMemcachedUse a managed in-memory cache for fast, ephemeral data without maintaining cache servers or exposing their infrastructure to your application team.
Explore module CacheValkeyUse Valkey as a managed cache with a protected endpoint, explicit limits and an isolated, verified Single topology.
Explore module Object storageS3Store objects through an S3-compatible API while the platform manages gateways over durable Ceph and exposes only the protected service endpoint.
Explore module