Rotaweek

Pre-launch: not built yet, gathering interest

Fair on-call rotas and weekly handoffs, right in Slack.

A small, flat-priced tool for 5 to 50 person engineering teams running Grafana or Alertmanager. It covers who's on call, fair rotations, and a handoff summary of the week's alerts. It works alongside your existing paging tool, not instead of it.

Join the waitlist Read the FAQ

Companion first: keep PagerDuty, Opsgenie, Grafana IRM or whatever pages you today. Rotaweek adds rotas, fairness and handoffs on top, with a path to replace your scheduling tool later if it earns that.

Aimed at teams moving off Grafana OnCall OSS, which Grafana Labs archived in March 2026, or outgrowing per-seat pricing.

# on-call Illustrative mockup, sample data

RotaweekMon 09:00

Weekly handoff: Priya → Sam. Sam is on call until Mon 09:00 next week; backup is Lee.

Alerts fired
23 (4 after hours)
Still firing
2 open
Noisiest rule
DiskWillFillIn4h
  • Open: KafkaConsumerLag on orders (firing since Fri, ticket linked)
  • Watch: cert on api-gw expires in 9 days
  • Priya's note: “Flapping disk alert on db-2 is known, silenced until Wed.”
Weekly workload After-hours interruptions · illustrative sample data
  • Alex3
  • Sam0
  • Jordan1
  • Taylor0

Alex handled 3 of 4 overnight interruptions. Consider redistributing coverage.

What it's for

The parts of on-call small teams actually use

Most small teams use schedules, a Slack ping, and some notes at shift change. Rotaweek is planned around exactly that.

Rotas that stay fair

Weekly or custom rotations with swaps and overrides from Slack. It tracks weekends and holidays so the load evens out over time, without spreadsheet offsets.

Handoffs written for you

A summary built from the week's Alertmanager or Grafana alerts: what fired, what's still open, what to watch. The outgoing person adds a note, and nothing gets lost at shift change.

One flat price

No per-seat maths when you add the sixth engineer. Slack-native, with Grafana and Alertmanager webhooks as first-class inputs. It doesn't try to be a paging service.

Pricing preview

Flat per team, not per person

Planned pricing for launch. Joining the waitlist costs nothing and commits you to nothing.

Small team

$29 / month

Up to 15 people

  • Rotas, swaps and overrides
  • Weekly handoff summaries
  • Grafana and Alertmanager webhooks

Growing team

$59 / month

Up to 50 people

  • Everything in Small team
  • Multiple rotas (e.g. per service)
  • Primary and secondary schedules

Prices in USD and subject to change before launch. Phone/SMS paging isn't included at any tier; keep your current paging vendor for that.

FAQ

Questions you'd probably ask

Does it page my phone?

No, on purpose. Rotaweek would notify the on-call person in Slack (DM plus channel) and escalate to the backup in Slack if nobody acknowledges. Reliable phone and SMS paging is a hard problem that dedicated vendors already solve well.

If you need phone paging, keep a paging tool (PagerDuty or similar) for critical alerts. Rotaweek is designed to work alongside it for rotas, fairness and handoffs; you don't have to switch anything to try it.

Can I self-host?

Not at launch. The first version would be hosted, so it can stay cheap and simple. Self-hosting is a real open question, especially for teams leaving Grafana OnCall OSS. If you'd need it, say so in the form below; that answer will shape the roadmap.

What data do you store?

Today (waitlist only): what you submit in the form (email, team size, current tool, biggest frustration, whether you're open to a feedback call, and any comments), plus the campaign tags (utm_source, utm_medium, utm_campaign) and referring page you arrived from, and the time you signed up. No cookies or ad trackers. Full details in the privacy note. Your email is used only to contact you about Rotaweek, and you can ask for it to be deleted at any time.

The planned product: your rota (Slack user IDs, names, schedules, swaps), handoff notes, and alert metadata from your webhooks (alert name, labels, status, timestamps), kept for a limited window to build summaries. No phone numbers, no metrics or logs, no source code.

Is this a Grafana OnCall replacement?

For the schedule and Slack parts, that's the goal. Grafana Labs put Grafana OnCall OSS into maintenance mode in March 2025 and archived it on March 24, 2026. The repository is now read-only, and the Cloud Connection features (SMS, phone and mobile push) stopped working. Grafana now points users to Grafana Cloud IRM.

Rotaweek isn't affiliated with Grafana Labs, and it won't replace OnCall's phone paging. The plan is to start as a companion to whatever pages you today, with a path to replace the scheduling side later.

When will it be ready?

It isn't built yet. This page exists to find out whether enough teams want it. If they do, waitlist members get early access first, and probably a say in what gets built first.

Privacy

What this page collects

When you join the waitlist, these fields are stored:

  • Your email address
  • Team size and current on-call tool (and the tool name, if you pick “Other”)
  • Your biggest on-call frustration
  • Whether you're open to a 15-minute feedback call
  • Any comments you add
  • Campaign tags from the link you followed (utm_source, utm_medium, utm_campaign) and the referring page your browser reports
  • The time you signed up, plus a coarse country derived by Cloudflare. Your IP address isn't stored; a short-lived salted hash of it is used only for rate limiting.

This page uses Cloudflare Web Analytics, which is cookieless and collects no personal data, to count page views and referrers. No cookies, ad trackers or third-party fonts. Your theme choice is saved only in your own browser.

Data is used only to contact you about Rotaweek and to decide what to build. It isn't sold or shared. To have your data deleted, reply to any Rotaweek email or write to oncall@rotaweek.com.