A zero-dependency, offline-first business continuity & disaster-recovery planner. One HTML file. No server. No accounts. Inventory the tech your business runs on (and its backup state), map dependencies, walk tabletop exercises, and export a recovery plan.
.pumapack. The safeguard against losing browser storage. Restore brings every plan back as a fresh workspace.See the Keyboard tab for shortcuts.
Business continuity management is a loop, not a document. PumaBCP follows the ISO 22301 / NIST SP 800-34 cycle: understand what matters, plan how to keep it running, exercise the plan, and keep it current.
An untested continuity plan is a hypothesis. The plan you've never exercised will surprise you on the worst possible day — exercise it, find the gaps, fix them, repeat.
Everything downstream depends on knowing which functions are critical and how long you can lose them. Rank by impact over time, not by how loud the owner is.
Three numbers anchor every plan. MTD (maximum tolerable downtime) — how long a function can be down before the damage is unacceptable. RTO (recovery time objective) — your target to restore it, inside the MTD. RPO (recovery point objective) — how much recent data you can afford to lose. These are business decisions, not IT defaults.
Map the dependencies. The shared database, the sole vendor, the one person who knows the runbook — recovery stalls at the weakest link, so find it before an incident does.
The standards are ISO 22301 (business continuity management systems) and NIST SP 800-34 (Contingency Planning Guide). Assess the threats feeding your BIA in PumaRisk; run the exercises in PumaTTX.
Every plan, asset, dependency, backup, workflow, scenario, and history snapshot is held in this browser's localStorage under the pumabcp.* key prefix. Nothing is sent over the network. Closing the tab keeps your data; opening this file in a different browser, profile, or device shows an empty plan.
Heads up. Clearing site data, using private/incognito mode, or losing the device erases everything. The browser is the database — back up regularly.
Two export scopes, each with its own home:
.pumapack. This is the safeguard against losing browser storage entirely — closed wrong window, cleared cookies, switched browser, lost device. Restore brings every plan back as a fresh workspace..pumapack (the format for sharing a plan with a client, or opening it in another browser). The Reporting group offers Markdown, RTF (Word/Pages/TextEdit), and PDF (system print dialog) renderings of the recovery plan suitable for leadership.This deletes every plan, score, history snapshot, and preference under pumabcp.* in this browser. It does not touch any .pumapack file you've exported.
Type DELETE EVERYTHING to confirm.
.pumapackPumaBCP is a lightweight, portable, offline business continuity and disaster recovery planning tool that runs entirely in your browser. It covers asset inventory, dependency cascade modeling, guided tabletop exercises, and recovery plan export.
This tool is provided as-is, with no warranties or guarantees. It is not professional advice. By using it you accept full responsibility for any outcomes that result from your use.
PumaWorx is a suite of offline, single-HTML productivity apps that run entirely in your local browser. The entire suite is a personal, open source vibecoding project.
Edit the plan name and the business it's for. Both show up on the dashboard header and in every exported report.
Each plan is a separate workspace — its own assets, dependencies, backups, scenarios, history. Use one per business unit, location, or annual review cycle.
Vendor-managed — the SaaS vendor (Google, Microsoft, Stripe, etc.) backs the data up; you trust their infrastructure.
Self-managed — you run the backup yourself (snapshots, scheduled exports, on-prem tape).
Manual export — someone downloads a copy on a schedule (CSV, JSON, paper).
A backup you've never restored isn't a backup you can trust. A test restore means you actually pulled the backup, brought the data up in a working state, and verified it. Auditors look for this date — leaving it blank is a red flag.
Recovery Time Objective — how quickly this asset needs to be back up after a failure. Document your target, not what's possible today. Example: "4 hours" if the business can tolerate that long without it.
Click to add common business tools. Already-added items are dimmed.
Define a relationship: if the upstream asset fails, the downstream asset is affected.
Pick a pre-built scenario to start a tabletop exercise.
This is an offline single-HTML app. No data goes to or from the internet. There is no server, no account, no sync, and no telemetry.
Your plans live in your web browser's localStorage — on this device, in this browser, and nowhere else.
Your data is YOUR responsibility.
If you clear site data, use a private/incognito window, switch browsers, or lose this device, your plans are gone. Back up regularly via the Export button in the topbar — writes every plan to one .pumapack.
Press ? any time for help and keyboard shortcuts.