Scheduled rollouts Widen it on a timetable.
Plan a rollout once and let Plinth carry it out: a few percent on Monday, a quarter on Wednesday, everyone on Friday. If a guardrail trips along the way, it holds and tells you.
How it works
-
Set the steps
Choose the percentages and how long to wait between them, or start from a template.
-
Add guardrails
Pick the metrics that should stop the rollout, such as error rate or p95 latency, from your monitoring tool.
-
Let it run
Plinth widens on schedule, pauses on its own when a guardrail trips, and posts every step to Slack.
The details
- Automatic pause
- A tripped guardrail holds the rollout at its current step until someone looks.
- Business hours only
- Keep steps inside working hours in your time zone, so nobody is woken by a widening rollout.
- Full history
- Every step, pause and resume is recorded with who did it and why.
await plinth.rollout('checkout-v2', {
steps: [1, 5, 25, 50, 100],
every: '1d',
pauseIf: { errorRate: '> 1%' },
});More of the platform
-
Feature flags
Put every change behind a flag and decide who sees it, without a deploy.
Learn more: Feature flags -
Experiments
Split traffic between variants and get a clear result, with the statistics done for you.
Learn more: Experiments -
Product analytics
Funnels, retention and cohorts, with every release marked on the chart.
Learn more: Product analytics
Try Scheduled rollouts today
Free for small teams. Set up in minutes.