Rollout — Deployment Strategy, Canary & Blast Radius

Rollout — Deployment Strategy, Canary & Blast Radius — a premium, 100% offline digital tool by Aceplore. Runs entirely in your browser: no accounts, no subscriptions, your data never leaves your device.

A private, offline desk for shipping changes — the stage ladder, the users each stage exposes, the blast radius in user-minutes, and whether the canary can actually see a regression. 34 tools in one, and a gate with too little data returns insufficient-data instead of passing.

34 built-in tools in one app. A release register with strategy, a strategies view stating what each implies for exposure and for rollback time, and a stage ladder drawn; exposure per stage from the population you set, a CUMULATIVE view — because a ladder is cumulative and 1/5/25/50/100 never sums to 181% — and a BLAST RADIUS in users and in USER-MINUTES, which is the only figure that compares a 1% stage baked for 12 minutes against a 5% stage baked for 3; cohorts, a ramp chart, a BAKE view giving the time a stage needs to observe an event at your base rate, and a DETECTABILITY view saying plainly when a stage is too small to distinguish a regression from noise — a 1% stage of 240,000 at a 0.4% base rate sees about 9.6 events, and Rollout says so rather than showing a green canary; promotion gates, a gate check returning pass, fail or INSUFFICIENT-DATA and never treating absence of failure as success, a promotion view and a halt view showing what a stop leaves half-deployed; recorded rollbacks, a ROLLBACK TIME view totalling detect plus decide plus revert — 8 + 5 + 4 is 17 minutes, and quoting the revert alone understates exposure fourfold — and a release MTTR; feature flags, a kill-switch view of what can be turned off without a deploy, and a FLAG DEBT view of flags past their cleanup date, which are the next outage; a release calendar with clashes, freeze windows and violations, and a strategy comparison; plus CSV exports, a JSON backup and a Method page.

Cumulative. A 1/5/25/50/100 ladder exposes those percentages, never their sum.

Insufficient data. Absence of failure is not success.

What's included:

• Rollout.html
• Quick-Start-Guide.html
• How-To-Use-Guide.html
• README.txt
• LICENSE.txt

Includes a personalized welcome wizard, an interactive guided tour, a ⌘K command palette, light/dark themes with 8 accents, and one-click JSON backup & restore.

Rollout is a planning, costing and record-keeping tool for software and infrastructure work. Every figure it reports is computed by a stated formula from the numbers YOU enter, and every figure carries its UNIT, because a millisecond, a byte, a request, a vCPU-hour and a user-minute are different quantities and confusing them is the classic failure in this field. Byte and month conventions are settings and are printed beside the figures they produced — 1 KB = 1,000 bytes and 1 KiB = 1,024 bytes are both correct and they disagree. Where something is consumed against an allowance, the consumed amount, the remaining amount floored at zero and the overage are reported separately, because a negative remaining renders as headroom and that is how an outage gets missed. Where a figure rests on an assumption — a hit ratio, a growth rate, a base event rate, an hourly price — it is labelled an assumption at the point of use and is yours to change. It runs entirely in your browser with no network access of any kind: it cannot reach a server, a registry or a cloud account, and it reports only what you recorded. It does not predict an outcome and is not a guarantee of uptime, of a deploy, of a bill, of compliance or of security posture, and nothing in it is legal advice.