Introducing Obsidian Pulse

The question comes up regularly: who changed that, and can we get it back?

Tape has some built-in history, but there is no native way to roll back a field update in one action, and once a record is deleted it is gone unless you act quickly. For organisations running real business data through Tape, that gap matters.

Obsidian Pulse is a purpose-built tool that fills it.

What it does

Obsidian Pulse connects to your Tape organisation via webhooks and keeps a running audit trail of everything that happens — every create, update, and delete, in real time.

From the audit interface you can:

• Browse the full event timeline — filtered by event type, date, application, or user
• Inspect field-level changes — diffs are pulled live from Tape’s own revision API, so you are always seeing Tape’s source of truth rather than something computed on our side
• Roll back an update — applies the previous field values back to the record via the Tape API in one action, excluding calculated and read-only fields automatically
• Restore a deleted record — Obsidian Pulse first attempts native Tape recovery, then falls back to its own encrypted snapshot if Tape’s window has passed

How record recovery works

When you trigger a restore, the system tries Tape’s own record recovery first. If that succeeds, nothing from our side is needed. If Tape can no longer recover the record, the system falls back to a point-in-time snapshot captured at the point of deletion — but only if delete retention was enabled during setup.

In practice this means recovery is often possible even without the snapshot option, because Tape’s own window covers most same-day deletions.

A few design decisions worth noting

Raw payloads, not computed diffs. The webhook payload from Tape is stored as-is. Field-level diffs are fetched from Tape’s revision API at the point you view them — there is no derived data stored on our side that could go stale.

Encrypted at rest. Deleted record payloads are encrypted with AES-GCM before storage. Each organisation’s data is isolated and only decryptable by that organisation.

Invite-only for now. Onboarding is manual while the system is being bedded in. If it sounds useful for your organisation, get in touch via obsidian-pulse.jmc.tools.