Building safety & compliance
VaultSync
Versioned compliance documents that stay consistent offline
A compliance-document platform with versioned storage, controlled access and audit trails, usable from a site with no signal, without producing conflicting copies.
This example comes from the technical delivery experience behind AussieSync. It does not necessarily represent a project contracted directly through AussieSync.
Have a process like this one? Tell us about it.
01 Problem
Regulated documentation has to be versioned, access-controlled and auditable, while being edited from sites with no connectivity.
- Field staff worked from local copies, and two people editing produced two truths.
- Nobody could show which version was current at the time of an inspection.
- Documents were scattered, so finding the right certificate meant asking someone.
- An audit needs the history, not just the file as it stands today.
02 The solution
Object storage behind a metadata index, with a versioned sync protocol and conflict handling.
- Files live in object storage; a metadata layer makes them searchable and permissioned.
- Every change creates a version, so the state at any past date is recoverable.
- A versioned sync protocol reconciles offline edits rather than overwriting them.
- Role-based access controls who can read or change each class of document.
- Access and modification are recorded for audit.
03 Technical approach
Every choice earns its place.
- AWS S3Durable object storage for the documents themselves.
- PostgreSQLMetadata, permissions and version history.
- ElasticSearchSearch across documents and their metadata.
- Versioned sync protocolReconciles offline edits without silent overwrites.
04 Outcome
Compliance-ready records, with no lost or conflicting files across devices.
- Compliance-readyrecords with full version history
- No conflictsacross offline edits and devices
- Searchableinstead of scattered across shared drives