Loading docs
Skip to main content

Create a Database

Go to Data → Databases → Create database.

Start with a small managed database. You can verify the routing and tighten access controls once the service is online.

Step 1 — Database engine

Choose the engine that fits your workload. Versions and sizes are selected separately.

EngineBest forTags
PostgresAPIs, dashboards, SaaS backends, jobs, and anything that wants SQL with structureSQL + transactions, Independent versions, Good default for most apps
RedisQueues, cache, sessions, rate limits, realtime counters, and coordination locksLow-latency cache, Great beside your app, Persistent storage
MySQLLaravel, WordPress-style apps, internal tools, and services already built around MySQLFamiliar SQL, Broad app support, Independent versions

Step 2 — Version

Pick the database build. This maps to a backend image but stays separate from size.

Available versions are shown per engine (e.g. Postgres 16).

Step 3 — Size

Choose compute, memory, and storage. Version is selected separately.

PlanPriceCPUMemoryStorage
PlaygroundFree1 CPU256 MB1 GB
Seed$1.15/mo1 CPU512 MB5 GB
Sprout$2.70/mo1 CPU1 GB10 GB
Bloom$4.60/mo1 CPU2 GB20 GB

Step 4 — Zone

Choose where the database runs. New databases default to olas-closet. Your database will be provisioned in the selected zone with the resources included in the plan.

Step 5 — Service basics

FieldDetails
Database nameA name for the instance, e.g. main-db
Public connection endpointChecked by default — creates a connection URL for clients outside the cluster

Service summary

The right panel updates as you configure:

FieldExample
ServicePostgres 16
Namemain-db
SizePlayground
Resources1 CPU · 256 MB · 1 GB
Zoneolas-closet
EndpointPublic database URL

What you get:

  • A database instance sized by the selected plan
  • Dedicated storage for database files and runtime state
  • A connection endpoint your apps can use when provisioning completes

Click Create database.