Fractal Secrets
A secrets manager built for AI agents. Your API keys and passwords stay on your own server, and the AI never sees them. When an agent needs one, Fractal makes the call for it and hands back only the answer.
You’ll join the Echofold newsletter, where Fractal invite codes will go out. Have a code already? Sign up with it.
Keys your agents can use but never see
The point
AI never sees your secrets.
Your agents work in a sandbox on your server, and your keys are kept outside it. An agent can ask Fractal to use a key, and gets the answer back. The key itself never goes in.
Your agent · inside its sandbox
List the files in the backups bucket, with the key called backups.
42 files. The newest is from 02:00 this morning.
It names the key. It never holds it, so it can’t end up in your code, a commit or a chat.
Fractal Secrets · outside the sandbox
- 2Checks your rule: this project may list and read the backups bucket.
- 3Adds the key and makes the call itself, to the address you fixed when you added it.
- 4Scans the reply for your secrets, writes the use down, and passes on the answer alone.
Your cloud storage
It gets an ordinary signed request from Fractal, and answers it.
Step by step
One key, from the day you add it.
The same example all the way through: the key to your backups.
Add a key. Paste the key into Secrets and give it a name, like backups. That is the last time anyone sees it: once saved, a value is never shown, copied or filled in again, to you or to an agent. It can only be replaced or removed.
What it takes off you.
No keys pasted into prompts, no keys in the code, nothing to remember to rotate by hand. Most important first.
01AI never sees your secrets.
- Your keys are kept on your own encrypted server, outside the sandbox your agents work in.
- Agents ask for an action, like listing the files in a bucket. Fractal adds the key and makes the call itself.
- Every reply is checked for your secrets before an agent sees a word of it.
02You stay in control.
- Access is set project by project and action by action, so a key allowed in one project does nothing in another.
- Mark a key as approve-each-time. Anything left unanswered is refused, so nothing hangs for hours.
- Swap a key and its permissions carry over. Revoke it and everything that used it stops on the next call.
03Nothing to leak by accident.
- No keys pasted into prompts, and none in your code or your commits.
- Once saved, a value is never shown, copied or filled in again. It can only be replaced or revoked.
- Every use and every refusal goes into a chained log, where an edited line shows up as a break.
Where it stands
Private beta, and what that means.
Worth knowing before you join the waitlist.
Add keys in Secrets, not in a chat.
A key you paste into a conversation with an agent has been seen by that agent. A key you add in Secrets never is.
Not a browser password manager.
It's built for your projects and agents: saved values can't be revealed, copied or filled into websites.
Tamper-evident, not tamper-proof.
The log shows where a line was changed. It can't stop someone with access to the file from rewriting everything after it.
Get an invite to Fractal.
Fractal is invite-only for now. Join the waitlist and you’ll be added to the Echofold newsletter, where invite codes will go out to everyone.
Have a code? Sign up with it. Already in the beta? Sign in.