Managed Operations & SRE
Between 'one engineer fielding pages at 3am' and a full reliability team. We share the on-call rotation, set uptime targets that matter to your business, and write the response playbooks, until you're ready to hire it in.
Managed operations is what happens after the platform ships: someone has to wear the pager, write the runbooks, run the incident reviews, and feed the lessons back into the platform.
Perpelin joins the on-call rotation alongside your engineers, taking a defined share of pages rather than promising blanket 24/7 cover. SLOs get defined against business-meaningful signals (checkout success, search latency, ingest backlog), not generic CPU graphs. Error budgets drive feature-vs-platform tradeoffs in the open.
Engagements are monthly retainers with a defined scope: rotation share, target MTTR, post-mortem cadence, runbook-maintenance commitment. Not time-and-materials.
Who this fits
Ideal client
- · Teams in the gap between 'one engineer on-call' and 'real SRE team'
- · Series B+ scaling on-call without dedicated headcount
- · Companies with infra ownership unclear post-acquisition
Not a fit
- · Open-ended T&M support contracts
- · Body-shopping for L1 ticket triage
Sample engagement
Onboarding: 2 weeks. Steady state: monthly retainer covering on-call rotation share, weekly incident-review meeting, runbook maintenance, quarterly platform-health report. 90-day notice on either side.
Production outcomes
Tell us what you're building.
Send a project brief and we'll reply within one business day, or book a 30-minute intro call directly.
Thanks, got it.
We'll reply within one business day at the email you provided. A real person reads every message; no auto-responders.