Managed Applications
Install open-source services such as PostgreSQL, MySQL, MongoDB and Kafka into your own Kubernetes cluster from the portal, and build faster.
Build faster with managed, open-source databases
Familiar dev tools and an open ecosystem
Databases are installed by open-source operators and run as standard PostgreSQL, MySQL and MongoDB. Develop and manage them with the tools you know, without licence lock-in.
High availability by default
The standard PostgreSQL install comes with one primary and two hot standbys; if the primary fails, one of the standbys takes over automatically.
Maintenance from the portal for less operational toil
When a new version shows in the installed applications list, run a rolling upgrade with one button. If an update goes wrong, the same path takes you back to the previous version.
Keep your data in your own cluster
The database runs in your cluster; data never goes to a database service shared with other customers.
Example scenarios
A team adding PostgreSQL to its app
PostgreSQL is installed into the cluster from the portal with one primary and two hot standbys. If the primary goes down, a standby takes over on its own.
An e-commerce team handling order events
Kafka is installed from the same catalog with three nodes, and order events flow between services. ClickHouse is added beside it with two replicas for reporting.
A small team keeping its database up to date
When a new version shows up in the list of installed apps, a rolling upgrade starts with one button. If the update misbehaves, the same path takes it back to the old version.
Scale and reliability built in
Multi-primary MySQL
MySQL is installed as a three-node multi-primary cluster. If a node is lost, the others keep accepting writes and traffic is routed to healthy nodes.
Backup and restore
Take a backup of PostgreSQL, MySQL or MongoDB whenever you need one. In PostgreSQL, a restore creates a new instance from the backup and leaves the running database untouched.
Capacity check before install
The cluster's CPU, memory and disk, and the number of worker nodes needed for high availability, are checked before installing. If they fall short, you are told how many nodes to add, so no half-built install is left behind.
Messaging and analytics
Install Kafka for event streaming and ClickHouse for analytical queries from the same catalogue. Kafka comes with three nodes and ClickHouse with two replicas in the standard install.
Flexible sizing
Pick a ready-made size, then adjust CPU, memory, disk and instance count by hand when you need to. Replicas and disk size can be increased later.
Built-in security
No inbound connections
Install and update requests are pulled outwards by the operator in the cluster; no port is opened into the cluster from outside.
Images scanned daily
Database images are scanned for vulnerabilities every day, and the status of each version is shown in the portal.
Protected connection details
Passwords are stored encrypted in owner-only fields, and every time a password is revealed it is written to the audit log.
Flexible options for development and production workloads
A single-instance small size for dev/test and highly available medium and large sizes for production sit in the same catalogue. Pricing is set by quote.
Learn more to get started
Kubernetes
See how the clusters your databases run on are built.
VM and container platform
The capabilities of the platform the clusters run on.
For software companies
Software teams that use databases, clusters and a delivery path together.