Most Salesforce backups give you a confirmation email.
Org Health gives you a receipt.
Captured count vs. your org’s own count, per object, every run. If anything was silently dropped, you find out the next day — not six months later. Plus per-field schema-decay analytics that turn cleanup into a measurable trend.
Open-source engine. Your data stays in your AWS account. Optional managed pipeline coming.
Why this is different
Backup vendors compete on coverage. Org Health competes on proof.
Every backup tool can copy your data. What most of them can’t do is prove it — or use what they captured to tell you something useful about your org.
Receipts, not promises
Every run records the captured count side-by-side with your org's own COUNT(), per object. If a flow ran amok overnight or an integration silently dropped writes, you find out the next day — not six months later.
Find your dead fields
Per-field fill-rate + last-touched date + days-dormant flags across every object. Zero-fill and near-zero-fill columns get tagged automatically. Hand the deprecation-candidates CSV to your admin and watch the org get tighter month-over-month.
Open source — read the engine
The extractor is a node CLI you can read, audit, and run yourself. No vendor lock-in, no opaque binaries, no “trust us, we backed up your data”. Same posture as Delivery Hub itself.
30-second diff
“Someone says Default Fees went weird on the 14th.” Pull two snapshots, run the built-in diff, and the change set is in front of you in half a minute. No support ticket. No timeline reconstruction.
Every single run
Four artifacts. One folder. Open formats.
You get a flat directory you can open in any file browser. JSON you can grep, CSV you can hand to an admin, reports you can read. No proprietary archive, no opaque blob, no console to sign into.
Full data export
One JSON file per object — every record, every field, ready to query or restore.
Integrity report
Captured count vs the org's own COUNT(), per object. The receipt that proves nothing was silently dropped on this run.
Utilization report
Per-field fill-rate + last-touched + days-dormant + automatic ZERO-FILL / NEAR-ZERO / STALE flags.
Deprecation candidates
CSV of fields safe to retire. Hand it to an admin, watch the schema get cleaner.
Snapshots over time
Where the real story is.
One backup is a safety net. A history of them is a tool — for cleanup, for forensics, for trust with leadership.
Diff between any two snapshots
Which records appeared, which disappeared, which fields changed — answered in seconds, not days.
Change attribution
Grouped by user, by date, by object. “Who edited what, when” becomes a folder lookup.
Schema decay over time
Watch your dead-field count drop month-over-month. Proof to leadership that the org is actually getting cleaned up.
Daily-verified integrity history
An audit-grade record of every run going back as long as you keep snapshots. A real differentiator vs. “just trust us.”
How it’s offered
Use it yourself. Or let us run it.
The engine is open source either way. Pick the level of ceremony that fits your team.
DIY
Available today- ✓Run the open-source CLI on your own schedule
- ✓Point at your own S3 bucket
- ✓Full integrity + utilization + deprecation outputs
- ✓Use the in-browser Explorer to read your snapshots
Managed
Early access- ✓We run the pipeline daily on your behalf
- ✓Hosted retention + automatic snapshot accumulation
- ✓Monthly schema-decay report sent to you
- ✓Integrity alert when a run finds anything anomalous
Enterprise
Annual- ✓Multi-org under one console
- ✓RBAC + audit trail
- ✓Long-term retention with compliance SLA
- ✓Compliance reporting deliverables
Inside Delivery Hub
An “Org Health” tab without leaving your org.
Delivery Hub will surface the latest receipts + decay trends right where your admin already is — integrity verified today, top deprecation candidates this week, schema getting tighter month-over-month. The pipeline runs outside (it has to); the tab reads the result. Same engine, customer-facing surface inside the platform you already use.
In-org tab in design. Today, use the Explorer + the OSS CLI.
Get started
Backups that come with receipts.
Run the open-source engine today. Join the waitlist for the managed pipeline. Read the code, audit the engine, keep your data in your account.