Migrate to AWS.Build on AWS.Ship faster.
Kloudly is a Dubai-based engineering team. We move companies onto AWS, deploy their products there properly, and build the software that runs on top.
Fixed price
Two-week discovery, before you commit to anything
Your accounts
Code and infrastructure stay in your name throughout
Senior only
The engineer who scopes it is the one who builds it
Day to day, we work in
- Terraform
- AWS CDK
- ECS & EKS
- Lambda
- Aurora & RDS
- Control Tower
- DMS
- Bedrock
- GitHub Actions
- OpenTelemetry
Four ways we're usually brought in
Most engagements start with one of these and grow into the next. You can also hire us for exactly one and stop there.
Four phases, and you can stop after any of them
No open-ended retainers dressed up as a project. Each phase has a deliverable, a price and a decision point at the end of it.
- 01
Discovery
1–2 weeks
We look at what you run, what it costs and what hurts. You get a written assessment and a scoped plan with a price on it. If that plan says you do not need us, it will say so.
- 02
Design
1–3 weeks
Target architecture, account structure, network layout, security model and a migration or build sequence — reviewed with your team before anything is provisioned.
- 03
Build & migrate
Scoped per wave
Work lands in reviewable increments. Everything is defined as code, every wave has rollback criteria, and you can see progress in your own repository the whole time.
- 04
Handover & operate
Ongoing or fixed
Documentation, runbooks and a working session with whoever will own it. Stay on a monthly retainer if you want us, or take the keys and run it yourself — both are fine.
Small team, unusually few strings attached
Three founders who got tired of watching consultancies bill for complexity they created. These are the rules we run the company by.
- 01
You own everything we build
Code in your repositories, infrastructure in your accounts, billing in your name. Nothing we do should make leaving us expensive — if it does, we built it wrong.
- 02
Senior engineers only
Three founders, no bench, no pyramid. The person who scopes your project is the person who writes the Terraform. It is why we take fewer clients at a time.
- 03
If it isn't in code, it doesn't exist
No console-only changes, no undocumented one-offs, no tribal knowledge that leaves when we do. Every environment can be rebuilt from a repository.
- 04
We'd rather tell you not to
Some workloads should not move. Some products should not be built. We would rather lose the engagement than take money for work that will not pay you back.
Three ways to work with us
Every one of them starts with a conversation and a written scope. None of them starts with a twelve-month commitment.
Discovery sprint
Fixed price
Two weeks, one deliverable: an honest assessment and a costed plan.
- Estate and dependency inventory
- Current versus projected AWS cost
- Risk register and target architecture
- Fixed-scope proposal for the work that follows
Migration or build programme
Scoped per phase
The main event — landing zone, waves, cutovers and hypercare, or a product built end to end.
- Phased delivery with a price per phase
- Everything as code, in your repositories
- Weekly demo and written status
- Hypercare after the final cutover
Embedded engineering
Monthly retainer
A senior engineer inside your team for a set number of days each month.
- Named engineer, not a rotating bench
- Roadmap work, on-call support or both
- Cancel with 30 days' notice
- Knowledge stays with your team
The things people actually ask
If yours isn't here, send it over — we answer email quickly.
You're a new company. Why should we trust you with production?
Because you should judge the work, not the letterhead. Start with a two-week discovery sprint — it is fixed price, it ends in a written plan you own, and it is small enough that being wrong about us costs you very little. Every engagement after that is phased for the same reason.
Are you an AWS Partner?
Not yet. We are working through the AWS Partner Network requirements and will say so here the moment it is granted rather than before. What we can tell you today is what we have built and how we work — ask us for specifics on a call.
We're not on AWS at all. Is that a problem?
No, that is the common case. On-premises servers, a colocation rack, another cloud, or a mix of all three — the discovery sprint is designed exactly for working out what should move, what should be rebuilt, and what should be left alone.
Do you work in our AWS account or yours?
Yours, always. We work through a role you create and can revoke, in accounts you own, with billing in your name. You are never in a position where leaving us means losing your infrastructure.
What happens when the project ends?
You get the code, the infrastructure definitions, the runbooks and a working handover session with whoever is taking over. Retainers exist if you want us to stay, but nothing is built in a way that requires it.
Fixed price or time and materials?
Discovery is always fixed price. After that we scope and price per phase, so you approve a known number before each one starts. Retainers are a fixed number of days per month.
Where are you based, and does it matter?
Dubai. It matters if you need someone in GST business hours, on site in the UAE, or working in me-central-1 and me-south-1 with data-residency requirements. We work with teams outside the region too.
Tell us what you're running.
One email, one call, and a written view of what moving to AWS would actually involve for you. No deck, no discovery fee for the first conversation.
We reply within one business day · Dubai, UAE · GST (UTC+4)