Provisioning a Database
Creating a database in Miabi takes a few choices and a click. Miabi handles the container, credentials, and networking for you.
Creating a database
From Databases → New database:
- Name — a human-friendly label, unique within the workspace.
- Engine — PostgreSQL, MySQL, MariaDB, Redis, MongoDB, or libSQL. See the overview for what each is good for.
- Version — choose the engine version. You can perform an in-place version upgrade later.
- Resource sizing — set CPU and memory limits, and the size of the persistent volume that stores the data.
Click Create, and Miabi pulls the image, starts the container on the workspace's internal network, and provisions credentials.
Resource sizing
| Setting | What it controls |
|---|---|
| CPU | CPU limit for the container. |
| Memory | RAM limit; the engine is tuned within this budget. |
| Disk / volume | Persistent storage for the data directory. |
Start modest. CPU and memory can be adjusted later, and you can grow the volume as your data does — so there's no need to over-provision on day one.
What gets generated
After provisioning, Miabi creates and stores (encrypted at rest):
- A database / default user as appropriate for the engine.
- A generated password and a ready-to-use connection string.
- An entry in the workspace's secret vault so apps can consume the credentials.
See Access & credentials for how apps connect, and port forwarding for temporary access from your own machine.
The database is reachable on the internal network only — no port is published on the host. This is intentional; expose it temporarily via port forwarding when you need direct access.
Provisioning is available to Owners, Admins, and Developers. Viewers see the database list but cannot create one.