CLOUD MIGRATION & HARDENING
Senior AI-native engineers move your app into your own AWS or Google Cloud account, with deploys that don't need downtime, backups you've actually restored, and alerts that reach you before your users do. Fixed price, 3 to 6 weeks.
From $6,500 · fixed after the call · your cloud account
3–6 weeks
From scoping call to cut-over
From $6,500
Fixed price, set after the scoping call
0
ZapBook crashes in 6 months, down from weekly
Your account
Infrastructure, repo and keys stay yours
WHO IT'S FOR
01
Friday nights, launch days, the morning a newsletter goes out. One server takes all of it, and it falls over.
02
Releases mean SSH, a checklist in someone's head and a quiet prayer. When that person is on holiday, nothing ships.
03
There's a backup job somewhere. Nobody has tried bringing the database back from it, so nobody knows if it works.
04
The app started on Replit or a similar host to prove the idea. Now customers pay, and the host was never meant to carry them.
SELF-CHECK
Answer for your own product. Nothing is sent anywhere until you choose to book.
WHAT YOU GET
Everything below lands in your cloud account and your repo. You hold the keys from day one.
EXAMPLE ARCHITECTURE
Every merge is reviewed by a senior engineer, and the infrastructure is written as code in your repo, so the next team can read it.
See how the cut-over works ↓THE CUT-OVER
The old server keeps running until the new setup has proven itself. You can stop the move at any point before step 4.
01
WEEK 1
We list every service, background job, webhook and secret, estimate your monthly cloud bill, and agree a cut-over window with you.
02
WEEKS 2–3
Containers, infrastructure and CI/CD go up in your account. A full copy of the product runs on staging next to the old server.
03
REHEARSAL
We run the whole cut-over on staging, including a database restore and a rollback, and time each step.
04
CUT-OVER
Traffic moves in a planned window. The old server stays on standby until the new setup has run clean, and rollback is one step.
PRICE
CLOUD MIGRATION & HARDENING
from $6,500
3–6 WEEKS · FIXED AFTER THE SCOPING CALL
Most single-app moves land near the low end. Your fixed price comes out of the Week 1 plan, before any infrastructure work starts.
WHAT MOVES THE PRICE
Cloud costs are billed to your own account at cost. Prices are in USD and exclude any applicable taxes.
PROOF
0 crashes
Booking SaaS
ZapBook had grown for five years on a single VPS and was crashing weekly. As part of a 12-month engagement with an embedded team of four, we moved it to Google Cloud Run with Docker and zero-downtime deploys. Since then it has gone six months without a crash. The engagement is now in Phase II.
GCP · CLOUD RUN · DOCKER · ZERO-DOWNTIME DEPLOYS
HELM's rebuild runs on the same stack: Next.js, NestJS, PostgreSQL and GCP Cloud Run.
Read the ZapBook case study →AFTER THE MOVE
You get 2 weeks of support after cut-over. After that, pick what fits, or run it yourselves with the runbook.
Flexible $2,000/mo · Dedicated $4,000/mo
Monitoring, monthly security patches, backup checks and a pool of hours for fixes. For a product that's stable and needs someone accountable.
See the Care Plan →from $3,375/mo
An engineer shipping your roadmap on a set cadence, on the infrastructure we just built.
See the retainer →FAQ
The app keeps running on the old server until the new one has run clean. The database move happens in a planned window agreed with you in advance, after we've rehearsed it on staging.
