Platform / Kubernetes

We'll move your app to Kubernetes without guesswork

For companies currently on a VPS or docker-compose who want to move to Kubernetes deliberately: with an inventory, a migration plan and a cutover window — not trial and error in production.

Plan the migrationPricing from 1 490 zł

For whom

Companies on VPS/docker-compose
Teams with no prior K8s experience
Apps outgrowing a single server
Software houses migrating client projects

What you get

Inventory of the current infrastructure
Migration plan with a maintenance window
Manifests and a Helm chart for the app
Database and storage migration
Preprod tests before cutover
A rollback plan

Packages and pricing

Prices net per month, starting proposals

Dedicated K8s Dev
1 node — test/preprod/dev
od 1 490 zł
Ask about a package
Dedicated K8s Starter
1 node — small production
od 2 490 zł
Ask about a package
Dedicated K8s HA Light
2 nodes + witness/quorum
od 4 490 zł
Ask about a package
Recommended
Dedicated K8s Business HA
3 nodes — production
od 7 990 zł
Ask about a package
Dedicated K8s Enterprise
3+ nodes, node pools, DR
od 15 000 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

Kubernetes needs constant care
Ingress, storage, RBAC and upgrades are work that doesn't end after go-live.
Security and isolation
Network policies, limits and updates keep the cluster in check.
Updates with rollback
We raise versions in maintenance windows, not in a panic.
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

Do we need to rewrite the app?
Usually not — we containerize the existing app and adapt the manifests, without rewriting code.
How long does a docker-compose migration take?
Depends on scale — from a few days for a simple app to a few weeks for a complex system.

On a VPS or docker-compose and thinking about Kubernetes?

Describe your current infrastructure. We'll prepare a migration plan with a maintenance window and rollback.

Plan the migration