FEATURES / DATABASES

The data layer, on the same machines as the app.

Six engines, provisioned and managed on servers you own. No separate data vendor, no per-gigabyte line on an invoice, and no question about which country the rows are sitting in.

SIX ENGINES

Pick the one you actually need.

Each has its own page with the version provisioned and how it is managed.

WHAT THEY SHARE

The parts that are the same whichever engine you run.

Each engine gets a server role

Database, cache and search are distinct roles rather than packages installed beside the app. Provisioning one configures the service, the firewall and private-network access in a single pass — and gives it its own machine sizing, so a memory-hungry search index cannot squeeze the application.

Reachable from your app, closed to everything else

Servers talk over the private network, and firewall rules are managed per server. The usual shape is a database port open to the app subnet and shut to the internet.

Config files you can edit

postgresql.conf and its equivalents are edited from the dashboard, and the service restarts on save. Tuning does not require finding the file over SSH first.

Monitored like every other server

CPU, memory and disk are tracked with alert thresholds you set. This is usually how you learn that a table has outgrown the machine, rather than from a customer.

POSTGRESQL

Replication and pooling, from the dashboard.

PostgreSQL is the engine Depfloy manages most deeply. Promote a second server to a replica and the replication slot is configured for you, with lag reported in both bytes and seconds. PgBouncer is installed from the same screen when connections outgrow the server.

Replication and PgBouncer is available on the Business plan. Compare plans →

acme-db-1 primary
acme-db-2 replica lag 128 KB · 0.4s
PgBouncerport 6432 · transaction pooling
FAQ

Data layer questions

Should the database share a server with the app? +
For a small project it is fine. Once traffic is real, a separate database server is the shape that keeps a memory spike in one from taking the other down — and Depfloy provisions both from the same console.
Which engines can be backed up? +
All six, plus your project files: PostgreSQL, MySQL, Redis, Valkey, ClickHouse and Meilisearch. Every engine Depfloy provisions is an engine it can back up and restore.
Is PostgreSQL replication available on every plan? +
The engine is provisioned on any plan. Scheduled backups need Pro; streaming replication, PgBouncer and server monitoring are on the Business plan.
Does my data ever reach Depfloy? +
No. The engines run on servers you own and backups stream from your server to your destination. Depfloy holds the configuration, not the contents.

Provision one in a few minutes.

7 days free, no credit card. Connect a server and pick an engine.