For DevOps / SRE · 8 Grok Bots

An on-call back office that captures every incident and keeps your runbooks honest

8 Grok Bots for a DevOps/SRE who carries the pager: capture the incident timeline, match the runbook, draft the postmortem, tame alert noise, hand off on-call, and track the error budget — all as drafts you approve. Nothing deploys, files, or sends on its own.

Hire the team See the bots
● Drafts only — nothing sends without your approval · Uses only your own data
After checkout
Your setup link arrives by email
We set up your fleet
After checkout, Workplace AI provisions your fleet on our Cursor Teams workspace and follows up soon. Watch for your Cursor invite and Grok Bot download link — then accept, install, and go.
8 bots·3 domain specialists·Success metric: Incident-record completeness and runbook freshness·Category: Corporate roles
The problem it targets

Carrying the pager between deploys — reconstructing an incident timeline from scattered alerts and chat, hunting for the right runbook mid-page, updating runbooks that drifted from reality, writing postmortems and chasing their action items, piecing the on-call handoff together from memory, and re-deriving each service's SLO and error budget by hand — so incidents run longer than they should, runbooks rot, postmortems slip, and the reliability picture is a guess.

What you get

From day one

1

Every incident timeline reconstructed from your alerts and chat, and each service's matching runbook found and drafted current — with each change flagged against what actually happened.

2

A blameless postmortem drafted while the detail is fresh — contributing factors, timeline, and proposed action items — plus an alert-noise analysis naming your least-actionable pages.

3

A clean on-call handoff note at shift change and a weekly SLO and error-budget report per service, every number traceable to its metric.

Meet the team

8 bots, each with one job and clear approval points

Read-only bots watch and prepare; drafting bots write but never send. You approve everything that leaves.

1

Chief of Staff

coach
Drafts for your review — you approve before anything leaves
Your morning brief, meeting prep, fleet roundup, and after-meeting coaching.
Approves: none — nothing leaves without you
2

Incident Timeline Scribe

intake
read-only
Watches & prepares — never sends
Reconstructing the incident timeline from alerts and chat, each entry sourced
Approves: none (nothing leaves; the record is internal)
3

Alert Noise Analyst

researcher
read-only
Watches & prepares — never sends
Alert-noise analysis and a proposed tuning diff for the engineer to apply
Approves: none (nothing changes; the diff is a proposal)
4

Runbook Drafter

drafter
specialist
Drafts for your review — you approve before anything leaves
Drafted runbook updates matched to the incident, changed steps flagged
Approves: every runbook change before it replaces the live one
5

Postmortem Writer

drafter
specialist
Drafts for your review — you approve before anything leaves
Blameless postmortem drafts with proposed action items and owners
Approves: every postmortem before it is filed; owner assignment
6

On-Call Handoff Coordinator

coordinator
Drafts for your review — you approve before anything leaves
Drafted handoff notes and the next-on-call message
Approves: every message before it is sent
7

SLO & Error-Budget Reporter

reporter
read-only
Watches & prepares — never sends
Weekly SLO and error-budget report, every number traced to its metric
Approves: none (nothing leaves; the engineer decides)
8

Social & Referrals

growth
Drafts for your review — you approve before anything leaves
First-party, disclosed reliability write-ups and referral notes to the engineer's own opted-in network
Approves: every post before it is published
The handoff — one shared chat
Scribe→Analyst→Drafter→Writer→Coordinator→Reporter
What the fleet does in week one

All read-and-prepare — you check its work before anything is trusted

What it does not do

The guardrails are the product

  • ×It drafts; it does not act. Every runbook change, postmortem, and handoff message waits for you.
  • ×It never runs a deploy, rollback, config change, or feature-flag flip, and it never applies an alert-config change — it hands you the change and you run it.
  • ×It keeps every postmortem blameless and proposes action-item owners; it never assigns blame or an owner on its own, and it never reports an SLO number it cannot trace to its metric.
Incident-record
completeness and runbook freshness
How you'll know it's working

One number, measured over time

Share of incidents that close with a captured timeline, a linked runbook, and a drafted postmortem, and how current the runbooks are against the last incident that touched them

Before day one

What you fill in — the bots never guess these

incident-log
the header contract for the incident log every bot reads.
runbook
the runbook layout your wiki uses.
slo-definitions
your services, their SLO targets, and windows. SLO math comes only from here.
Pricing

Cancel anytime.

Workplace AI provisions and runs your CrokPot fleet on our Cursor Teams workspace. We invite you on your own email — you accept, install Grok Bot, and we handle the rest.
$200/mo
  • Your whole fleet provisioned and installed for you
  • Cursor Teams seat included — paid by Workplace AI, never billed by Cursor
  • Onboarding + ongoing training
Hire the team
Your Cursor Teams seat is included and paid by Workplace AI. Drafts only, using your own data. No earnings, time-saved, or outcome guarantees are made.
How access works

You buy a CrokPot fleet from Workplace AI — not a Cursor plan

CrokPot runs on Workplace AI, Inc.’s (WAI) Cursor Teams workspace. WAI keeps the unpaid admin seat and pays Cursor for your seat. You join as the invited user on your real email and work through the installed Grok Bot fleet.

Your card is charged by WAI via Stripe for the CrokPot fleet ($200/mo, auto-renewing monthly) only — never by Cursor. If you cancel your fleet subscription, the invite/seat ends with it and is not portable to your own Cursor account.

FAQ

What you get, who owns the seat, and what happens after you pay

From the team behind Ancestry — CrokPot is built by Paul Allen, a co-founder of Ancestry.com.

Drafts only — you approve everythingYour own data, never shared$200/mo · cancel anytimeProvisioned & supported by Workplace AI

What do I actually get?

A pre-built fleet of Grok Bots for your trade, provisioned and installed for you on Workplace AI’s Cursor Teams workspace, plus onboarding and ongoing training. Every bot drafts; you approve.

Who owns the seat?

Workplace AI, Inc. (WAI) owns the Cursor Teams account and pays Cursor for your seat. You’re invited as a paid user on your own email. The seat isn’t portable to a personal Cursor account.

Do the bots act on their own?

No. The fleet is drafts-only, working from your own data. Nothing sends, files, or is trusted until you review and approve it — that’s the whole design.

Can I cancel?

Yes, anytime. It’s an auto-renewing monthly subscription at $200/mo. If you cancel, your invite/seat ends with the subscription.

What happens after I pay?

We follow up soon: our team provisions your fleet and invites you on the email you used at checkout. Watch for your Cursor Teams invite and Grok Bot download link, then accept, install, and go.

Training

New to Grok Bots? Get your team trained.

Live sessions and replays to get you and your coworkers productive with your fleet fast.

Explore Grok Bot training