Databases

A database keeps the version it was made with, so nothing changes under you.

Connecting from your apps

Apps in the same environment reach a database by its name on the private network, for example postgres.internal. Use a reference so the address and password are filled in for you: DATABASE_URL=${{postgres.DATABASE_URL}}.

Connecting from your computer

Turn on public access in the database's Connect tab, then:

wattle db proxy postgres      # opens it on a local port, for GUI tools
wattle db connect postgres    # straight into psql, mysql or valkey-cli

The connection goes through an encrypted tunnel; no database port is open to the internet.

The data browser and console

Console lists tables and runs queries, without opening the database to the internet. It's read-only unless you choose Allow changes, and a query stops after 15 seconds.

Backups and restores

• PostgreSQL, MySQL and MariaDB are backed up continuously: restore to any second of the last 7 days. Valkey and ClickHouse restore to a full backup.
• Restore into a new database beside the original (the default), or in place, which backs up what's there first.
• Backups are copied off site, encrypted, every hour.

Moving data in and out

• Export now on the Backups tab makes a file to download: .dump.gz (PostgreSQL, for pg_restore), .sql.gz (MySQL and MariaDB), .rdb.gz (Valkey) or .tar.gz (ClickHouse).
• To bring data in, open the database with wattle db proxy and load it with the engine's own tool, such as pg_restore or mysql.

What your database account can't do

Your account owns your data but isn't a superuser: it can't run operating system commands, read the server's files, or change server-wide settings. That keeps every customer's database safe from the others.