Operations lead at a company still on rented dedicated servers
Hardware is aging, the renewal quote arrived, and nobody remaining on staff knows how the machine was originally built.
Move to the cloud without a bad weekend
We plan, build and migrate cloud infrastructure on AWS, Azure and Google Cloud. For engineering teams running production systems that outgrew their current servers.
What arrives
- An architecture diagram of the target environment, with every service, network boundary and access route named
- Terraform code for the entire environment, committed to your own Git repository and reviewed with your team
- A migration runbook with the cutover steps, the timings, the owner of each step and the rollback point
- Backups running on a schedule, plus a restoration you watch us perform from start to finish
Who this is for
Three profiles. If none of them is recognisably you, this is probably the wrong page - and the line below is the one worth reading before you book anything.
Not a fit: If you want servers rented and handed over with nobody named to operate them, a hosting reseller suits you better.
CTO of a SaaS product with a rising cloud bill
Spending climbed faster than revenue, and nobody can identify which service or environment is responsible for it.
Founder whose application went live on 1 unmanaged virtual machine
Traffic doubled after launch, the server collapsed twice, and there is no backup you have ever tested.
What you get
- An architecture diagram of the target environment, with every service, network boundary and access route named
- Terraform code for the entire environment, committed to your own Git repository and reviewed with your team
- A migration runbook with the cutover steps, the timings, the owner of each step and the rollback point
- Backups running on a schedule, plus a restoration you watch us perform from start to finish
- IAM roles and network rules documented, with an owner named for each one and a date to review it
- A cost report that breaks spending down by environment and by service, sent to you each month
- 2 recorded handover sessions, so your own engineers can rebuild the whole environment without us
What we build it with
-
AWS
- Microsoft Azure
-
Google Cloud
-
Terraform
-
Kubernetes
-
Cloudflare
- Amazon RDS for PostgreSQL
- Ubuntu Linux
Chosen per project, not per fashion. If your team already runs something else and it works, we use that.
How the work runs
-
1
1 week
Inventory
We inventory every server, database, cron job, domain and certificate you operate today, then record what depends on what.
From you: Access to the current hosting accounts, plus 1 person who can answer questions about legacy systems.
-
2
1-2 weeks
Target design
We design the target environment, size it against your genuine traffic, and cost it in writing before anything gets built.
From you: Traffic numbers for a busy month and any regulation about where your data may live.
-
3
2-5 weeks
Parallel build
We build the new environment in Terraform while the old one keeps serving users, then copy the data across.
From you: A staging DNS record and written approval of the architecture diagram before we build.
-
4
1-2 days
Cutover
We migrate traffic in a window you choose, monitor the error rates, and keep the old environment warm.
From you: A named person on call during the window and an agreed trigger for rolling back.
-
5
1 week
Handover
We hand over the repository, the runbook and the dashboards, then walk your engineers through a complete restoration.
From you: 2 engineers available for the sessions and a decision on who owns the account.
How we work together
Fixed project
Scope and price agreed up front. Best when the outcome is known and the deadline is real.
Dedicated team
A named team for a quarter or more. Best when the roadmap will change and you want the context kept.
Staff augmentation
Engineers inside your process and your tools. Best when you have the lead and need the hands.
Invoiced in
- USD
- EUR
- GBP
- CHF
- SGD
- AUD
- CAD
- AED
- SAR
- QAR
- JPY
- INR
Paid by
Card, netbanking, wallet and UPI through Razorpay, which is what our checkout runs on, so anything it accepts we accept. Bank transfer, SEPA, Wise and Payoneer for invoices that prefer it.
NDA before the first call. Full IP assignment on delivery. Contracts under Indian, English or Delaware law.
Work like this
Case studies are being written up
Three are in legal review. We can walk you through the work on a call in the meantime, including the parts that did not go to plan.
What clients say on Google
Live from our Google Business listing - not retyped here.
Loading reviews from Google - read them on Google.
Questions we get asked
You do, from the first day. We build inside your own AWS, Azure or Google Cloud account and commit the Terraform to your Git repository. Our access is a named role you can revoke in a minute. Nothing runs on a Recilens account, so nothing is hostage to the relationship.
We roll back to the old environment, which stays running until you sign off. The plan names the trigger for rolling back and the person who calls it. Data written during the migration window is replayed rather than lost. You then get a written account of what failed and the fix.
Most migrations we run take 6 to 12 weeks from inventory to handover. A single application with 1 database can finish in 3. What stretches it is legacy code with hard-coded paths, licences tied to a machine, and data that must remain in 1 country. We size that during inventory.
Usually yes, once idle resources are switched off and instances are sized against genuine traffic. We will not promise a number before we have seen your account, and we do not quote a percentage. You receive a cost report per environment and per service, so the next decision is yours.
Yes, as a monthly retainer with an agreed response time, or not at all. Plenty of teams take the runbook and run it themselves, which is exactly why the handover includes a live restoration. If you want us on call, we agree the hours, the escalation path and what counts as an incident.
Planning a migration this year?
List what you operate today and roughly what traffic it takes, and we will come back with a target design.