.avif){kind=small}
We're already on AWS — can you fix our setup?
Honestly: that’s a different job, and pretending otherwise would waste your money. Quick Start is for greenfield — getting onto AWS cleanly the first time. If you’re already on AWS and the setup hurts, you want our Modernization package instead. Write us through the form below and say so in the “current setup” field; we’ll route you straight there instead of selling you the wrong thing.
How does the AWS funding actually work?
Most Production Launch projects qualify for AWS Proof-of-Concept funding — we check your eligibility for free and handle the application end-to-end. Funding is tied to actual AWS usage, which is why it applies to Production Launch — a running, billing workload. Eligibility and amounts are decided by AWS, not by us — which is exactly why we check before you commit, not after.
How soon can you start, and do the timelines hold?
Reply to the form and we’ll give you a concrete start date. The timelines hold because the scope is productized: we deploy from templates we’ve built and validated end-to-end, so your project is parameterisation, deployment, and proof — not invention. Buffer for the usual customer-side delays is already inside the 5–10 days and 3–4 weeks. The deadline we give you is the deadline you get.
What will my AWS bill actually be?
Depends on what you run, and anyone who quotes you a guaranteed number is guessing. What we can say without guessing: a Foundation environment idles around $80–95/month (mostly the NAT Gateways) — it deploys no workload, so nothing else is running up the meter. Either way, your exact cost baseline is a deliverable: the expected bill for every deployed resource, calculated for your deployment, in writing — not a landing-page estimate. Billing alarms are part of both tiers, so the first surprise never becomes a second one.
What do you need from us to start?
Very little. An AWS account (we help set up secure access at kickoff — a scoped read-only role plus a deployment role via OIDC trust; no shared credentials, no static keys). For Production Launch: your application — an existing Dockerfile is ideal, but we’ll advise on containerizing or Lambda packaging if you don’t have one — and a repo on GitHub, GitLab, or Bitbucket (CodeBuild also works). Optional: AWS IAM Identity Center (SSO) wiring on request. No AWS expertise required on your side — that’s what the handover workshop and runbook are for.
Do we need you after handover?
No — and that’s by design. Your team leaves the handover workshop able to operate and redeploy everything: the code is in your repo, the runbook and incident playbook are written for your on-call, and the workshop recording is there for whoever joins later. If you want us afterwards — for the next workload, a migration, or modernization — we’re easy to find. But needing us is not part of the product.
.avif)
.avif)
