THREE TIERS · NAMED ENGINEERS · MONTHLY RETAINER
One good AWS engineer costs more than this and can only be in one place at a time. This is a team with an AWS Hero behind it, on a monthly retainer, running the estate you already have.
Monitoring and alerting, business-hours incident response, monthly cost review, patching and maintenance, and a named engineer who knows your estate.
For: a stable production estate that needs to stay stable, with an internal team that handles day-to-day operations.
Everything in Standard, plus extended response coverage, proactive optimization work each month, architecture review as the estate changes, and involvement in your release process.
For: an estate that is actively changing, where the infrastructure has to keep up with the product.
Everything in Advanced, plus the highest response commitment, dedicated senior capacity each month, direct AWS Hero involvement in architecture decisions, and a quarterly business review with the numbers.
For: revenue-critical estates where downtime is measured in money and the architecture is still being decided.
A remediated estate stays healthy for about two quarters on its own. Then someone ships fast, something gets provisioned outside the pattern, an alert gets muted because it was noisy that week, and the drift starts again. The fix is not another review. It is somebody whose job it is to notice.
Hiring that person is the obvious answer and it is a bad one for most companies at this size. You need three of them to cover on-call properly, they are expensive, they are hard to interview for if you do not already have one, and they leave.
Operations of the AWS estate as agreed at onboarding: monitoring, incidents, patching, cost, and access management.
A named engineer and a shared Slack channel. The same people every month.
Project work. A migration, a modernization or a major architectural change is scoped and priced separately, at a rate that reflects the retainer.
Application development and application support.
Anything outside the accounts agreed at onboarding.
A monthly retainer per tier, quoted on the estate: the number of accounts, the workloads and the coverage you need. Monthly, no setup fee where the estate has been through a Foundation Sprint or a WAFR with allOps. Where it has not, an onboarding assessment comes first, because nobody should take operational responsibility for an estate they have not seen.
Two AWS Heroes, AWS Advanced Tier Partner, DevOps Competency. The external AWS-commissioned technical audit finding on delivery depth applies here more than anywhere: the depth is the product.
Because one person cannot cover on-call, and three people cost more than any tier on this page. Hiring makes sense once the estate is big enough to keep a team busy, and at that point allOps works alongside them.
Yes, and most do. The tier is reviewed quarterly against what actually happened, in both directions.
Yes, scoped to what the tier requires, through a role you control and can revoke. Access is agreed in writing at onboarding, so it is settled long before the first incident.
Managed Services
Share what you need. We will get back to you to discuss the scope.
