Get a defined DevOps service for your AWS environment. AI assists investigation and preparation; CloudHero engineers handle the production work agreed in your service scope.
Agree the covered estate during onboarding.
Plan projects and application responsibilities explicitly.
| Incident / request | Acknowledgement | What happens next |
|---|---|---|
| P1 · critical incident | 30 minutes, 24/7 | Triage and mitigation within the approved incident scope. Use the agreed on-call route or automated alert. |
| P2 · priority incident | 1 business hour | Assessment and plan within 4 business hours. Remediation immediately when required, otherwise within 1 business day. |
| P3 · planned request | 1 business hour | Proposal within 1 business day. Start within 3 business days after approval, subject to capacity and dependencies. |
Business hours: Monday–Friday, 09:00–18:00 Bucharest time. Acknowledgement targets are distinct from restoration times. Severity definitions and scope are agreed in your service schedule.
AI helps correlate alerts, investigate logs, preserve incident context and prepare recommendations. Your CloudHero team reviews the findings and retains authority over production changes.
We agree the models, data access, logging and approval boundaries before enabling these workflows. Operational continuity does not depend on an AI system being available.
Review security and data handlingThe same P1/P2 targets across packages. More capacity for planned engineering work as your needs grow.
For an agreed operational baseline.
For an agreed operational baseline.
For an agreed operational baseline.
Engineering days are up to eight hours and do not roll over. Delivery uses a pooled team with a stable two-engineer rotation. New-client onboarding is assessed and quoted separately. Initial term: three months, then monthly with 30 days’ notice. Final scope and package fit follow the platform review.
Monitoring, core infrastructure as code, supported upgrade paths and a manageable incident profile.
Document access, dependencies, runbooks, escalation and the boundary with your application team.
Track incident response and recovery separately, recurring issues, changes, costs and the next actions.
It is the P1 acknowledgement target through the agreed on-call or alert route. The team begins triage and mitigation within the approved scope. Restoration depends on the incident and its dependencies.
Eligible P1/P2 incidents within the Day-0 baseline are not capped by incident count. The service schedule defines incident coverage separately from planned engineering capacity.
Two P1 or five P2 incidents within a rolling 30 days, the same root cause three times, or material growth triggers a joint review. Response continues unchanged while any service changes require written agreement.
Application-release execution and application-code changes are outside this infrastructure baseline. We can discuss a separate scope for those responsibilities.
Yes. We review the environment first, identify prerequisites and agree any onboarding work before the operating service begins.
Up to $10,000 in AWS credits for eligible startups through CloudHero’s AWS Resell program.
Use the CloudHero product to review potential cost opportunities before changing your environment.
Start with a conversation about your environment, your priorities and the work you need someone to own.