If someone questions your work, your history already answers.
TakeProvenance quietly signs your DAW project — and any audio you confirm — every time you save meaningful progress. No cloud, no accounts, nothing sent anywhere: just a tamper-evident record, built on your machine, that you can point to months or years from now.
Three steps, none of them a change to how you already work.
TakeProvenance runs alongside your DAW, not inside it — nothing about your session changes except that its history is now provable.
Track a session
Point TakeProvenance at your project folder. Your files stay exactly where they are — nothing moves, nothing uploads.
Sign a take
Whenever you save real progress, sign it. The project file — and any audio you confirm — gets sealed with a timestamp and your signature.
Show your work
Build an evidence pack any time you need one — a certificate anyone can check, with no install required on their end.
Watch a take get signed, start to finish.
A short walkthrough of opening a session, signing a take, and building an evidence pack from it.
This will show a real session — signing a take, confirming a new bounce, and building an evidence pack from it.
The proof only matters if the process holds up.
Zero network calls
Everything happens on your machine. Nothing is sent anywhere unless you choose to share an evidence pack yourself.
Your key never leaves this computer
Held in macOS Keychain or Windows Credential Manager — never written to disk in plain text, never transmitted.
Verifiable without installing anything
Every evidence pack ships with plain-language instructions anyone can follow with tools they already have.
What stays on your machine, stated plainly.
- Zero network calls, anywhere in the app. Nothing about your sessions, your files, or your signing key is ever sent anywhere.
- Your signing key lives in this computer's secure storage — macOS Keychain or Windows Credential Manager — generated on this machine and never transmitted.
- Your session history lives in a local folder (
~/.provenance) on this computer, not in any account or cloud service. - No analytics, no crash reporting, no telemetry of any kind in this build. We learn about problems only when you tell us.
- The only thing that ever leaves your computer is a file you choose to export or share yourself — an evidence pack, or a key backup you place somewhere on purpose.
What this alpha doesn't do yet.
So a real gap reads as expected, not as something you need to report.
- No background auto-signing yet. Every take is signed by hand, on purpose, for this round.
- The local history store is a single point of loss. If this machine's drive fails without a backup, that project's signed history goes with it — export or back up regularly.
- Logic Pro's project format is a bundle (a folder disguised as a file); changes made deep inside it between saves may not always be caught.
- No cloud sync or multi-person collaboration yet — one signer, one machine, at a time.
- This build is unsigned — see the download section below for what that means the first time you open it.
Try it now — and tell us what breaks.
This is early software, made for a small group of musicians and producers to try before anyone else. Expect rough edges; please report them.
Intel Macs; runs on Apple Silicon via Rosetta 2 (an Apple Silicon–native build is planned). Unsigned alpha build — see the note below before you open it.
Download .pkgWindows 10 and 11, 64-bit. Unsigned alpha build — see the note below before you run it.
Download installer- Opening an unsigned build: neither installer is code-signed yet, so both OSes will warn you before letting it run — that's expected, not a sign anything's wrong. On macOS: right-click the app in Applications, choose Open, then confirm Open again. On Windows: click More info, then Run anyway.
A short list, so your feedback lands somewhere useful.
Start a session — point it at a real (or throwaway) project folder.
Sign a few takes — including one where you've just bounced fresh audio, to see the review step.
Back up your signing key, then try restoring it — the whole point of a backup is that it actually works when you need it.
Build an evidence pack and open the certificate it makes.
Tell us what felt confusing — not just what broke. Alpha feedback on rough edges is exactly as useful as bug reports.