Your bucket, your rules
Any S3-compatible endpoint, with path-style addressing for the stores that need it. The evidence lives under retention, versioning and access control you set.
Evidence export
Keep the evidence in storage you control
Send every artifact and its manifest to your own S3-compatible bucket as audits complete. The copy in your storage verifies exactly as ours does, so custody moves without the proof weakening.
Create a free accountRead the API docs
- Any S3-compatible store
- Written with its SHA-256
- Credentials sealed
- Included on every plan
Destinations3://acme-evidence/auditwolf/
aw-2841/screenshot.pngsha256 8a13c0...aw-2841/page.htmlsha256 4f287b...aw-2841/signature.binsha256 d2f51d...aw-2841/audit.jsonmanifest
Verifies from your bucket, without us.
Custody
Evidence held only by the party that produced it
A record that exists solely in a supplier system is worth less than one you hold, and it disappears on the day you stop paying, the day the retention period ends, or the day the supplier does. That is an uncomfortable dependency for anything you might need years later.
Export puts the primary copy in your own storage, under your lifecycle and access rules. Because the proof travels with the bytes, the copy you hold verifies on its own: the hashes, the Merkle path, the signature and the timestamp are all in the bundle.
POST /auditwolf/v1/export-destinations
Authorization: Bearer ...
{
"endpoint": "https://s3.eu-west-2.amazonaws.com",
"bucket": "acme-evidence",
"prefix": "auditwolf/",
"path_style": false,
"access_key_id": "AKIA...",
"secret_access_key": "..."
}
POST /auditwolf/v1/export-destinations/{id}/testCapabilities
What lands in your bucket
The artifacts, the manifest, and the integrity data that lets the copy stand on its own.
Credentials sealed
Access keys are sealed in a vault at rest, opened only to run an export you configured, and never returned by the API once stored.
Written with its hash
Every object carries its SHA-256, and the ETag your storage returns is recorded against the export, so the copy can be reconciled with what was sent.
The manifest travels too
An audit.json goes with the artifacts, so the export is a self-describing record rather than a folder of files with opaque names.
Verifies on its own
A bundle from your bucket passes the public verifier exactly as the original does. Custody moves; the proof does not weaken.
Tested before it matters
Testing a destination writes one small object to a reserved path, so a wrong key surfaces then rather than when an audit completes.
Use cases
Why teams take custody
Usually a policy, sometimes a retention period, occasionally a lesson from last time.
Evidence that outlives the plan
Keep records beyond your hosted retention period, in storage you control.
Regulated custody requirements
Satisfy a policy that says the primary copy of a record cannot sit with a supplier.
Your own retention rules
Apply the object lifecycle, versioning and locking your storage already offers.
Feeding an internal archive
Land evidence where the rest of your compliance record already lives.
Exit without loss
Leaving with everything is a configuration setting, not a support request.
Separation of duties
The party producing the evidence is not the only party holding it.
Retention now deletes. Export is how evidence survives it.
Hosted evidence is kept for the period your plan includes and then deleted, leaving a record that names what was observed but can no longer verify it. If a bundle has to outlive that period, it needs to be in your storage before it expires. The evidence.expiring webhook fires when hosted evidence is close to expiry and no export holds a copy.
Pricing
Export is included on every plan
There is no export charge and no add-on tier. You pay your own storage provider for what you keep, and Auditwolf for the pages you capture. Evidence integrity is identical on the free plan and every paid one.
Questions
Before you integrate
The details that decide whether this fits, without reading the whole reference first.
What gets written to my bucket?
Every artifact from the audit, plus an audit.json manifest, under a prefix you choose. Each object is written with its SHA-256, and the ETag your storage returns is recorded against the export.
Does it work with storage that is not AWS?
Yes. Any S3-compatible endpoint, with path-style addressing supported for the stores that need it, so MinIO, Backblaze B2, Cloudflare R2 and similar are all reachable.
How are my credentials handled?
Sealed in a vault at rest and opened only to run an export you configured. They are never returned by the API once stored.
Can I check a destination before I depend on it?
Yes. Testing a destination writes one small object to a reserved path and reports what happened, so a wrong key or a missing permission surfaces immediately rather than the first time an audit completes.
Does an exported copy still verify?
Yes, and that is the point. The bundle in your bucket verifies exactly as the original does: the hashes, the Merkle path, the signature and the timestamp are all in what you hold.
What happens when my hosted retention runs out?
The hosted copy is deleted and a record of the audit remains, naming what was observed but no longer able to verify it. An export is how a bundle outlives your plan retention, and the evidence.expiring webhook warns you when hosted evidence is about to expire and no export holds a copy.
Is there a charge for exporting?
No. Export is included on every plan; you pay your own storage provider for what you keep. You are charged by Auditwolf for the pages you capture.
Point it at your bucket
Create an account, add a destination and test it. The first export runs when your next audit completes.
Export is included on every plan, with no per-object charge and no card required to start.