DevOps hours, without the full-time hire.
Pick the level you need now and change it as the business grows. You pay for the hours you use, not a salary, recruitment fees and a desk.
Pick a level
Setup and monitoring
Early teams where the work is mostly keeping things healthy.
One-off setup fee, then a monthly plan
- We set up or clean up your AWS account once, for a fixed quote.
- Then monitoring, alerts, backups, security checks and a monthly cost review.
- Incident response within 4 hours.
Half day
Teams shipping often who need someone on infrastructure most days.
About 80 hours a month, priced on scope
- Deployments, pipelines and infrastructure changes as they come up.
- Monitoring and incident response included.
- A second engineer for cover when one of us is away.
- A monthly report on hours used and issues found.
Full day
Scaled teams that need a DevOps function, not one person.
About 160 hours a month, priced on scope
- A full working day of cover, scheduled around your hours.
- Two engineers, so leave and sick days don't stop the work.
- A written handover at the end of every shift.
- We join your weekly engineering call.
What a full-time hire actually costs
Salary is only part of it. Add recruitment fees in the first year, payroll taxes and benefits, a laptop and software licences, training, and cover for holidays and sick leave. If the person resigns, you pay most of that again.
A dedicated plan is one monthly number, and the work doesn't depend on one person.
How it starts
- 01
A 20-minute call to pick a level.
- 02
Read-only access first. We review your setup and agree the first month's priorities.
- 03
Two to four weeks to learn your system, then steady work.
- 04
Move up, move down or stop with 30 days' notice.
Common questions
Can we change level later?
Yes, with 30 days' notice. Most teams start small and move up as they grow.
Which time zones do you cover?
We're in India (IST). That's a full working-day overlap with Australia and Europe, and mornings or evenings with the US. Full-day plans are scheduled around your hours.
What happens if one engineer leaves?
The second engineer already knows your setup, and every shift ends with a written handover, so nothing lives in one person's head.
Who has access to our AWS account?
An IAM role you create and can revoke at any time. No root credentials and no shared logins.
Not sure which level fits?
Book a 20-minute call and I'll suggest one. Or send a note below.