AWS infrastructure for startups

Production-ready AWS, without hiring DevOps.

Fixed-price AWS setup for startups, built with Terraform and GitHub Actions in your own AWS account by a senior DevOps engineer. You own all of it.

Book a free 20-minute call See packages and prices
Fixed prices, agreed in writing Your AWS account, your code No lock-in
your-company/infra · delivered to your repo
├─ .github/workflows/
│ └─ deploy.yml # OIDC, no stored AWS keys
├─ environments/
│ ├─ dev/ # 10.10.0.0/16
│ └─ prod/ # 10.20.0.0/16
├─ modules/
│ ├─ network/ # VPC, subnets, NAT
│ ├─ identity/ # SSO, least-privilege roles
│ ├─ database/ # RDS or DynamoDB
│ ├─ compute/ # ECS Fargate or Lambda
│ └─ guardrails/ # CloudTrail, budgets, alarms
└─ HANDOVER.md
dev prod · approval required state in your account

Sound familiar?

Most startups we talk to hit one of these moments. Each one is a good time to get the foundation right.

"We've outgrown Render, Railway or Heroku."
You need real AWS networking, a managed database and room to grow, without a six-month detour.
"A customer asked about our security."
An enterprise deal or investor wants to know how production is separated, logged and protected.
"Nobody fully understands our AWS account."
It was clicked together early on, and every change now feels risky.
"Our AWS bill keeps growing."
Costs climb faster than usage, and nobody owns finding out why.

Packages

Fixed scope. Fixed price. Written down before we start.

No hourly billing and no surprises. AWS charges are billed to you directly by AWS, so you always see exactly what your infrastructure costs.

Start here

AWS Foundation Review

For when you have AWS already and want to know what's risky, what's wasted and what to fix first.
$950 fixed · 1 week
  • Read-only review of security, IAM, networking, backups and cost
  • Findings ranked by risk and effort to fix
  • 60-minute walkthrough with the engineer who did it
  • Full fee credited if you book a Launchpad within 30 days
Book a review
Core package

AWS Launchpad

For when you're ready to run production on AWS properly, from scratch or from a hand-built account.
from $7,500 new build · 2–3 weeks
  • Separate dev and prod environments, each with its own VPC
  • SSO access, least-privilege roles, CloudTrail, budgets and alarms
  • Managed database and hosting for your app on ECS Fargate or Lambda
  • Terraform in your repo; GitHub Actions deploys with OIDC, no stored keys
  • Handover doc, recorded walkthrough and a 30-day fix period
Already on AWS? We start with a Review, then quote a fixed price to adopt, rebuild or mix.
Plan my Launchpad
After Launchpad

Care Plan

For when you want an expert on hand for changes, reviews and questions, without a full-time hire.
$1,000 per month
  • Up to 8 hours a month of changes and reviews
  • Replies within 2 business days
  • Monthly summary of what changed and why
  • Cancel any time with 30 days' notice
Planned work, not on-call. See the FAQ for what that means.
Ask about the Care Plan

What you get

See exactly what you're paying for

No black boxes. Here is the architecture a typical Launchpad builds, and what a Foundation Review report looks like.

AWS Launchpad: the architecture

Your GitHub
Infrastructure repo
Terraform for every environment
GitHub Actions
Plan on pull request, apply on merge
OIDC: short-lived credentials, no stored AWS keys
deploys
Your AWS account
you keep root, billing and MFA
SSO and least-privilege roles CloudTrail audit log Budgets and cost alerts CloudWatch alarms Terraform state (S3)
devVPC 10.10.0.0/16
Public subnets
Load balancer · NAT gateway
Private subnets
App: ECS Fargate or LambdaDatabase: RDS or DynamoDB
Changes apply on merge
prodVPC 10.20.0.0/16
Public subnets
Load balancer · NAT gateway
Private subnets
App: ECS Fargate or LambdaDatabase: RDS or DynamoDB
Changes wait for your approval
A typical Launchpad for one application. Separate networks keep dev and prod apart. Exact services depend on your app and are agreed in the design step. Already on AWS? We can adopt what you have instead of starting over.

AWS Foundation Review: a sample of the report

Findings, ranked by risk
Each finding comes with the exact fix and who should do it
EXAMPLE FINDINGS
RiskFindingAreaEffort to fix
HighRoot user has no MFA and was used in the last 90 daysIdentityMinutes
HighAn S3 bucket with customer uploads allows public readDataMinutes
MediumProduction database has no automated backups or point-in-time recoveryResilienceHours
MediumDev and prod share one VPC and the same IAM usersNetworkingProject
LowIdle volumes and unused IP addresses still billed every monthCostMinutes
Limited spots

Founding client program

We're taking a small number of founding clients. You get reduced Launchpad pricing and free early access to the InfraPrompt platform. In return, we ask for a short monthly feedback call and, with your approval, a testimonial.

Ask about a founding spot

How it works

From first call to running in production

  1. 01
    Free 20-minute call
    Tell us what you run and where it hurts. We'll recommend one package, or tell you if you don't need us yet. Already on AWS? We start with a Review.
  2. 02
    Fixed quote in writing
    Scope, timeline, price and exactly what access we need, in a short statement of work.
  3. 03
    Built in your account
    Design first, then dev, then prod. Production changes only go ahead with your approval.
  4. 04
    Handover
    A walkthrough, documentation and the code in your repo. Our access is removed and confirmed in writing.

Security and ownership

Your account. Your code. Your keys.

Everything is built in your AWS account and committed to your repository. If you stop working with us tomorrow, nothing breaks and nothing needs migrating.

Access that matches the job
Read-only for reviews. Time-limited, MFA-protected admin during a build. Removed at handover.
Everything logged
CloudTrail is switched on before we make any change, so every action is on record.
No root, no stored keys
You keep root, billing and MFA. Deployments use short-lived OIDC credentials.
Revoke any time
You control every role we use, and you can remove it whenever you like.

How we're different

Typical hourly contractorInfraPrompt
PriceHourly, open-endedFixed, agreed in writing up front
Starting pointA blank repositoryTested InfraPrompt blueprints, adapted to you
AccessOften shared admin keysScoped, logged, time-limited, removed at handover
What's left behindWhatever was documentedTerraform, pipelines, handover doc and a recorded walkthrough
What comes nextCall them againRequest and approve changes yourself in InfraPrompt

Coming from the same team

We're turning this work into software.

InfraPrompt lets your developers describe what they need and get production-ready AWS in your own account, with approvals before anything reaches production. Our clients get early access first.

Request early access
We need an API with a Postgres database.
Proposed: orders-apidev
+ load_balancer · public subnets
+ ec2_instance · private subnet
+ rds_postgres · private
+ security_groups · least privilege
prod: pending approval

Questions

Who actually does the work?

A senior DevOps engineer with hands-on production experience, the same person from design to handover.

Do you provide on-call or incident response?

No. We do planned work: builds, reviews and changes, with a stated reply time. We set up alarms so your team hears about problems first, and we'd rather tell you that clearly than promise 24/7 cover we can't give.

What access do you need to our AWS account?

For a review, a read-only role. For a build, a time-limited admin role with MFA, after CloudTrail is on. You create the roles, keep root and billing, and can revoke access at any time. We never ask for root credentials or long-lived keys.

What do we own when you're done?

Once the work is paid for, you own the infrastructure in your account, its Terraform state and the code we write for you. Some of that code comes from our reusable blueprints; those stay ours, and you get a permanent license to use, change and extend them for your own systems. Either way, everything runs in your account and your repository, so your team or a future hire can take it over at any time.

Can you move us off Heroku, Render or Railway?

Yes. The Launchpad builds the AWS side. Moving your data and cutting over traffic depends on your setup, so we scope and quote it separately on the call.

We already have AWS. Can you work with it?

Yes, and most startups we talk to do. We start with a Foundation Review to see exactly what's there, then quote a fixed price for one of three paths:

  • Adopt: bring what you have under Terraform as it is, then improve it step by step.
  • Rebuild and migrate: build clean environments alongside the old ones, move across, then retire the old setup.
  • Mix: keep what's sound, like your database and data, and rebuild what's risky.

Because your production is live, we confirm your backups first, and our first step changes nothing at all. Every production change waits for your approval. The Review fee is credited toward the work.

Do you work with Kubernetes, GCP or Azure?

Not right now. We focus on AWS, using ECS Fargate or Lambda, which suit most early-stage startups and are simpler to run without a dedicated platform team.

What does AWS itself cost?

AWS bills you directly, so there's no markup. We'll estimate monthly costs during design and set budget alerts so there are no surprises.

Free · 20 minutes

Get your AWS foundation right, once.

Tell us a little about your setup. We'll set up a short call and tell you honestly whether you need us, and which package fits.

What happens next
  1. 1We reply within 2 business days to find a time.
  2. 2A free 20-minute call about your setup and what you need.
  3. 3We recommend one package, or tell you honestly if you don't need us yet.

Prefer email? Write to support@infraprompt.ai

We only use this to reply to you. See our privacy notice.