Database VPS — from €5.49/mo
Run your database under full control — a server for PostgreSQL, MySQL and MongoDB, with a 5-hour test period, completely risk-free
Launch a database now
A database VPS is a virtual server with full root access where the DBMS lives apart from the application. Size the server by the working set of your data: it should fit in RAM. A 10 GB database runs comfortably on 16 GB RAM (Power 1, €17.99/mo), a 20 GB database on 24 GB (Power 3, €27.99/mo); the line-up starts at 4 GB for €5.49/mo, enough for development. You install Linux and the exact version of PostgreSQL, MySQL, MariaDB or MongoDB yourself, and tune buffers and permissions. NVMe matters specifically for a DBMS: journals are written synchronously, so disk latency directly limits commit speed. A 5-hour test period before payment lets you load a dump and time your own queries. Other configurations are on the VPS hosting page.
Plans
VPS for a database
A developer database and a test environment fit on Standard 1 — 4 vCPU, 4 GB RAM and 50 GB NVMe for €5.49/mo. For production, size memory by the working set: 16 GB is Power 1 at €17.99/mo, 24 GB is Power 3 at €27.99/mo. 5-hour test period before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Any DBMS
Install the version of PostgreSQL, MySQL, MariaDB or MongoDB you need — the environment is set up entirely for your database.
Fast NVMe disks
NVMe drives speed up reads, writes, indexes and complex queries, while dedicated RAM keeps the cache warm under load.
Full control
Root access, fine-grained configuration, users and permissions, replication and regular backups — the server is entirely yours.
How to set up a database on a VPS
Choose a plan and an image
Estimate the working set of your data and take a plan with RAM headroom — from Standard 1 (4 GB) to Power 3 (24 GB) — then pick a Linux image: Ubuntu, Debian or another distribution.
Install the OS yourself
Through the panel you deploy the chosen OS on a KVM server yourself — so the configuration stays fully under your control.
Deploy and tune the database
Over SSH or the KVM console install the DBMS, create users and permissions, tune the buffers and connect your application.
A server sized for your DBMS
We will help you pick a plan for your data volume: how much RAM to give the database cache, how many vCPU, and how much NVMe space for tables and indexes.
We can also help set up secure remote access, read replicas and a dump schedule. The application usually lives on a separate machine — a VPS for a backend and API fits well; database setup and maintenance can be handed to us: database administration.
Get sizing adviceFrequently asked questions
Did not find your answer?
Write to us via the contact page form.
Any — PostgreSQL, MySQL, MariaDB, MongoDB and others. You install the exact version yourself on a server with root access.
A separate server isolates the DBMS from the application: stable RAM for the cache and NVMe disks with no competition for I/O.
The main rule: the working set must fit in RAM. A 10 GB database lives comfortably on a 16 GB server (Power 1, €17.99/mo); for 20 GB take 24 GB (Power 3, €27.99).
Yes, on a top-tier plan: Max 3 offers 40 vCPU, 64 GB RAM and 700 GB NVMe for €84.99/mo. When data no longer fits in memory, the disk becomes critical — NVMe is a must here.
A database constantly writes journals and reads pages from disk. NVMe has an order of magnitude lower latency than network or shared storage — both writes and recovery are faster.
Automatic backups are not included: you take a server snapshot yourself in the control panel in a couple of clicks, and schedule logical dumps with pg_dump or mysqldump via cron.
You do: choose an image and deploy the system through the panel or the KVM console. We never touch your software — the server is entirely yours.
Yes, with the standard DBMS tools between two of our servers. A replica on a separate machine also improves availability: for fault-tolerance requirements we build a distributed cluster across several data centres.