Share your team's keys and skills, without sharing your keys.

One vault holds every secret, one registry holds every skill. Your Claude Code, your teammates, and your agents call through a token you can revoke. No key is copied to a laptop or a repo, and there's one library to maintain, not one per person.

keys copied everywhereeveryone maintains their ownskills need creds

Read the docs →

Try it live, no signup: 1 keys stay in the vault → 2 point at an API or a skill → 3 call it with just a token

🔒 Vault {{s.name}}••••••

treg holds these · referenced by name · never downloaded to a machine

{{demo.view==='endpoints'?'One API URL, called with a token. treg injects the key.':'A whole capability your agent loads. Some need a key, some are just know-how.'}}

Three ways a key leaks. treg closes all three.

The same secret, needed in more and more places - and every place is a copy that can leak.

Key sprawl

The same key pasted into every project, .env, and machine. One leak exposes them all.

treg → one vault. The key is injected at call time and lives nowhere else.

Team access

Give a teammate access and they hold your key - forever, everywhere they go.

treg → they get a token, not the key. Revoke it and they're out.

Agent skills

A skill needs credentials to run. Sharing the skill shouldn't mean shipping the secret.

treg → the skill calls through the vault. Your agent runs it and never sees the key.