Encrypt connections with TLS, control network exposure, limit actions by role and namespace, and sign in through your identity provider.
Technical reference: TLS · RBAC · OIDC · Load Balancer and NodePort Policies
XaasIO RDS · Managed Relational Database Service
Private Database as a Service, Made Simple
Give teams self-service PostgreSQL, MySQL, MariaDB and MongoDB with high availability, automated backups and recovery built in. Run the service in your data center, sovereign cloud or provider environment, while retaining control of your infrastructure, identity, data and operations.
Built on OpenEverest, a CNCF Sandbox project. Upstream-aligned. Customer-operated, co-managed or fully managed by XaasIO.
Databases, simplified
Everything Needed to Deliver Databases as a Service
Users select the database they need. XaasIO RDS coordinates provisioning, high availability, storage, backups and access behind the scenes.
Main components
Database Engines | Launch PostgreSQL, MySQL, MariaDB and MongoDB from approved versions and service profiles. Start with a single node for development or a highly available cluster for production. Technical reference: OpenEverest · Percona Operators · mariadb-operator |
Availability and Scaling | Run replicas with operator-managed failover. Add nodes, resize CPU and memory, and expand storage as workloads grow. Technical reference: Patroni · Galera · Replica Sets · Sharding |
Backup and Recovery | Schedule backups to S3-compatible object storage, restore in place or into a new database, and recover to a point in time on supported engines. Technical reference: pgBackRest · XtraBackup · mariadb-backup · Percona Backup for MongoDB |
Identity and Governance | Separate teams, customers, and environments using namespaces, roles, and policies. Integrate enterprise single sign-on and map identity provider groups to roles. Technical reference: RBAC · OIDC · Namespaces · TLS |
Use the same service through the:
Database engines
Four Engines. One Operating Model.
Every engine is provisioned, scaled, backed up and recovered the same way, so platform teams learn one service instead of four.
PostgreSQL
The default choice for new transactional applications, with a rich extension ecosystem and strong SQL standards support.
PgBouncer · connection pooling
Replicaread
Primaryread / write
Replicaread
Streaming replication with automatic failover managed by Patroni.
Topologies
Single node, or one primary with read replicas. Connection pooling through PgBouncer.
High availability
Streaming replication with automatic failover managed by Patroni.
Backup and recovery
Scheduled and on-demand backups to S3-compatible storage. Point-in-time recovery.
Technical reference
Percona Operator for PostgreSQL · Patroni · pgBackRest · PgBouncer
MySQL
For web, commerce and SaaS applications that depend on MySQL compatibility and need every node to hold the same data.
HAProxy · single endpoint
Node 1in sync
Node 2in sync
Node 3in sync
Synchronous replication across every node. The cluster stays available while a majority of nodes is healthy.
Topologies
Single node, or a multi-node Percona XtraDB Cluster behind HAProxy or ProxySQL.
High availability
Synchronous replication. The cluster stays available while a majority of nodes is healthy.
Backup and recovery
Scheduled and on-demand backups to S3-compatible storage. Point-in-time recovery.
Technical reference
Percona Operator for MySQL · Percona XtraDB Cluster · XtraBackup · HAProxy
MariaDB
PreviewFor applications built on MariaDB and teams standardizing on Galera clustering.
Primary and replica endpoints
Galera noderead / write
Galera noderead / write
Galera noderead / write
Galera synchronous cluster shown. Standalone and asynchronous primary and replica topologies are also available.
Topologies
Standalone, Galera synchronous cluster, or asynchronous primary and replica.
High availability
Galera quorum, or operator-managed promotion of a replica when the primary fails.
Backup and recovery
Scheduled and on-demand logical and physical backups, and restore. Point-in-time recovery follows the upstream provider roadmap.
Technical reference
mariadb-operator · Galera · mariadb-backup · mariadb-dump
Availability
MariaDB is delivered through the OpenEverest v2 provider architecture, which is an upstream developer preview. XaasIO offers it as a Technology Preview until the validated XaasIO release is announced.
MongoDB
For document data such as catalogs, content, profiles and event streams that benefit from a flexible schema.
mongos router · sharded clusters
Secondaryread
Primaryread / write
Secondaryread
Replica-set elections provide automatic failover.
Add shards to scale out horizontally.
Topologies
Replica set, or a sharded cluster with config servers and
mongos routers.
mongos routers.
High availability
Replica-set elections provide automatic failover.
Backup and recovery
Scheduled and on-demand backups to S3-compatible storage. Point-in-time recovery.
Technical reference
Percona Operator for MongoDB · Percona Server for
MongoDB · Percona Backup for MongoDB
MongoDB · Percona Backup for MongoDB
Good to know
MongoDB is a document database, not a relational one.
XaasIO RDS delivers it through the same console, policies and operating model as the relational engines.
XaasIO RDS delivers it through the same console, policies and operating model as the relational engines.
How it works
One Request. XaasIO RDS Coordinates Everything.
01
Choose
Select an engine, an approved version, a cluster size, and a storage option.
02
Validate
XaasIO RDS confirms identity, role permissions, namespace policies and available capacity.
03
Provision
Kubernetes operators create the database nodes, replication, storage volumes, TLS certificates and credentials.
04
Deliver
XaasIO RDS returns the connection endpoint and credentials, with the selected backup schedule and monitoring in place.
Users request a database. XaasIO RDS handles the infrastructure coordination.
Advanced capabilities
Production Database Operations, Presented as Simple Choices
High Availability by Design
Offer single-node, three-node and larger topologies as simple choices. Operators manage replication, failover and recovery for each engine.
Technical reference: Patroni · Galera · Replica Sets · Sharding
Backup, Restore and Point-in-Time Recovery
Schedule backups with retention, run them on demand, restore in place or into a new database, and recover to a point in time on supported engines.
Technical reference: pgBackRest · XtraBackup · Percona Backup for MongoDB · S3-Compatible Storage
Scaling and Performance Tuning
Add or remove nodes, resize CPU and memory, expand volumes, pause idle databases and tune engine parameters. Scheduling policies keep replicas on separate hosts or zones.
Technical reference: Horizontal and Vertical Scaling · Storage Expansion · Pod Scheduling Policies
Security and Access Control
Monitoring and Query Analytics
Send metrics and query analytics to Percona Monitoring and Management, or expose Prometheus-compatible metrics to your existing observability stack.
Technical reference: PMM · Prometheus · Query Analytics
Migration and Data Import
Create new databases from existing backups, and import external backups to move self-managed or cloud-hosted databases onto the service.
Technical reference: Data Importers · Restore to New Database
Advanced capabilities depend on the engine and on the validated Kubernetes, storage, and OpenEverest architecture selected for each deployment.
Production databases
Databases on Kubernetes Without the Integration Burden
XaasIO designs, deploys, validates and supports XaasIO RDS as one production service rather than an unsupported collection of operators, charts and scripts.
Validated Architecture
Kubernetes, operators, storage classes, backup targets, identity and monitoring are tested as a complete solution.
Controlled Lifecycle
Engine versions, operators and the control plane follow a documented release, patching and upgrade policy based on validated upstream releases.
Sovereign and Air-Gapped Ready
Operate with local image registries, identity, object storage, monitoring and controlled update procedures inside the approved security boundary.
Flexible Operating Model
Choose customer-operated, co-managed, fully managed or dedicated SRE Pod operations.
Built for enterprise private cloud, sovereign and regulated cloud, and cloud service provider or MSP environments.
Console included, platform optional
Start with Databases. Expand to a Full Cloud When You Need More.
The default XaasIO RDS edition includes the XaasIO Hyperscaler console for database self-service. To deliver Compute, AI Lake, and other XaasIO modules through the same console, add the XaasIO Hyperscaler Platform.
Included
Included with XaasIO RDS
- XaasIO Hyperscaler console for database services
- Database catalog for PostgreSQL, MySQL, MariaDB and MongoDB
- Self-service provisioning, scaling, backup and restore
- Projects, roles and single sign-on
- REST API and Kubernetes custom resources
Optional
Requires XaasIO Hyperscaler Platform
- Additional XaasIO modules in the same console
- Multi-service catalogs and tenant management
- FinOps, metering, billing and payments
Modules delivered through XaasIO Hyperscaler Platform
XaasIO Compute
OpenStack private cloud for virtual machines, networks and persistent storage.
XaasIO AI Lake
Governed data lake, lakehouse, enterprise context and knowledge foundation.
XaasIO AI Factory + HPC
Accelerated AI, scientific computing, engineering and High-Performance Computing workloads.
XaasIO AI Token Factory
Governed and metered AI inference delivered through standardized APIs.
Database Migration Support Packs
Separately scoped support for assessment, migration, cutover and managed operations – available for:
Amazon RDS and Amazon Aurora
Azure Database and Google Cloud SQL
MongoDB Atlas and self-managed MongoDB
Self-managed PostgreSQL, MySQL and MariaDB
Software supply chain assurance
Every supported XaasIO RDS release includes an upstream SBOM and XaasIO release SBOM, covering components, container images, dependencies, licenses, vulnerabilities, provenance, and signed artifacts. SPDX or CycloneDX outputs support SOC 2-aligned controls and audit evidence.
Upstream SBOM
XaasIO release SBOM
Components and container images
Licenses and vulnerabilities
Provenance and signed artifacts
SPDX or CycloneDX output
SOC 2-aligned audit evidence
Applications connect with standard database drivers
SPDX and CycloneDX outputs are available for every supported release
Frequently asked questions
What is XaasIO RDS?
XaasIO RDS is a managed database service for PostgreSQL, MySQL, MariaDB and MongoDB that runs on Kubernetes in your own data center, sovereign cloud or service provider environment. It provides self-service provisioning, high availability, backups and recovery through a console, a REST API and Kubernetes custom resources.
Which database engines does XaasIO RDS support?
XaasIO RDS supports PostgreSQL, MySQL, MariaDB and MongoDB. PostgreSQL, MySQL and MongoDB run on the stable OpenEverest release line. MariaDB is delivered through the OpenEverest v2 provider architecture and is offered as a Technology Preview until the validated XaasIO release is announced.
Is OpenEverest the default platform for XaasIO RDS?
Yes. XaasIO RDS is built on OpenEverest, an Apache 2.0 licensed CNCF Sandbox project for provisioning and managing databases on Kubernetes. XaasIO adds a validated architecture, lifecycle management, the XaasIO Hyperscaler console and support.
Is MongoDB a relational database?
No. MongoDB is a document database. XaasIO RDS delivers it alongside the relational engines so that teams manage both through the same console, policies and operating model.
Is XaasIO RDS an alternative to Amazon RDS?
XaasIO RDS provides a comparable self-service managed database experience on infrastructure you control. It is not API-compatible with Amazon RDS. Applications connect with standard PostgreSQL, MySQL, MariaDB and MongoDB drivers, and provider-specific features such as proprietary extensions or IAM database authentication are reviewed during migration planning.
Does XaasIO RDS support high availability and point-in-time recovery?
Yes. Production clusters run multiple nodes with operator-managed failover, and scheduled or on-demand backups are stored in S3-compatible object storage. Point-in-time recovery is available for PostgreSQL, MySQL and MongoDB. For MariaDB it follows the upstream provider roadmap.
Where does XaasIO RDS run?
XaasIO RDS runs on XaasIO Managed Kubernetes or on a validated Kubernetes platform in your data center, colocation facility or cloud account. Database volumes use your Kubernetes storage classes, such as Ceph, and backups use S3-compatible object storage.
Can XaasIO RDS operate in an air-gapped environment?
Yes. XaasIO RDS can be designed with local image registries, identity, object storage, monitoring and controlled update procedures for disconnected, sovereign and restricted environments.
Is the XaasIO Hyperscaler console included?
Yes. The default XaasIO RDS edition includes the XaasIO Hyperscaler console for database self-service. Extending the console to other XaasIO modules, such as XaasIO Compute or XaasIO AI Lake, requires the XaasIO Hyperscaler Platform.
Are other XaasIO modules required?
No. XaasIO RDS can operate independently. XaasIO Compute, XaasIO AI Lake, XaasIO AI Factory and the other XaasIO modules are optional and are delivered through the XaasIO Hyperscaler Platform.
Who operates the databases?
You choose the operating model. XaasIO RDS can be customer-operated, co-managed, fully managed by XaasIO or run by a dedicated SRE Pod.
PostgreSQL, MySQL, MariaDB, MongoDB, MongoDB Atlas, Percona, Kubernetes, OpenEverest, Amazon RDS, Amazon Aurora, Microsoft Azure and Google Cloud SQL are trademarks of their respective owners and are named for identification only. XaasIO is not affiliated with, endorsed by or sponsored by these organizations.
Build what the world depends on.
Planning a cloud for government, financial services, pharmaceuticals, healthcare, energy, transport, industry, service-provider operations, or private AI? Work with XaasIO to define the architecture, security boundary, and operating model your environment requires.