Single PostgreSQL pod
One managed PostgreSQL pod for workloads that do not need a multi-pod topology.
Run PostgreSQL as an isolated managed service with a protected endpoint, quota visibility and a customer panel for access and lifecycle operations.
One managed PostgreSQL pod for workloads that do not need a multi-pod topology.
Prices and limits appear only after a plan is published and the platform confirms fresh capacity.
Modules are advertised here, but checkout stays disabled until an administrator publishes prices and the platform reports fresh capacity.
PostgreSQL uses TLS by default and requires at least one IP or CIDR allowlist entry. Plaintext access needs an explicit warning acknowledgement; ACLs never grant access to platform schemas.
Run MySQL without operating database servers. Receive a protected endpoint, explicit limits and a service isolated from your application hosting.
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 Compute platformKubernetesManaged Kubernetes for customer workloads uses a separate cluster lifecycle, node pools, upgrades and protected access. Plans are published independently from data modules.
Explore module