What we do — and what you walk away owning.
Four engagements. Each has a defined deliverable, a price agreed before it starts, and a handover that leaves you independent of us.
Cloud migration
Move what you already run — servers, databases, licences and all — onto AWS without a weekend of downtime.
Most migrations go wrong in the assessment, not the cutover. We start by inventorying what you actually run and what it costs today, then pick a strategy per workload rather than forcing everything through one pattern. Migration happens in waves, each one reversible until you sign it off.
- AWS MGN
- DMS
- Control Tower
- Transit Gateway
- Direct Connect
- Terraform
What you get
- Discovery and dependency map of the current estate
- Per-workload strategy: rehost, replatform, refactor or retire
- Side-by-side TCO model — today's spend against projected AWS spend
- Landing zone with account separation, guardrails and SSO
- Wave plan with rollback criteria for every cutover
- Data migration, including live databases with minimal downtime
- Two weeks of hypercare after the final wave
Deployment & platform engineering
Your product, running on AWS the way it should have been from day one — reproducible, observable and cheap to change.
If you have already built something and need it live on AWS, this is the work. Infrastructure defined as code so nothing lives only in one person's console history, a pipeline that ships on merge, and enough observability that you find out about problems before your customers do.
- ECS
- EKS
- Lambda
- API Gateway
- CDK
- GitHub Actions
- CloudWatch
- OpenTelemetry
What you get
- Infrastructure as code — Terraform or AWS CDK, your choice
- Multi-account setup with isolated dev, staging and production
- CI/CD pipeline with automated rollback
- Container or serverless runtime, sized to the actual workload
- Logging, metrics, tracing and alerts that page a human
- Backup, restore and a disaster-recovery runbook you have tested
- Handover documentation and a walkthrough with your team
Product & application development
Software built by the same people who run it — web apps, APIs, data pipelines and AI features.
We are engineers before we are consultants. When the gap is the product itself rather than the infrastructure under it, we build it: full-stack applications, integration work between systems that were never meant to talk, data pipelines, and AI features that do something useful rather than something impressive.
- TypeScript
- Python
- Next.js
- Node.js
- PostgreSQL
- Bedrock
- Step Functions
What you get
- Full-stack web applications and internal tools
- APIs and integrations between existing systems
- Data pipelines, warehousing and reporting
- AI features on Amazon Bedrock — retrieval, extraction, assistants
- Automated tests and a pipeline that runs them
- Source code in your repository, under your licence, from day one
Cost & Well-Architected review
Find out what your AWS bill is actually paying for, and what it would take to halve it.
AWS bills grow quietly. We audit the account against the Well-Architected pillars, put numbers against every finding, and rank the fixes by what they save versus what they cost to do. You get the report whether or not you hire us to implement it.
- Cost Explorer
- Compute Optimizer
- Trusted Advisor
- Security Hub
- GuardDuty
What you get
- Line-by-line spend analysis with the top cost drivers named
- Right-sizing, Savings Plans and Reserved Instance modelling
- Security review: IAM, network exposure, encryption, secrets
- Reliability review: single points of failure, backup coverage
- Findings ranked by saving against effort — you choose what to do
- Follow-up review after the changes land
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.
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.
Not sure which of these you need?
That's what the discovery sprint is for. Describe what you run today and we'll tell you honestly which of these — if any — is worth your money.
We reply within one business day · Dubai, UAE · GST (UTC+4)