How databases work: connections and backups

Your database starts inside the Project’s private network. It’s only open to the outside when you open it, and it’s backed up on a schedule.

Path 1 stays entirely in the private network and never crosses the internet. Path 2 is closed until you turn on the public endpoint and add allowed IPs.

Step by step, following the numbers

Apps in the same Project connect with server-name.internal (PostgreSQL port 5432, MySQL/MariaDB 3306). If you link the database to a container, DATABASE_URL is set for you.
To connect from your computer or an outside system, turn on the public endpoint and add allowed IPs. Connections must always use TLS. If the IP list is empty, everything is refused.
Backups run on the schedule you set and keep the number of copies you choose. Make one yourself before important work, such as before changing table structure.
Click Restore on the backup you want in the Backups tab.

What we look after, and what you look after

We look after	You look after
The machine, the disk and installing the engine	Choosing a machine size and enough space for your data
Backups on the schedule you set	Setting a schedule and number of copies that suit your work, and backing up yourself before big jobs
Requiring TLS, and the firewall for outside connections	Adding only the IPs you need, and keeping passwords safe
The Studio and Import tools in the Console	Your tables, indexes and your app’s SQL

If your app runs in a Container in the same Project, you don’t need the public endpoint at all. It’s safer, and there’s no IP list to look after.

Still stuck? Let our team help

Open a ticket from the Console. Tell us the site or service, what you did and the message on screen. Our reply comes back in the same ticket, so everything stays in one place.

Open a ticket All guides