Managed databases
Managed Databases
Eight engines from PostgreSQL to ClickHouse on our software-defined storage with fast fsync, backups and monitoring included.
What a managed database is
A managed database is a database server that we set up and run for you. You pick an engine and a size, and you get an address and a password for your application.
Running a database yourself means installing and tuning it first, then backups and updates for as long as it runs. Here setup and updates are on us.
Each database runs on a server of its own in your private network, with a configuration tuned for its size.
Why ours
We tested PostgreSQL here against DigitalOcean, Hetzner and AWS RDS, with every run published.
See the benchmarksFast storage under every commit
Databases sit on our software-defined storage, where an fsync takes about 150 µs on average. Heavy writes and large scans stay fast under load, and the same workload often fits a smaller plan than it would elsewhere.
One panel for every engine
PostgreSQL, Valkey, MySQL, OpenSearch, ClickHouse, VictoriaMetrics, VictoriaLogs and Qdrant. Each one gets the same panel and backups.
Easy recovery
Restore your database to the moment before data was deleted or a migration failed. If the region is unavailable, restore from an off-site backup.
More room as you grow
Start on a small plan and move up when traffic grows. Your data stays where it is.
Bring your existing database
Paste your current database’s connection string or upload a dump. We copy the data over, then you connect your app to the new database.
Engines
PostgreSQLRelationalThe usual choice for an application database. Extensions are switched on from the panel.v18
ValkeyKey-value, in memoryFast caching and key-value storage. Works with Redis clients.v9
MySQLRelationalFor WordPress, Laravel and other software written for MySQL.v8.4
OpenSearchSearchFull-text search over your documents with the Elasticsearch style REST API.v3
ClickHouseAnalytics, columnarAnalytical queries over billions of rows in seconds, over the native protocol or HTTPS.v26.8
VictoriaMetricsTime seriesStore and query metrics. Connect your Prometheus agents and Grafana.v1
VictoriaLogsLogsCollect, search, and analyze logs from your services.v1
QdrantVector searchStores embeddings and finds the nearest ones, for semantic search and RAG.v1Backups and recovery
PostgreSQL and MySQL keep a recovery history. You pick a window of 3, 7, 14 or 30 days and can restore the database to any second inside it. A weekly copy can be kept for a month and a monthly one for up to a year.
The other engines take one backup a day. A restore brings the data back as it was at that backup.
Most engines also get off-site backups: daily dumps of your databases with copies at other providers. They are in the engine’s own format, so any server of the same engine loads them. You can make a dump by hand at any time and download it.
Looked after every day
Every database has its metrics and its log in the panel. For PostgreSQL, MySQL and ClickHouse the panel also shows what your applications ran, the heaviest queries first, and which tables and indexes cost the most.
We keep your database up to date. Updates install once a week in the maintenance window you pick, or right away when you ask. Maintenance like VACUUM, repack and ANALYZE runs from the panel, and you can watch it or cancel it.
The disk grows by itself before it fills up, by 20% when it is 80% full unless you set other values.
How to start
- Create a database in the Cloud Panel. Pick an engine, a size and the private network it lives in.
- Copy the connection string from the database page.
- Connect from your servers in the same network. To reach it from outside, turn on public access and allow your addresses in its security group.
Example usage
# PostgreSQL, from a server in the same network
psql "postgresql://dbadmin:<password>@orders.db.internal:5432/app"
# through PgBouncer, for many short connections
psql "postgresql://dbadmin:<password>@orders.db.internal:6432/app"Also in every PostgreSQL
Extensions
pgvector, TimescaleDB, pg_cron and others are switched on from the panel. CREATE EXTENSION works as the owner, from migrations too.
PgBouncer
A connection pooler on port 6432 in transaction mode, in every plan.
Write modes
Standard confirms a commit once it is on disk. Fast and Extreme give up some safety for speed, for caches and data you can load again.
Users and databases
Made from the panel, each user with read only, read and write or admin access.
Require SSL
Turn it on and connections without SSL are refused, from your networks too.
Read-only switch
New transactions can only read, and writes fail until you turn it off.
Questions
Do I need a network first?
Yes. A database lives in a private network behind a router, the same way your servers do.
Can I connect from outside my network?
Yes. Turn on public access and the database gets a port on the public address of your router and a name in db.serverscamp.com. Its security group decides who gets through.
How do I move my database here?
Paste the connection string of your current database or upload a dump, up to 20 GB. The data is copied into the new database.
What happens when the disk fills up?
It grows before that. By default the disk grows by 20% when it is 80% full. A disk never shrinks.
Can I move to a bigger size later?
Yes, from the panel. Your data stays where it is, and the disk grows if the new size comes with more.
Can I use PostgreSQL extensions?
Yes. Switch them on from the panel, or run CREATE EXTENSION as the database owner, also from your migrations.