Every field on the database create form - engine (PostgreSQL or MySQL), shared vs dedicated size, storage, region, credentials, and seeding.
Database settings
The Database tile creates a managed PostgreSQL or MySQL database. Defaults are chosen so the visible decisions stay small - size, storage, region - and the rest is generated safely. What databases are and how they connect to apps is covered in Databases; this page explains each field on the create form.
Name#
The display name for the database across your dashboard. On dedicated instances it also seeds the suggested database name under Connection details - which stays editable.
Example: my-shop-db
Engine#
PostgreSQL or MySQL, both fully managed:
| Engine | Version | Default port |
|---|---|---|
| PostgreSQL | 15 | 5432 |
| MySQL | 8.0 | 3306 |
Pick whatever your framework's ORM expects - connection details come out in the right shape either way. See Connect an app.
Size#
The one decision with real consequences:
- Shared (the default) runs your database on a pooled instance. It's ready in seconds, and it's the cheapest tier - right for development, previews and small production apps. See The Shared tier.
- Dedicated sizes provision a private instance with reserved memory. Creation takes 10-20 minutes, and the instance is yours alone - right for production loads that need predictable performance.
The tiers and their prices are on Databases. If a size isn't offered, your plan doesn't include it.
Storage#
How much disk the database gets. It can be grown later without downtime, but never shrunk - start small.
| Tier | Storage choices |
|---|---|
| Shared | 1, 2, 5, or 10 GB (a usage quota on the pool) |
| Dedicated | 10, 20, 50, or 100 GB of reserved SSD (250 and 500 GB coming) |
Example: 10 GB
Region#
The data centre the database runs in. Keep it in the same region as the app that talks to it - every query crosses that distance.
Shared databases are offered in the regions the pool runs in (Belgium, europe-west1, today); if your selected region isn't one of them, the form says so and moves it. Dedicated instances are offered in every platform region.
Connection details#
Collapsed by default because every field has a safe generated value:
- Database name - the initial database on the instance; what goes in your connection string. On the shared tier the name is generated opaque on purpose: co-tenants of a pooled instance can list database names, so yours must reveal nothing. Read it from the Credentials tab once ready. Example (dedicated):
shop_production - Admin user - the instance's admin account:
postgresfor PostgreSQL,rootfor MySQL, unless you set another name (dedicated only). - Password - at least 12 characters, no spaces, quotes or backslashes. Left blank, a strong password is generated - read it any time from the Credentials tab.
Seed from dump#
Shared tier only: pick a .sql or .sql.gz file and it's imported the moment the database is ready - the same format the Backup tab exports, so moving a database in is one create. If the import fails, the empty database survives and the import can be retried from its Backup tab.
Dedicated instances take 10-20 minutes to provision, so their imports live on the Backup tab instead of the create form. See Backups.
Example: backup.sql.gz