Skip to content
Olimpia
Esc
↑↓navigate↵open⌘Jpreview
On this page

Postgres

Managed Postgres 18, ready in seconds, connected to your apps over the internal network, with backups in your own S3.

An Olimpia Postgres database is a full Postgres 18 instance with its own user and password. It is created in seconds, and your apps connect to it over the internal network without any TLS setup.

Create a database

Open Postgres

In the console, go to Postgres → Create database.

Choose a name

Use 3 to 63 characters: lowercase letters, numbers, and hyphens. The user and password are generated automatically.

Choose the image

Postgres 18 works for almost everything. Choose Postgres 18 + pgvector if you plan to store embeddings or run similarity searches. You can’t change the image later.

Connect it to your app

In the app, open Variables and add the database. Olimpia sets DATABASE_URL. Deploy to apply the change.

What’s included

  • Postgres 18, with the app database and the app user, which owns the database. If you created it with pgvector, it also includes the vector extension.
  • Internal connection for your apps and optional external access over TLS.
  • Data explorer to view tables and rows from the console.
  • Scheduled backups to an Olimpia bucket or to your own S3.
  • Logs and metrics: errors, slow queries, CPU, memory, connections, and transactions per second.
  • Disk billed by usage. You don’t pick a disk size: Olimpia measures what the database takes up every minute and bills per GB.

What you can and can’t do

The app user owns its database but is not a superuser:

You can You can’t
Create tables, indexes, views, functions, and schemas Use ALTER SYSTEM or change the server configuration
Use trusted extensions such as pgcrypto, citext, pg_trgm, unaccent, hstore, and others, plus vector on pgvector databases Install untrusted extensions
Run migrations with any ORM Create other superusers

Limits

Limit Value
Memory 8 GB per database.
CPU 4 vCPU per database.
Connections 20 at the same time with the app user.

If several apps share a database, split the connections across their pools: for example, a maximum of 8 in the API and 3 in a worker. Prices are in Pricing and billing.

Embeddings with pgvector

On a database created with Postgres 18 + pgvector, enable the extension once, either in one of your app’s migrations or by asking your agent to do it (query_postgres with write: true):

CREATE EXTENSION IF NOT EXISTS vector;
CREATE TABLE documentos (id bigserial PRIMARY KEY, texto text, embedding vector(1536));

On a database with the standard image, CREATE EXTENSION vector fails. Create a new database with pgvector and move your data to it.

With your ORM

DATABASE_URL works as is with Prisma, Drizzle, Knex, TypeORM, SQLAlchemy, Django, Ecto, sqlx, and any Postgres driver.

Delete a database

Use the database’s actions menu. This deletes the database and all its data, and it can’t be undone. The console asks you to type the name to confirm. Backups already in your S3 are not affected.

Was this page helpful?