Discovery and assessment
An inventory of every server, database, scheduled job, and hidden dependency, with a plan for each one.
Cloud migration
Move off the server in the corner without losing a weekend to downtime.
Overview
We audit what is actually running, map the dependencies nobody documented, then move workloads in stages so there is always a way back. Cost modelling comes before the migration, not after the first bill.
What you get
- AWS and Azure landing zones
- Staged cutover with rollback
- Cost baseline and monthly review
- Decommissioning plan for old hardware
What we offer
Cloud migration, in detail
Pick the parts you need. We scope them together, quote a fixed price, and build in two-week steps.
Cost modelling
What the cloud will cost per month, before you commit, with the options that lower it.
Landing zone setup
Accounts, networks, identity, backups, and security baselines on AWS or Azure, set up properly from the start.
Staged migration
Workloads moved one at a time, each with a tested rollback, usually outside your working hours.
Modernisation
Where it pays, moving to managed databases, containers, or serverless instead of copying old servers as they are.
Decommissioning
Old hardware retired safely, with data wiped and licences cancelled, so you stop paying twice.
Where it fits
Typical projects
- Moving an ERP and file server out of the office comms room
- Leaving a hosting provider that has become slow or expensive
- Consolidating several cloud accounts nobody fully understands
- Meeting a customer's security requirements for hosting
Technology
What we use
Well-supported tools with a long runway, chosen for the project rather than for novelty.
- AWS
- Azure
- Terraform
- Docker
- Kubernetes
- PostgreSQL
- Cloudflare
Where AI fits in
We use AI-assisted tools to read old configuration, scripts, and logs during discovery, which speeds up mapping undocumented systems. An engineer checks every finding before it goes into the plan.
How it works
From first call to production
Every engagement follows the same shape, so you always know what happens next and what you will see.
- 01 · Week 1
Scope
We sit with the people who will use the thing. You get a written scope, a fixed estimate, and an honest note about what we would cut first.
- 02 · Weeks 2 to 10
Build
Two-week iterations against a shared board. You see working software every fortnight, not a status deck.
- 03 · Launch week
Launch
Staged rollout, real monitoring, and a rehearsed way back. We stay on the call until the graphs go flat.
- 04 · Ongoing
Run
Patching, alerts, and a monthly review of cost and reliability. Leave with your code and your documentation whenever you want.
Questions
Frequently asked questions
Will there be downtime?
We plan for as little as possible, usually a short window outside working hours for each system, with a rehearsed rollback if anything goes wrong.
Is the cloud always cheaper?
No. For some steady workloads a well-run server is cheaper. We model the cost before migration and will tell you if moving does not make sense.
AWS or Azure?
Both are good. If you already use Microsoft 365 or Windows servers, Azure is often simpler. We recommend based on your systems and your team.
Related
More from Run
Have a project like this in mind?
Send a paragraph about what you need. An engineer replies within one working day, and you get a written scope with a fixed price within a week.