Storage
Storage connectors: platform storage and your own bucket
Generated bytes land either in Wakemark's platform storage or in your own S3-compatible bucket. The custody record is identical in both cases; what changes is who holds the bytes, who can delete them, and what Wakemark is able to promise about them.
Two destinations, one driver
There is a single S3-compatible driver and no per-vendor adapters. Vendors differ only as data in a registry: an endpoint template, region semantics, a few quirk flags, a copy-paste least-privilege policy, and the date a real end-to-end run last passed against that vendor. A vendor appears as verified because a live test wrote, read and deleted an object there — not because the protocol ought to work.
Connecting a bucket requires the same envelope vault that seals provider keys: the bucket credentials are sealed the same way, bound the same way, and are as opaque to the database as any other secret. You can test a connection without a vault; you cannot save one.
What changes when the bytes are yours
| Platform storage | Your own bucket | |
|---|---|---|
| Who holds the bytes | Wakemark | You |
| Byte-exact write + SHA-256 in the ledger | Yes | Yes |
| Provenance sidecar written beside the asset | Yes | Yes |
| Reads | Served by Wakemark | Presigned against your bucket, or proxied through an authenticated path |
| Metered for storage | Yes | Never — Wakemark does not meter bytes it does not hold |
| Deleted when a retention deadline passes | Yes | Yes, while the connection works — and loudly if it does not |
| Deleted on account deletion | Yes | No. Your bucket is never touched; Wakemark deletes its access and its records |
The failure posture
A connection to somebody else's bucket can break in ways platform storage cannot: a rotated key, a revoked permission, a bucket that was deleted. Wakemark's rule is that such a failure is always visible. A write that could not complete surfaces on the asset with an explanation, and where the provider's own URL is still valid it is preserved so the bytes can be rescued.
The same honesty applies to what Wakemark counts. If a bucket has been concluded unreachable, bytes in it stop counting as bytes Wakemark holds — a report about what can and cannot be attested should say so rather than quietly include them.
Check this yourself
Nothing on this page should have to be taken on our word. Each of these settles part of it, and none of them requires trusting the sentence above it.
- Security & Trust — bucket credentials sealed by the same envelope vault as provider keys.
- Privacy Policy, account deletion — the boundary in the legal surface's own words: offboarding removes Wakemark's access and records, not your objects.
- Custody — the sidecar written beside each object — in your own bucket you can open it yourself and compare it to the API's copy.