How to build an emergency infrastructure binder

Create an account, verify email, start a trial, and create a blank workspace for the real company or client.

Add the first asset, backup, credential reference, runbook, vendor contact, and note. Then generate a Markdown or JSON emergency export.

Assets, network devices, switch ports, firewall references, physical locations/racks, domains, manually entered SSL dates, backups, restore tests, runbooks, vendors, contacts, credential references, renewals, notes, and evidence.

Use notes for details that belong to a specific record: replacement history, vendor portal references, restore-test screenshots, rack access notes, and handoff warnings.

The takeover package summarizes critical assets, owner contacts, credential references, vendor contacts, backups, restore evidence, domains/DNS/SSL records, runbooks, and post-takeover checklist items.

It excludes raw passwords, API keys, private keys, recovery codes, TOTP seeds, and secret values.

Do not store credentials in InfraBinder. Store where authorized users can find them, such as 1Password, Bitwarden, Keeper, or another external vault.

Record the vault provider, vault name, item/path/reference, owner, MFA/recovery reference, approval contact, and whether rotation is required after takeover.

Markdown export is useful for an offline handoff packet. JSON export is useful for review, backup, or later import tooling.

Exports include notes and evidence references, and can include archived records only when explicitly requested.

Reminder emails are based only on dates users enter into the binder.

Examples: domain renewal date, manually entered SSL expiry date, warranty/support expiry, restore-test review date, and runbook review date.

Business Owners control membership and takeover access. Technical Admins can maintain documentation but cannot remove the protected Business Owner by default. Viewer/Auditor is read-only.

Sensitive changes are audited, version history is retained, critical records use soft archive/restore behavior, and customer data is tenant-scoped.