Records
Standard and custom objects, discovered from your organisation rather than assumed, with field-level access respected and anything skipped recorded.
Salesforce backup, archiving and recovery readiness
Know exactly what is protected, and what is not.
RASP Vault brings Salesforce records, files, attachments and metadata into one protection model — with evidence for every job, execution that respects your API limits, and storage that stays private.
In active development — early access is open for Salesforce teams.
What RASP Vault protects
One protection model for the whole organisation.
Partial coverage is the most common reason a Salesforce recovery goes wrong. RASP Vault is designed to close the gaps that are easy to miss.
Files and attachments
Salesforce Files and legacy Attachments are captured with their relationships intact, checksummed on the way in, and stored outside the web root.
Metadata
Objects, fields, Apex, flows, layouts and permission sets, retrieved through supported Salesforce APIs, with unsupported components reported honestly.
Incremental change
Inserts, updates and deletions after the first full backup, using the safest strategy each object actually supports.
Selective backup
A single record, a record and its children, chosen objects, or a filtered subset — without writing a line of SOQL.
Archive readiness
Identify records eligible for archiving, confirm a verified backup exists first, and keep an immutable record of every approval.
Operational confidence
Evidence for every job, not just a green tick.
A backup marked “completed” means little on its own. RASP Vault is designed so you can answer the harder questions afterwards.
- Per-object record counts, checksums and byte totals
- Fields and objects that were skipped, and exactly why
- API calls consumed, broken down by category
- Deletion tombstones kept alongside the records
- Jobs that pause safely and resume from their last checkpoint
- An immutable audit trail of who changed what
How it works
Connect, define, and let it run within your limits.
Three steps to a protected organisation, with nothing hidden along the way.
01
Connect your organisation
Authorise through the Salesforce OAuth web server flow. Tokens are encrypted at rest and never reach the browser. Connect production and sandbox organisations side by side.
02
Define what to protect
Choose whole organisations, selected objects, or a filtered subset. Add files, attachments and metadata. Set the share of your daily API allocation that backups may use.
03
Run and verify
Run on demand or on a schedule. Watch progress live, review what was captured and skipped, and download the manifest for any snapshot.
Early access
Help shape a more responsible Salesforce backup platform.
We are working with Salesforce teams who care about coverage, evidence and operational safety. Tell us about your organisation and how you need recovery to work.