Databases

We'll move your database without chaos or guesswork

PostgreSQL/MySQL/MariaDB/MongoDB migrations between providers, versions or engines — with consistency validation before and after cutover, and a rollback plan in case something goes wrong.

Plan the migrationPricing from 79 zł

For whom

Companies moving off cheap hosting
Migrations between engines (MySQL → MariaDB)
Upgrades to a newer database version
Consolidating multiple databases into one place

What you get

Schema and data inventory
Migration plan with a maintenance window
Replication and consistency validation
Preprod tests before cutover
A rollback plan
The first backup after migration

Packages and pricing

Prices net per month, starting proposals

DB Dev
1 vCPU / 1 GB / 10 GB · 24h
79 zł
Ask about a package
DB Starter
1 vCPU / 2 GB / 25 GB · 24h
149 zł
Ask about a package
Recommended
DB Business
2 vCPU / 4 GB / 75 GB · 24h
349 zł
Ask about a package
DB Pro
4 vCPU / 8 GB / 150 GB · 24h
799 zł
Ask about a package
Dedicated DB HA Light
2 nodes + witness/quorum
od 2 990 zł
Ask about a package
Dedicated DB HA Pro
3 nodes — critical production
od 5 990 zł
Ask about a package

For HA — a quote after a short assessment. Add-ons (1h backup, PITR, read replica, migration) are quoted clearly before deployment.

Why it's worth it

Why it's worth handing this to us

A production DB is more than data
Parameters, backup, replication and monitoring decide performance and safety.
Backup you can actually restore
24h/1h backup and restore tests, not an unchecked file.
Single → HA path
Start cheaper and scale to HA as risk grows.
In every package

The standard you don't pay extra for

Backup and restore
24h backup by default, 1h backup and PITR optional, restore on demand and recovery tests.
Monitoring and alerts
Metrics, logs and alerts matched to your risk — you know about an issue before a customer reports it.
Security and access
SSL/TLS, access restrictions, RBAC, hardening and private networks and VPN.
Deployments and updates
GitOps, Helm, CI/CD, maintenance windows and prepared rollback procedures.
Locations PL / FR / DE / USA
We pick the region for latency, cost and EU compliance.
Documentation and care
Environment description, runbook, emergency procedures and contact with a technical person.
Managed vs in-house

Why managed costs less than an in-house hire

A single in-house specialist rarely covers 24/7, backup, monitoring and SLA at once. Here's a realistic comparison.

Your own specialist (in-house)
One salary = one person
A senior admin/DevOps is a full employer cost of ~18–25k zł/mo — and it's still just one person.
Available 8–16
Working hours, holidays, sick leave and weekends. A night outage waits until morning.
Backup on their shoulders
Separate tooling and storage cost; restore tests often skipped.
No formal SLA
No one guarantees response time; knowledge sits in one head (bus factor).
Tools and training
Monitoring, licenses, certs and training add to the salary.
VITAL CLOUD Managed
A 24/7 team
Many people, on-call and procedures. Someone's there even when your admin sleeps.
SLA in writing
An agreed response time per package, not goodwill.
Backup in 3 locations
Copies in three places, with validation and deduplication, and restore tests.
Service monitoring included
Alerts before a customer reports it; automatic service recovery after a failure.
Auto-provisioning
We start services automatically and repeatably (GitOps/IaC).
What it really costs per month
ItemIn-houseVITAL CLOUD
Specialist1 FTE ~18–25k zł/mo (8–16, holidays)24/7 team included in the package
AvailabilityBusiness days, working hours24/7 per package
Backup+tools and storage, tests often skipped3 locations, validation, deduplication — included
MonitoringSeparate tools + configurationIncluded, with alerts and auto-restart
SLANone / informalFormal, in writing
Bus-factor riskKnowledge in one headProcedures, runbook, team
Entry costRecruitment + onboardingFrom a few hundred zł/mo
Illustrative comparison. Amounts depend on market and scale — but even one in-house senior rarely replaces a team, backup in 3 places, monitoring and an SLA at once.See how much you'd save

FAQ

Will there be downtime?
Usually minimal — most of the work happens before the cutover window, thanks to replication.
Do you migrate between different engines?
Yes, e.g. from MySQL to MariaDB or from a single instance to an HA cluster — with app-compatibility tests.

Need to move a database and worried about losing data?

Describe your current database and the migration goal. We'll prepare a plan with validation and rollback.

Plan the migration