06 · Pricing
Free until it matters.
You won't pay us until you have real users. AWS pays AWS directly — our line on your bill stays small.
Free
$0/forever
For solo founders shipping their first thing. Real infrastructure, real limits.
- 1 service · 1 environment
- Your AWS account · always yours
- CLI + MCP server included
- GitHub deploy pipeline
- Community support
Pro
$99/mo per project
For teams going from prototype to paying customers. Day-one buy for any real project.
- Three environments (dev · stage · prod)
- Custom domain + HTTPS, managed
- AI assistant powered by Claude Sonnet 4.6
- Canary deploys + auto-rollback
- Custom policies + audit log
- Priority email support
Team
$399/mo
For teams running multiple projects with role-based access and SLAs.
- Multi-project orgs
- Role-based access (RBAC)
- SLA on the control plane
- Slack alerting + on-call routing
- Multi-region pipelines
- Priority engineering support
Enterprise
Custom
For when production matters more than your weekend. EC2-backed compute, compliance add-ons.
- EC2 + dedicated tenancy options
- SSO + SCIM
- SOC 2 readiness package
- Custom IAM boundary policies
- Onboarding engineer assigned
- Slack channel with our team
07 · Questions
Things founders ask us.
That's the entire reason it exists. If you can use git push and click a button to authorize GitHub, you can ship to production with StrictOps. We don't expose Terraform, CloudFormation, or YAML to you — those exist under the hood, generated from your repo.
Your app keeps running. Everything provisioned by StrictOps lives in your own AWS account — pipelines, infra, secrets, all of it. The control plane is the only thing that goes away, and you can replace it with a normal Terraform workflow because that's all we're generating anyway.
Because doing one cloud extremely well beats doing three clouds badly. GCP and Azure support are on the roadmap once we've earned the right to be opinionated about them. If you need them today, we're probably not the right fit yet.
Vercel, Railway, and Heroku are hosting platforms — your app runs on their infrastructure. StrictOps is a control plane — your app runs on yours. Different trade: less convenient at the very start, but no migration tax when you grow, no surprise bills, no vendor lock-in on data residency or compliance.
TypeScript + Next.js (web) and NestJS (API/workers), with Postgres via Prisma. That tight default is what makes ~30-minute onboarding possible. Python/FastAPI, Go, and serverless adapters are on the roadmap.
They can, if you let them. Claude, Cursor, and Codex can all be configured to open PRs against your repo, which then flow through our pipeline like any human PR — same checks, same policy gates, same approval before prod. You stay in control of the merge.
Ready to ship
with AI?
Vibe coding gets you to v1. StrictOps gets you to production — without learning DevOps.