DevOps on Demand
Senior AWS and platform engineering capacity, in a committed monthly block. You control the repos, the roadmap, and the runbook — we add build depth against a backlog you prioritize, with direct Slack, weekly written status, and delivery Monday–Friday, 8am–6pm Pacific Time. Engagement-specific work lands in your repositories as it's produced; ownership and reusable-material licenses follow the engagement terms.
One hour with the engineer who does the work. Verbal advice, no obligation, no deck.
The same engagement at every block
- A shared backlog you prioritize
- Direct Slack access to the engineer doing the work
- Weekly written status — hours used, work in progress, what's next
- Delivery during business hours: Monday–Friday, 8am–6pm Pacific Time
- Engagement-specific work committed to your repos as it's produced, with reusable dependencies listed in the handoff manifest
- Ninety-day initial commitment, then month-to-month
Monthly capacity, published
Most of one senior engineer's committed month — subject to availability; ask at the consult.
Choose an exact committed block of at least 10 hours. The cards show the minimum monthly fee at each rate threshold; your monthly fee is your exact block multiplied by that tier's rate. Every tier gets the same engineer, Slack channel, and weekly status.
Deliberately limited
DevOps on Demand is delivered personally by the founder, so committed hours are deliberately limited to what one senior engineer can deliver well. When they're full, new retainers join a waitlist: you get a realistic start date at the consult — never oversold hours.
Need more than the largest block? Talk to us — if it's more than one senior engineer can deliver well, we'll say so.
You keep the keys
Your accounts, your repositories, your on-call rotation, your operational ownership — none of that transfers to us. Incident response and after-hours coverage stay with your team; if you need a vendor to run your environment around the clock, that's a different kind of firm, and we'll say so and point you there. What you get here is senior build-and-improve capacity designed to compound — the aim of every month is a platform that's more automated, better documented, and easier for your own team to run.
- Lean engineering teams with a roadmap already in motion
- Teams coming out of a migration or platform build who want the momentum to continue
- Companies that need senior AWS depth without a full-time platform hire
- Teams that want to own their infrastructure — and want help making it more ownable every month
The terms, plainly
- Renewal — after the initial ninety days the retainer continues month to month; either side can end it with at least thirty days' written notice. An already-invoiced month runs to its scheduled end, and unused hours in that final month are not refunded.*
- Tier changes — at least thirty days' written notice, effective at the start of the next monthly cycle after the notice ends. Increases can start sooner by written agreement; decreases don't take effect during the initial ninety days.*
- Absences — planned absences of a week or longer are flagged at least ten business days ahead, and a materially affected month is prorated or paused by agreement.*
- If we became unavailable — current engagement-specific work already lives in your repos, dependency access is documented, and every credential path is yours to revoke; an already-invoiced month runs to its scheduled end. Full continuity mechanics: Security & Trust.
*Contract terms are drafts pending attorney review.
Frequently asked questions
How do the hours work?
You commit to an exact monthly block of at least 10 hours. The hourly rate changes at the published 10+, 20+, 40+, and 80+ thresholds, so the cards show the minimum monthly fee at each rate; your invoice is your exact block multiplied by that rate. Hours are consumed within the month and don’t roll over. We tell you before the block runs out; hours beyond it happen only with your prior written approval at your tier rate — otherwise the work picks up at the next cycle.
What is the minimum commitment?
Ninety days, then month-to-month. The renewal, notice, and tier-change mechanics are spelled out in the terms summary above — stated here so nothing in the paperwork surprises you.
What kind of work fits?
The ongoing stream that never fits a project: architecture reviews before big decisions, IaC improvements, pipeline work, cost checkups, security hardening, and the questions in between. When a backlog item grows into a real project, either of us can propose moving it to its own fixed-price SOW — by agreement, never by surprise.
How fast do you respond?
Requests through the agreed channel are acknowledged within one business day, with a plan or triage decision shortly after. Work runs Monday–Friday, 8am–6pm Pacific Time, with weekly written status. These are working expectations we hold ourselves to, not contractual SLAs — and the engagement terms state the same expectations, so the paperwork matches this page.
Who owns the work?
Engagement-specific code, pipelines, documentation, and runbooks are delivered into your repositories and accounts as produced, with ownership transferring on payment under the engagement terms. Reusable Uptempo materials keep the agreement’s license carve-out and are listed with continuing-access terms; nothing is hidden in an inaccessible private dependency.
Put a senior engineer on your backlog
Start with the free consult — we'll look at the backlog together, tell you which block actually fits, and give you a realistic start date.
Book the Free Consult