Uptime — SLOs, Error Budgets & Burn Rate

Uptime — SLOs, Error Budgets & Burn Rate — 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 reliability targets — what a target actually permits, how much is spent, how fast, and the day it runs out. 33 tools in one, and it never shows you a negative budget remaining.

33 built-in tools in one app. A service register and an SLO register carrying target, window and basis; a NINES view expressing a target as permitted downtime per day, week, month, quarter and year; the error budget a target and window produce — a 30-day window is 43,200 minutes, so 99.9% permits 43.2 of them; consumed from your recorded incidents and indicators, remaining FLOORED AT ZERO with any overage stated separately, and a BURN RATE measured against ELAPSED time rather than against the whole window, because 22 minutes of a 43.2-minute budget is 50.925926% spent but only 20% elapsed at day 6, which is a burn of 2.546296x and an exhaustion date of day 11.781818; multi-window burn alert thresholds and a check of which would be firing right now; good events against total events, an event-based SLI kept SEPARATE from the minute-based one and each labelled, and a latency SLO as a percentile promise; incidents with a PARTIAL view prorating an incident affecting a share of traffic — 40 minutes at 25% consumes 10 minutes, not 40 — downtime by service and month, MTTR with the count it is drawn from, frequency, and your error-budget policy; a dependency graph and a DEPENDENCY MATH view showing that three services at 99.9% in series give 99.700300%, lower than every member; plus a what-if, CSV exports, a JSON backup and a Method page.

Nines. 43,200 minutes in a 30-day window: 99.9% permits 43.2 of them.

Basis. 1,450 bad of 1,000,000 is 99.855% and fails 99.9% with no full minute down.

What's included:

• Uptime.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.

Uptime 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.