Cloud consulting and migration
Cloud consulting that ends with someone running it.
Architecture, migration and platform work delivered as a scoped, fixed-price project, in Terraform in your account. Then one fixed monthly fee if you want it run around the clock.
- Sage AI
Wave 2 plan: 14 services, 3 databases, target VPC and IAM in Terraform. Plan and policy checks attached.
Approved by the lead engineer - Sage AI
Cutover rehearsal in staging: replication caught up, health checks green, 11 minutes end to end.
Recorded for the cutover window - Sage AI
Rollback path tested: traffic returned to the source in one change, data intact.
Approved by the platform lead - Iris AI
DNS weighted 10%, then 50%, then 100%. Error rate and p95 latency flat at each step.
Engineer watching the cutover - Summary
Wave 2 complete. Source environment kept for the parallel-running period. Wave 3 plan opened.
Posted to #migration
What we consult on
The work a cloud consultancy scopes, built by the people who will run it.
Every recommendation arrives as Terraform in your account, reviewed by a named engineer, with the agent that will keep it that way afterwards.
Cloud architecture and landing zones
Accounts, networks, IAM and environments designed to grow from MVP to Series B, written in Terraform from day one so nothing lives only in a console.
Sage AIMigration to AWS
From a data centre, from another cloud, or between accounts and regions. Planned in waves with a rehearsal, a rollback and a cutover window agreed for each.
Sage AIRe-platforming onto Kubernetes
Workloads moved onto EKS with node groups sized to real use, ingress, identity and secrets done properly, and the cluster state kept in code.
Sage AICost and commitment strategy
The target estate sized from measured usage rather than the old one copied across, and commitments bought only once the new floor is known.
Finly AISecurity baseline and compliance
Least-privilege IAM, encryption, logging and vulnerability management built into the target, with SOC 2, ISO 27001 and PCI DSS controls enforced on every deploy.
ClearRiskObservability design
Metrics, logs and traces designed for the new estate before cutover, so the first day on the new platform is watched as closely as the last day on the old one.
Iris AIHow a migration runs
Waves, rehearsals and a rollback for every one.
Nothing moves until the target is written down, and nothing is cut over until it has been rehearsed.
- Week 1
Review and scorecard
Read-only access. We inventory what runs, what it costs and what depends on what, and hand you a scorecard with the wave order we would propose.
- Weeks 2 to 3
Target architecture in Terraform
The landing zone, networks and IAM written as code, with a wave plan that names the cutover step and the rollback for every wave before any of it moves.
- Waves
Parallel running and rehearsals
Each wave is rehearsed in staging, then cut over with the source kept running alongside until you sign it off. No wave starts before the previous one is stable.
- Cutover
Handover
Either to your team, with Terraform, diagrams, runbooks and the cutover record in your repositories, or to the managed plan on day one.
Which clouds
AWS first, Azure and GCP through Sage.
AWS first
Most of our engagements are on AWS, which is where the deepest landing zone, EKS and commitment work is. The founder has built on AWS since 2012 and is an AWS Community Builder.
Azure and GCP through Sage
Sage writes Terraform for AWS, Azure and GCP from the same plain-English request, so a target on either cloud is planned, reviewed and applied the same way.
A mixed estate is normal
Many teams arrive with workloads in two clouds or a data centre and one cloud. The review inventories all of it and the wave plan decides what moves and what stays.
Consulting, hiring or DevLift
What changes when the consultancy also runs it.
| A consultancy | Hire in-house | DevLift | |
|---|---|---|---|
| Coverage | Engagement hours, then a handover document. | One engineer, business hours. Nobody when they are on holiday. | Agents around the clock. Engineers on call under an SLA. |
| Who does the work | Whoever is assigned this month. | The engineer, for as long as they stay. | Four agents carry the routine load. Senior engineers approve every change. |
| Price | Hourly or retainer, plus change orders. | $200K+ a year with benefits, tooling and recruiting. | A fixed price for the project. One fixed monthly fee to run it. |
| Time to value | Weeks, then scope negotiations. | Three to six months to hire and ramp. | Scorecard in week one. Managed plans live in four weeks. |
| Compliance | Usually a separate engagement. | Depends on the hire. | Enforced on every deploy, evidence exported continuously. |
| When you leave | Depends on the contract. | Knowledge leaves with them. | Everything is in your account and your Terraform. |
Pricing
A fixed price for the project. One fixed fee to run it.
The project price is agreed after the free review, with a date attached. Running the result afterwards is the managed plan: one fixed monthly fee, scoped to your footprint, month to month.
Starter
- All four agents under policy
- Terraform ownership and drift control
- CI/CD with security gates
- 24/7 incident response, 99.9% uptime SLA
- Monthly cost reconciliation
Growth
- Everything in Starter
- EKS operations and upgrades
- Compliance automation with evidence export
- SOC 2 readiness in six weeks
- Disaster recovery, tested on a schedule
Scale
- Everything in Growth
- A named lead engineer
- Custom response and resolution targets
- Migration and re-platforming projects
- Quarterly architecture reviews
Already on AWS and only need it run? See the managed AWS and DevOps service. Only need the bill fixed? The cost audit is free and read-only.
From customers
What engineering leaders say.
“Since bringing DevLift's AI agents into our production environments, our infrastructure operates seamlessly. We established strict, automated security guardrails without slowing down our deployments, and Finly optimized our cloud waste by thousands of dollars automatically.”
“DevLift completely removed the ops toil from our sprint cycles. Instead of manually wrestling with IaC and chasing compliance drift, we rely on their platform to keep our environments stable and audit-ready. It's like having a senior SRE on staff 24/7.”
Case studies
What running it looks like.
Three engagements: the infrastructure chores that went away, and what the invoices and the auditors saw next.
Coinshift Security guardrails on every deploy, and cloud waste cut automatically.
Read the case study
Infrastructure chores out of the sprint, and environments that stay audit-ready.
Read the case study
Regulated money movement, without paying for two of everything.
Read the case studyTrack record
Built by operators, not theorists.
We ran production for fintech and crypto companies for four years before we encoded the recurring work into agents. The engineers who did it are the ones who plan your migration and sit on your rotation afterwards.
The people behind the agents
DevLift is built by a small DevSecOps team in Dubai. Everyone touches production, everyone talks to clients, and the engineers who operate your accounts are the same ones who answer the page.
- Headquartered in Dubai. Runs production for fintech, crypto and AI companies across the UAE, the US and the UK.
- OSWE-certified engineers, DEF CON and Black Hat speakers and former CTF leads, with five discovered CVEs between them.
- Four years operating infrastructure by hand before the recurring work was encoded into the agents.
- A shared pager. Someone is reachable when it breaks, under an SLA, and the same engineers approve every agent change.
The DevLift team, 2026.
Founder
Harshil Olavakott
Founder and CEO, DevLift. LinkedIn
Cloud architect and DevSecOps specialist, building and running infrastructure on AWS and Azure since 2012. He has led engineering at Dentsu and ran production for fintech and crypto teams for four years before turning that work into DevLift.
Has built and run infrastructure for
Questions
Before you book.
Do you do fixed-price projects?
Yes. The project is scoped after the free review, with a fixed price and a date. There are no change orders for work that was in the scope, and the managed plan is there afterwards if you want us to keep running it.
Do you only do AWS?
Mostly. AWS is where most of our engagements are and where the deepest work is. Sage writes Terraform for AWS, Azure and GCP, so a target on either of the others is planned and applied the same way.
Do we have to take the managed plan afterwards?
No. The project stands on its own. Everything lands in your Terraform and your repositories, with diagrams and runbooks, so your team can run what we built. The managed plan is an option, not a condition.
How long does a migration take?
It is planned in the review, wave by wave, from what runs and what depends on what. We run waves with parallel running and a rehearsal before each cutover rather than promising a number before we have seen the estate.
What do we hand over at the end?
Terraform in your repositories, architecture diagrams, runbooks for the new estate, and the cutover record: what moved, when, who approved it and how it would be rolled back.
What about downtime?
Each wave has a rehearsal in staging, a cutover window agreed with you, and a rollback path that has been tested before the window opens. The source keeps running alongside until you sign the wave off.
Start with a free review of what you have.
Book a free 30-minute demo with an engineer. Bring the estate you want to move or fix and leave with the review scoped and a first read on the wave order.