Support and Advisory
Senior AWS and DevOps help in a committed monthly block. You control the accounts, repositories, roadmap, and backlog. We add hands-on engineering and decision support across Terraform, GitHub Actions, GitOps, landing zones, platform work, security, cost, and the operational questions between projects.
Business-hours engineering capacity. Not managed services, monitoring, incident response, or a 24x7 pager.
The same working model at every block
- A shared backlog you prioritize
- Direct client Slack access to the engineer doing the work
- Weekly written status — hours used, work in progress, and what is next
- Delivery Monday–Friday, 8:00 AM–6:00 PM Pacific Time
- Engagement-specific work committed to your repositories as it is produced
- Ninety-day initial commitment, then month to month
Monthly capacity, published
Most of one senior engineer's committed month — subject to availability; ask during the assessment.
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.
The work between projects
Use the block for a prioritized stream of engineering and advisory work: infrastructure changes, module improvements, pipelines, architecture decisions, cost cleanup, security hardening, migration follow-through, platform documentation, or a backlog that needs senior AWS depth.
When one backlog item becomes a defined project, either side can propose moving it into a separate Consulting SOW. That happens by agreement, never by surprise.
You keep the keys and the operating responsibility
Your accounts, repositories, on-call rotation, and operational ownership remain yours. The aim of each month is to make the platform more automated, better documented, and easier for your own team to operate.
- Lean engineering teams with an AWS or DevOps roadmap already in motion
- Teams coming out of a Consulting project that want momentum to continue
- Companies that need senior AWS depth without a full-time platform hire
- Teams that want help making their infrastructure easier to own
Deliberately limited
Support and Advisory is delivered personally by the founder. Committed hours are limited to what one senior engineer can deliver well. When capacity is full, new engagements receive a realistic future start date instead of oversold hours.
Need more than the largest block? Ask. If the requirement is larger than one senior engineer can deliver well, we will say so.
The terms, plainly
- Renewal — after the initial ninety days the engagement 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 do not 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 repositories, dependency access is documented, and every credential path is yours to revoke. Full continuity mechanics: Security and 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 rate changes at the published 10+, 20+, 40+, and 80+ thresholds, so the cards show the minimum monthly fee at each rate. Hours are used within the month and do not roll over. Work beyond the block happens only with prior written approval at the tier rate; otherwise it resumes next cycle.
What is the minimum commitment?
Ninety days, then month to month. Renewal, notice, and tier-change mechanics are summarized above and finalized only in the signed engagement terms.
Is this managed services?
No. Support and Advisory does not include monitoring, pager duty, incident response, uptime commitments, or 24x7 coverage. It is business-hours engineering and decision support against a backlog you own.
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, 8:00 AM–6:00 PM Pacific Time, with weekly written status. These are working expectations, not contractual SLAs.
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 retain the agreement’s license carve-out and are disclosed with continuing-access terms.
Put senior AWS and DevOps help on the backlog
Start with the free assessment. We will review the backlog, tell you which block fits, and give you a realistic start date.
Book Your Free AWS Assessment