Service · Software developmentSoftware development
Cloud migration: fewer platforms, fewer surprises on the bill
We move your applications, websites and DNS to where they make sense: off platforms you outgrew or overpay for, onto a server you control with Docker Compose, or into a managed cloud when that is the better fit. Each move starts with an inventory and a cost audit, runs with a rollback plan, and ends with DNS, SSL, backups and monitoring checked.
What we do for you
- An inventory of everything you run: apps, databases, domains, DNS zones, certificates, scheduled jobs, who has access
- A cost audit per project, with what can be stopped, merged or moved
- A target architecture in plain words, and the reasons for it
- Apps packaged as containers and run with Docker Compose, builds on GitHub Actions rather than on the production server
- DNS moved zone by zone with records reviewed first; SSL certificates issued and renewed automatically
- Migration in steps with the old platform kept as a fallback until the new one has proved itself
- Daily snapshots, health checks and monitoring on the new setup (see hosting and DevOps)
Who it is for
- Fits: companies with apps spread over several platforms and bills nobody fully understands
- Fits: teams whose serverless or managed platform costs grew faster than their traffic
- Fits: businesses moving domains and DNS to one provider before a relaunch
- Does not fit: large regulated estates with dedicated cloud teams and contractual hosting requirements
What we have moved
- More than 100 hosted projects consolidated onto our own server.
- Apps moved off Cloud Run and Vercel to Docker Compose.
- DNS moved from Route53 to Cloudflare.
- SSL renewal automated on 4 AWS servers.
- After an audit of 34 projects, our own Google Cloud spend was roughly halved. That is our own figure, on our own infrastructure; your savings depend on what you run, and we do not promise a number.
Managed platform or your own server?
There is no single right answer. Google describes Cloud Run as a fully managed platform for running containers that removes idle instances when traffic stops and can bill per request, which suits irregular traffic and teams that want nothing to manage. A small server running Docker Compose (a tool for defining and running multi-container applications from one YAML file) suits many always-on apps with steady traffic, at a fixed monthly cost. We compare both on your real usage and say which we would choose, and why.
How a migration runs
- Inventory and audit. What runs where, what it costs, who depends on it.
- Plan. Order of moves, a rollback for each, and the quiet hours to do them.
- Rehearsal. Each app runs on the new platform at a test address before any traffic moves.
- DNS. Records reviewed and copied before the switch. For a Cloudflare full setup, Cloudflare asks you to review your existing records and disable DNSSEC before changing nameservers at your registrar. We never switch nameservers without your explicit go-ahead.
- Certificates. Let's Encrypt, a free and automated certificate authority, issues certificates through the ACME protocol; we set renewal to run on its own.
- Switch and watch. Traffic moved, health checks watched, the old platform kept until you agree to close it.
What we need from you
- Access to your cloud accounts, registrar and DNS, or the people who hold them
- Your recent invoices from each platform
- Windows when a short interruption is acceptable, if one is needed
- Your decision on anything that is deleted: we never delete without it
Questions we get
Will there be downtime?
We plan for none and rehearse each move on a test address first. When a short interruption cannot be avoided (some database switches), we schedule it with you.
Are we locked into your server afterwards?
No. Everything runs in standard containers with configuration in a repository you own; it can be moved to any server or cloud.
Can you guarantee a lower bill?
No. We show the audit and the expected costs before moving anything, and you decide. Some moves save money, some buy simplicity or speed.
Do you delete the old projects?
Only with your explicit decision, after the new setup has run long enough to be trusted. Until then the old platform stays as a fallback.
Sources
- Google Cloud documentation: what is Cloud Run (checked 2026-10-06)
- Docker Docs: Docker Compose overview (checked 2026-10-06)
- Cloudflare Docs: full (primary) DNS setup (checked 2026-10-06)
- Let's Encrypt: how it works (checked 2026-10-06)