Choose the database engine
The API supports PostgreSQL, MySQL, Redis, Valkey, MongoDB, Kafka and OpenSearch. The creation flow shows the combinations available for the selected provider and region.
Managed Databases
Managed Databases are provider-operated clusters provisioned through Unbroker. Choose an available engine, version, region, plan, storage size and node count, then manage the cluster alongside your applications.
For applications that need a database with less host and cluster administration. Engine and plan availability varies by provider and region.
The API supports PostgreSQL, MySQL, Redis, Valkey, MongoDB, Kafka and OpenSearch. The creation flow shows the combinations available for the selected provider and region.
Unbroker exposes cluster state, connection details, resizing, users, logical databases and available provider metrics. The provider provisions and operates the database host.
You own schemas, indexes, queries, credentials, application migrations and recovery planning. Backup and recovery capabilities depend on the selected engine and plan.
Managed databases require Pro and generate usage charges based on the selected cluster configuration. Pro has a $25 monthly commitment and $25 of eligible usage credit per billing cycle. Prices are in USD, excluding applicable taxes. Check the selected engine, plan, storage and node count before provisioning.
See current prices and billing examples →No. An Apps database node runs a database image as a private application service. A managed database is a provider-operated cluster. They differ in scaling, metrics, user administration and backup options.
No universal recovery guarantee applies to every engine and plan. Confirm the selected provider's capabilities and define and test your recovery policy.
Use the cluster's connection details and the connectivity options documented for your setup. Keep credentials in application configuration, outside source control.
Use these guides for configuration details, supported options and operational limits.
Walk through a deployment with the CLI →