Managed PostgreSQL, Redis and ClickHouse
Add a database next to your application in one action. Each instance runs in a container of its own with memory and CPU you set, gets a private address on your own network, and comes with backups, metrics, logs and a console from the first minute.
PostgreSQL 15
High availability availableThe default choice for an application database.
- Your own database, user and generated password, created with the instance
- Tune the server settings that matter: memory, connections, work_mem, WAL and autovacuum
- A live standby on a second server with automatic failover, as an add-on
- Scheduled backups, plus restores checked by reading the dump back before it is trusted
Redis 7
High availability availableCache, queues, sessions and rate limiting.
- Password set on creation, so it is never open to the network unauthenticated
- Choose the standard server, or the Stack build for JSON, search, Bloom and time series
- Set the eviction policy, memory ceiling and persistence to suit cache or queue use
- A live standby on a second server with automatic failover, as an add-on
ClickHouse 25.8
Analytics over events, logs and product usage.
- Both interfaces are wired up: the native protocol on 9000 and HTTP on 8123
- Query limits are yours to set: memory, threads, execution time and result size
- Runs on the long-term-support line, so the version under you does not move every quarter
- Starts at 512 MB of memory, which is the floor at which it behaves like a database
Private by default
Created and connected in the same step
Choose the site an instance belongs to and leave the private network option on. If that site does not have a network yet, one is provisioned; if it does, the instance joins it. Either way the database comes up with a private address rather than a public one, and there is no second task to remember.
Your own subnet
One private network per customer, on a /24 that is yours alone. Peers you create are the only things on it.
The connection string is offered to you
Add DATABASE_URL, REDIS_URL or a ClickHouse variable to your app and the dashboard offers the private string for that instance, ready to insert.
Your laptop can join
Add a WireGuard peer, import the config, and local tools like psql, TablePlus or redis-cli reach the private address directly.
No public port, ever
There is nothing to allow-list and no password standing between the open internet and your data, because the internet has no route to it.
Private networking is included on Pro, Studio and Agency, from £59/mo. How it works
Managed means managed
The running of it, not only the starting of it
A database is easy to launch and tedious to keep. These are in the dashboard from the moment the instance comes up.
Backups on a schedule
Set a schedule per instance, or take one on demand. Restores are verified by reading the dump back before anything is trusted, and you can download an archive whenever you want a copy of your own.
A standby that takes over
A live copy of a PostgreSQL or Redis instance on a second server, with automatic failover if the primary dies. Your connection string does not change. £7.50/mo per database.
Resize without rebuilding
Change the memory and CPU allocated to an instance from the dashboard. Start small while you are still finding the shape of the thing, and grow it when the workload does.
See what it is doing
Live statistics and metrics per instance: memory in use, connections, query activity and disk. Enough to tell a slow query from a small server.
A console when you need one
Run SQL against PostgreSQL or ClickHouse, or commands against Redis, from the dashboard. Useful for the migration you only run once.
Logs
Read the server log from the dashboard, live or as a snapshot, without arranging shell access to the machine underneath.
Every hosted site also gets its own MySQL-compatible database as standard, which is what WordPress and most PHP applications expect. Managed instances sit alongside it for the workloads that want a different engine. How backups and restores work, or read how to deploy an app your AI agent built for choosing between the three engines in context
Managed database FAQ
Engines, plans, private access and what you can tune.
Which database engines can I run?
PostgreSQL 15, Redis 7 and ClickHouse 25.8. Each instance runs in its own container with memory and CPU you choose, separate from your site's container. Every hosted site also gets its own MySQL-compatible database as standard, which is what WordPress and most PHP applications use.
Is the database reachable from the internet?
Not when you attach it to a site with a private network. It gets a private address on your own subnet, your application connects to it there, and no database port is opened publicly. Your own machine can join the same network with a WireGuard peer config.
How do I get the connection string into my app?
The dashboard offers it when you add the matching environment variable. Type DATABASE_URL, REDIS_URL or one of the ClickHouse variables on an app with an attached instance and the private connection string is offered for you to insert, so it never has to be copied by hand.
Which plans include managed databases?
Managed PostgreSQL, Redis and ClickHouse instances are available from Business at £24/month. Attaching one to a private network needs a plan that includes private networking, which is Pro, Studio and Agency, from £59/month.
Can I tune the server configuration?
Yes, and the settings that matter are in the dashboard rather than a support ticket. PostgreSQL exposes memory, connection and autovacuum settings; Redis exposes eviction, memory ceiling and persistence; ClickHouse exposes the query limits: memory, threads, execution time and result size.
What does Redis Stack add?
The Stack build adds the JSON, search, Bloom filter and time series modules on top of the standard server. Choose it at creation time if your application uses them; otherwise the standard build is the smaller, simpler option.
Why does ClickHouse need more memory than the others?
A single insert allocates a block buffer, and the merge threads, mark cache and query pipeline all draw on the same budget. Below 512 MB it restarts under the first serious query rather than answering it, so 512 MB is the floor we allow rather than letting you provision something that cannot work.
Are managed database backups separate from site backups?
Yes. A managed instance has its own backup schedule, its own retention and its own restore history, because it has its own lifecycle. Your site backups continue to cover the site container and the database that ships with it.