Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
🗄️

Managed databases (DBaaS)

Updated 2026-11-20
On this page

Managed databases (DBaaS)

This service is in beta — features and availability may change.

Managed databases let you create a ready-to-use database instance in a few clicks. Patrii Cloud provisions and runs the underlying server so you can focus on your data instead of installing, patching and tuning a database host.

Instead of launching an instance and installing a database engine by hand, you choose an engine, a version, a size and a disk, and Patrii provisions a managed instance for you. The compute and storage underneath are handled for you, and the console shows the connection details your application needs.

Managed databases are in beta. The available engines, versions and options may change as the service matures, so try it on non-critical workloads first and keep your own backups of anything important.

Because this service is in beta, treat it as a preview: validate it against your workload, and do not rely on it as the only copy of critical data yet.
Screenshot — The Databases list showing managed database instances with their engine, size and status
The Databases list showing managed database instances with their engine, size and status

Key concepts

Database instance — A managed server running one database engine, with its own compute, storage and connection endpoint.

Engine (datastore) — The database software the instance runs; the choices offered come from the console.

Version — The specific release of the chosen engine.

Size (flavor) — The CPU and memory allocated to the instance.

Storage size — The disk capacity for your data, set when you create the instance.

Before you start

  • Enough quota for the instance size and storage you choose.
  • A client or application that speaks the chosen engine's protocol.
  • Network access from your application to the instance's endpoint.

Step by step

  1. Open the create wizard

    Go to Databases and choose Create database.

    Screenshot — The Create database button on the Databases page
    The Create database button on the Databases page
  2. Pick an engine and version

    Choose a database engine and one of its available versions.

    Screenshot — The engine and version selection step
    The engine and version selection step
  3. Name it and choose a size
    • Give the instance a recognizable name.
    • Select an instance size for your workload.
    • Set the storage size for your data.
    • Optionally set an initial database name.
    Screenshot — The instance name, size and storage step
    The instance name, size and storage step
  4. Create and wait until available

    Review the summary and create. The instance provisions and moves to an available state after a short time.

    Screenshot — A database instance transitioning to the available state
    A database instance transitioning to the available state
  5. Connect your application

    Open the instance to read its connection details, then put the host, port and credentials into your application's configuration.

    Screenshot — The database detail page showing connection details
    The database detail page showing connection details

Examples

Connect with a generic client (illustrative)
# use the host, port and credentials from the console
HOST=<db-host-from-console>
PORT=<db-port-from-console>
# then connect with your engine's own client, e.g.
# <engine-client> --host $HOST --port $PORT -u <user> -p
Store the credentials as an app config value
DATABASE_URL=<engine>://<user>:<password>@<db-host-from-console>:<port>/<database>

Limits & specifications

What you can do with a managed database:

CapabilityWhat it does
CreateProvision a new managed database instance.
ListSee your instances with their engine, size and status.
View detailsRead connection details and instance information.
DeleteRemove an instance you no longer need.

Best practices

  • Keep your own backups of important data while the service is in beta.
  • Store connection credentials as secrets or environment variables, never in source control.
  • Restrict network access so only your application can reach the database endpoint.
  • Size storage with headroom for growth so you do not run out unexpectedly.
  • Test a version change on a throwaway instance before applying it to anything you depend on.

FAQ

Which database engines are available?
The create wizard lists the engines and versions currently offered. Because the service is in beta, the list can change over time, so check the wizard for what is available now.
Where do I find my connection details?
Open the instance from the Databases list; its detail page shows the host, port and the information your application needs to connect.
My application cannot reach the database.
Confirm the instance is in the available state and that your network and firewall rules allow traffic from your application to the instance's endpoint and port.
Is managed databases production-ready?
It is in beta. Options and behaviour may change, so validate it against your workload and keep independent backups of anything critical before relying on it.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us