A database that shares a server with no one
Deploy PostgreSQL, MySQL or ClickHouse on a dedicated NVMe instance in minutes: stable query speed, a private network with no public IP, backups on your schedule. The image — one click from the Marketplace.
Why a database needs its own server
The classic pains of a database on a shared or app-shared server — and how a dedicated instance removes them.
-
"The database and the app on one server"
A classic that ends badly: the backend eats CPU at peak, the database slows queries, everything falls together. A separate instance = independent resources and independent failure.
-
"Slow queries on shared hosting"
There your DB competes for disk with hundreds of other sites. A dedicated NVMe gives stable IOPS — response time is predictable.
-
"The database is exposed to the internet"
A public IP on port 5432/3306 is an invitation for scanners. With us the database lives in a private network, access — only to your instances via VPC.
-
"We'll set up backups later"
Scheduled disk images + dumps in Object Storage ($0.0013/GB) close this in 10 minutes, before the first outage, not after.
Choose your DBMS
Six ready images in the Solution Marketplace — each comes up on a dedicated NVMe instance in minutes.
| DBMS | For what | Recommended start |
|---|---|---|
| PostgreSQL | universal: apps, geodata, AI (pgvector) | ocp-3 (2 vCPU / 8 GB), ≈$20.45/mo |
| MySQL | sites, stores, CRM | ocp-3 (2 vCPU / 8 GB) |
| Redis | cache, sessions, queues | ocp-1 (1 vCPU / 2 GB), ≈$8.11/mo |
| MongoDB | flexible schemas, catalogs, IoT | ocp-3 (2 vCPU / 8 GB) |
| ClickHouse | analytics, events, billions of rows | ocp-5 (4 vCPU / 16 GB), ≈$40.90/mo |
| RabbitMQ | message queues between services | ocp-1 (1 vCPU / 2 GB) |
Another DBMS — MariaDB, OpenSearch, Kafka? Deploy on a clean instance with full root. All ready images — in the Solution Marketplace.
What matters for a database — and what you get
Stable speed, isolation from the internet and saved data — by default.
-
NVMe and dedicated vCPU
Writes don't depend on "neighbours" — stable IOPS and predictable response time.
-
RAM for the working set
Scales with no reinstall: started with 4 GB, grew — add memory in minutes.
-
Private network (VPC)
A database with no public IP, traffic to apps doesn't go to the internet and isn't billed.
-
Backups + dumps in Object Storage
Scheduled disk images + logical dumps in another location — the 3-2-1 rule.
-
A snapshot before a schema migration
Roll back in minutes if an ALTER goes wrong.
-
Monitoring nearby
Zabbix or Grafana + Prometheus from the Marketplace on a neighbouring instance.
-
Replication
With the DBMS's standard tools between instances in a VPC: PostgreSQL streaming replication, MySQL source-replica.
Don't want to administer it yourself?
Setup, config tuning, backups, monitoring and updates of your DBMS can be handled by our team — the "Basic administration" service. You work with the app, we watch over the database.
Frequently asked questions
Delegate administration to usA database on your own NVMe instance — in 5 minutes
Pick an image, configuration and location. Billing is hourly — a test costs nothing.
Latest publications
Everything you need to create a stable, secure and scalable environment
Cloud on-call handover checklist for reliable 24/7 support: prevent context gaps and speed up issue resolution
A practical cloud on-call handover checklist to keep support continuity, avoid missed alerts, and resolve incidents faster across shifts.
Cloud change freeze and rollback plan for safer production releases: reduce outage risk during critical updates
A practical change freeze and rollback framework to protect production stability, keep customer services available, and recover fast if an update fails.
Cloud maintenance window planning playbook for stable service updates: reduce disruption and keep customers productive
A practical cloud maintenance window playbook to plan updates safely, reduce disruption risk, and keep customer operations predictable.
Cloud instance disaster recovery testing playbook: prove restore readiness before real outages
A practical cloud disaster recovery testing playbook to validate restore readiness, reduce recovery risk, and keep customer services available during critical disruptions.
Cloud incident response runbook for faster service recovery: reduce downtime and protect customer experience
A practical cloud incident response runbook to reduce downtime, speed up service recovery, and keep customer operations stable during disruptions.
Cloud instance capacity planning calendar for predictable growth: keep services fast during peak demand
A practical monthly capacity planning calendar for cloud instance workloads to keep response times stable during peak demand and control infrastructure spending.
Cloud instance rightsizing and cost control playbook: keep performance stable while reducing monthly spend
A practical cloud instance rightsizing playbook to reduce monthly infrastructure spend while maintaining stable service performance.
OpenStack + Kubernetes multi-region failover checklist for stable client services
Practical multi-region failover checklist for OpenStack and Kubernetes to keep client-facing services stable during outages.
OpenStack + Kubernetes multi-region failover checklist for stable client services
Practical multi-region failover checklist for OpenStack and Kubernetes to keep client-facing services stable during outages.
Cloud instance monitoring and alerting baseline: prevent silent failures before they impact customers
A practical monitoring and alerting baseline for cloud instances to detect failures earlier, reduce downtime, and protect customer experience.