VPS for a database
PostgreSQL, MySQL, ClickHouse or Redis under load
Why that many
For a database, memory is not headroom but a working tool: the more data fits in the cache, the fewer trips to disk. The rule to start from: the active part of the database should fit in memory. The second most important parameter is the disk, and not so much sequential read speed as random-access latency
disk from 40 GB
A database of up to a few gigabytes, a dozen concurrent connections
disk from 80 GB
PostgreSQL or MySQL under a medium-sized application
disk from 160 GB
Analytical queries, ClickHouse, hundreds of connections
- The I/O operations limit: NVMe in the description guarantees nothing if the plan caps IOPS
- The ability to grow the disk without reinstalling the server
- Snapshots and their frequency, a database is the last thing you can afford to lose
- A private network between servers, if the database will be separate from the application
Find a server for a database
Server matching
60 plans with a verified price, data checked August 6, 2026PostgreSQL, MySQL, ClickHouse or Redis under load
Some links are affiliate links: if you sign up we earn a commission at no extra cost to you. It does not affect the ranking, the matching formula is open
Suitable plans from the base
Selected are the ones that cover the recommended configuration: at least 4 cores and 8 GB of memory
| Provider | Plan | CPU | RAM | Disk | Price per GB | Verified | Price |
|---|---|---|---|---|---|---|---|
| AdminVPS | Start | 4 | 8 GB | 80 GB NVMe | $2 | August 6, 2026 | $16 |
| Hostman | Cloud 5 | 4 | 8 GB | 160 GB NVMe | $2 | August 3, 2026 | $17 |
| FirstVDS | Liftoff SSD | 4 | 8 GB | 80 GB SSD | $2 | August 6, 2026 | $20 |
| Timeweb Cloud | Cloud MSK 80 | 4 | 8 GB | 80 GB NVMe | $3 | August 3, 2026 | $22 |
| DataPacket | VServer 8 GB | 5 | 8 GB | 250 GB NVMe | $3 | August 6, 2026 | $25 |
| AdminVPS | Standard | 8 | 12 GB | 100 GB NVMe | $2 | August 6, 2026 | $27 |
| VDSina | Standard 4 × 8 GB | 4 | 8 GB | 150 GB NVMe | $4 | August 6, 2026 | $30 |
| is*hosting | Premium | 4 | 8 GB | 50 GB SSD | $4 | August 3, 2026 | $34 |
| Timeweb Cloud | Cloud MSK 100 | 8 | 12 GB | 100 GB NVMe | $3 | August 3, 2026 | $34 |
| DataPacket | VServer 16 GB | 6 | 16 GB | 300 GB NVMe | $2 | August 6, 2026 | $35 |
| Hostman | Cloud 6 | 8 | 16 GB | 320 GB NVMe | $2 | August 3, 2026 | $37 |
| Fornex | Cloud NVMe 8 | 4 | 8 GB | 120 GB NVMe | $5 | August 6, 2026 | $39 |
Who claims this workload
A Russian cloud with data centers in Moscow and St. Petersburg. Clear panel, hourly billing, snapshots and private networks. One o…
A budget VPS with a fast start and locations in Russia, Europe and Kazakhstan. One of the lowest entry points among Russian provid…
A managed cloud that deploys apps from your repository in a few clicks. A fit for teams without dedicated DevOps: updates, monitor…
Very broad geography: more than forty VPS locations plus a separate dedicated-server line. Handy when you need a specific host cou…
A local Emirati provider with a data center in Dubai. Best for projects with an audience in the UAE and the Gulf, where low latenc…
Focused on performance and dedicated servers for production. A choice for heavy workloads where stable capacity matters more than…
Managed NVMe hosting focused on site speed and WordPress. They take on part of the administration, which helps if you have no sysa…
A general-purpose mid-range provider with flexible configurations. A fit when you need a predictable server for typical workloads…
A provider with Russian-speaking support and European locations. A range from a simple VPS to dedicated servers.
An inexpensive provider with hourly billing and a clear plan line-up. Often chosen for small services and test stands.
A provider with many data centers and dedicated products for 1C, trading and GPU. Notable in the corporate segment.
One of the older Russian VDS providers, with a range from budget servers to GPU and storage.
A Russian provider with its own data center in Moscow and a flexible configurator: resources are assembled for the task rather tha…
Common questions about a database
How much memory does PostgreSQL need
A guideline: the size of the active part of the database plus headroom for connections and the operating system. For a four-gigabyte database it is reasonable to take eight gigabytes of memory. If the database is several times larger than memory, the disk becomes the bottleneck, and then it matters more to take NVMe without a hard operations cap
Keep the database with the application or separate
Together is simpler and cheaper while the server copes. Splitting them makes sense when the application’s peaks start taking memory from the database or when you need to scale them independently. Splitting across servers requires a private network, otherwise traffic goes over the public address