Services / Startup Cloud Foundation
AWS set up properly, once, so your team can ship every day.
For startups that deploy by hand, have one person who understands production, or got a surprise AWS bill. We build the base your product runs on and hand it over documented.
AWS · Terraform · GitHub Actions
$ terraform apply✓ dev auto-deploy on every push✓ staging deploy on merge to main✓ production manual approval, blue/green✓ secrets AWS Secrets Manager✓ access per person, least privilege● rollback one click, under 2 min
Sound familiar?
Signs you need this
Deploys mean someone running commands on a laptop
There's no staging environment, so you test in production
Nobody is sure what's running in the AWS account or why
A release has taken the app down in the last three months
The change
Before and after
| Before | After |
|---|---|
| Deploys run from someone's laptop | Every merge deploys through a pipeline |
| Testing happens in production | A staging copy of production for every change |
| Setup lives in one person's head | Everything written as code and documented |
What you get
Deliverables
AWS account structure
Separate accounts or environments for dev, staging and production, with access per person.
Infrastructure as code
Terraform for everything we create, so environments can be rebuilt and reviewed like code.
CI/CD pipeline
GitHub Actions that test, build and deploy on every merge, with safe rollbacks.
Zero-downtime releases
Blue/green or rolling deploys, so users don't notice when you ship.
Security basics
Least-privilege access, secrets out of code, TLS everywhere.
Runbook and handover
Written docs plus a recorded walkthrough your team keeps.
How it runs
Four steps
- ReviewWe look at your current setup and agree the target in writing.
- BuildInfrastructure and pipelines built in your accounts, weekly updates.
- CutoverWe move your app over with a tested way back.
- HandoverDocs, recording and a Q&A session with your team.
What we need from you
- Admin access to your AWS account (or we create one with you)
- Access to your code repository
- One person on your side for a weekly 30-minute check-in
Proof
Done before, in production
- Rebuilt CI/CD across three regional environments: deploy lead time cut by about 35% and failed releases halved
- Set the container and deployment standard adopted by three feature teams: new service setup from days to hours
From our lead engineer's roles at larger companies. See Work.
Fit and price
A good fit if
- You have a product in use and a small engineering team
- You're on AWS or ready to move there
- You want your team to run it afterwards
Not a fit if
- You need an entire platform team permanently
- You're set on a cloud other than AWS for everything
Price Fixed quote after a 20-minute call. Typical scope: 2–4 weeks.
FAQ
Can you work with our existing setup?
Yes. We usually keep what works and bring the rest under Terraform step by step.
Do we need Kubernetes?
Usually not at the start. We pick the simplest option your team can run, often ECS or a managed service.
Who has access afterwards?
You do. Everything lives in your accounts and our access is removed at handover.
Also useful
Tell us what you're building.
20 minutes, no pitch deck needed. You leave with a clear next step, even if it isn't us.