OceanLaunch docs

Build, ship and run your apps

Domains and data

Databases

Managed PostgreSQL, MariaDB (MySQL-compatible) and Redis next to your apps. OceanLaunch runs them, backs up the SQL ones every night, and gives your app the connection details.

Create a database

  1. Open your workspace and choose Databases in the sidebar.
  2. Enter a name, for example orders-db, choose the kind (PostgreSQL 17 or MariaDB 11.4), and choose Create database.
  3. It shows Starting for up to two minutes, then Running.

Each database has 256 MB of memory and a quarter of a CPU. How many you can have depends on your plan, PostgreSQL and MariaDB together: see Plans and limits. Only owners and admins of the workspace can create and delete databases.

Who can reach it

A database runs on your workspace's own private network, next to your workspace's apps. It has no address on the internet: only your workspace's apps can connect to it. Apps in other workspaces can't reach it either.

The database page shows the connection details: host, port 5432, database app, user app and a JDBC URL. The password is shown only to owners and admins, behind a Show button.

What the app user can do

The user app owns the database app. It can create and change tables, schemas, views, functions and indexes, and add PostgreSQL's trusted extensions such as pgcrypto, uuid-ossp, citext, hstore and pg_trgm (CREATE EXTENSION pgcrypto;). Migration tools such as Flyway and Liquibase work as usual.

It isn't a superuser, so it can't run programs or read files on the server, change server settings, or create other users. Extensions that need a superuser can't be added. A dump that adds one, or gives objects to another user, won't import: make it with --no-owner, as shown under Import your data.

Connect it to an app

  1. On the database page, under Connected apps, choose your app and Connect.
  2. Redeploy the app, so its next version starts with the new settings.

Connecting adds these variables to the app (replacing any it had with the same names):

VariableValue
SPRING_DATASOURCE_URLjdbc:postgresql://<host>:5432/app
SPRING_DATASOURCE_USERNAMEapp
SPRING_DATASOURCE_PASSWORDthe password (kept as a secret)
DATABASE_URLpostgresql://app:<password>@<host>:5432/app (a secret)

A Spring Boot app reads the first three by itself: add the PostgreSQL driver to your build and nothing else.

<!-- pom.xml -->
<dependency>
    <groupId>org.postgresql</groupId>
    <artifactId>postgresql</artifactId>
    <scope>runtime</scope>
</dependency>

Other frameworks can read DATABASE_URL. Any member of the workspace can connect and disconnect apps; disconnecting removes these variables again.

A database can't be connected to a static site.

Disk space

Each database may hold your plan's size of data: Free 1 GB, Starter 5 GB, Pro 15 GB, Team 40 GB. The Disk section of the database page shows how much it uses. At 90% the workspace's owners and admins get an email; once it's full the database refuses new data (apps get errors on writes) until you delete some or move to a bigger plan. Backups don't count towards it.

Backups

Every database is backed up every night around midnight (server time), and the last 7 backups are kept. The Backups section of the database page lists them, with when each was taken and its size. Owners and admins can also:

pg_restore --no-owner --dbname=postgresql://localhost/mydb orders-db-20261026-1158.dump

Restore a backup

  1. In the Backups list, choose Restore… next to the backup you want.
  2. Type the database's name to confirm, and choose Restore.

OceanLaunch first takes a backup of the current data, so you can undo the restore by restoring that one. Only when it has succeeded does the restore start; if it fails, nothing is changed. The page shows progress and refreshes by itself until it's done. Apps using the database may see errors while it runs.

Restoring puts back the tables that were in the backup, with their saved contents. Tables created after the backup are kept as they are.

Import your data

Moving an existing database to OceanLaunch? Make a dump of it, then upload it on the database page under Import your data (owners and admins, up to 150 MB):

# pg_dump's own format (recommended)
pg_dump --no-owner -Fc -d postgresql://user@oldhost/mydb -f mydb.dump

# or plain SQL
pg_dump --no-owner -d postgresql://user@oldhost/mydb -f mydb.sql
  1. Choose the file: .dump or .tar from pg_dump, or .sql / .sql.gz.
  2. Leave Replace tables that are in the dump on to drop and recreate those tables (for pg_dump files); other tables are kept.
  3. Type the database's name to confirm, and choose Import.

As with a restore, a backup of the current data is taken first, the import starts only once that has succeeded, and the page shows progress. For safety, plain SQL that tries to run programs on the server (COPY … FROM PROGRAM) is refused.

Delete a database

At the bottom of the database page, type its name and choose Delete database. This deletes it with all its data and backups, and removes its variables from the apps it was connected to. It can't be undone, so download a backup first if you might need the data.

MariaDB (MySQL)

Choose MariaDB 11.4 for WordPress, PHP and other apps written for MySQL: MariaDB speaks MySQL's protocol and SQL, so they use it unchanged, with the MySQL driver or the MariaDB one. Everything above works the same, with these differences:

Browse data

Owners and admins can look inside a PostgreSQL or MariaDB database from the portal: open it and choose Browse data.

Redis

Choose Redis when you create a database for a cache, sessions or a job queue. It runs Valkey 8.1, the open-source Redis kept by the Linux Foundation: every Redis client and library works with it unchanged.