About OpsRunway.

Why we work with startups specifically.

A platform team at a 60-person SaaS company asks about maturity models and on-call rotas. A founder with eight engineers asks when the credits run out, whether to hire, and what the investors' technical reviewer will find. Same skills, different conversation.

So we package the work for that moment: a short fixed-price review first, cost work you can pay for out of the savings, monthly help without a hire, and a clean handover when you're ready for your own platform engineer.

A few opinions we'll defend.

• Boring infrastructure is a feature. Most startups need ECS, RDS and good backups, not a platform.
• Your AWS bill before credits is the real bill. Plan around that one.
• Everything we build should be readable by the next engineer, including your first hire.
• The best outcome is a client who outgrows us.

How we research and fact-check our guides.

• Primary sources first. Prices come from AWS's own pricing pages, credit rules from AWS's Activate pages, pay data from named datasets. Every figure links to where it came from.
• Dated and re-checked. Each guide shows the date its facts were last verified. We re-check the AWS numbers every quarter and update the date only when we've actually looked.
• Labelled when illustrative. Example companies, sample reports and worked examples are marked as such. We don't publish client names without permission.
• Written by engineers. Guides are written and reviewed by the engineers who do the work, from problems we see in real AWS accounts. Writing tools may help with drafts; a person checks every claim before it goes out.
• Corrections. Spot something wrong or out of date? Email hello@opsrunway.com and we'll fix it.