Put digital keys and game codes in a vault, then keep distribution accountable.
Vultkey stores license keys, API keys, coupon codes, gift cards, and Steam, Epic, or GOG keys as masked records. You can track what is ready, claimed, used, or archived without turning a spreadsheet into a security problem.
Code vault
A compact preview of the dashboard: search, status filters, and masked code rows.
OpenAI API credits
OpenAI · May 22API credits
Windows 11 Pro license
Microsoft · May 21Licenses
Steam game key
Steam · May 18Game keys
Take keys out of notes.Keep them in a vault.
Vultkey treats keys like inventory. Every record carries its purpose, status, category, and last movement.
Move keys out of scattered notes
Licenses, API keys, coupons, gift cards, and Steam or Epic keys land in one vault.
Keep lists masked by default
Raw values do not float around in the list. Reveal and copy stay as explicit actions.
Keep the last action visible
Ready, claimed, used, and archived records stay in the same operational flow.
Share the key, keep control in the vault.
Open a single-key link or a category list. You decide what the recipient sees, what they must provide, and whether raw access is allowed.
Plain link
Use it when you want to hand off a code quickly without asking the recipient for extra details.
Require email
Ask for recipient information when you need a distribution trail.
Member allowlist
Limit a link to signed-in Vultkey members you selected by email.
Control raw access
Decide whether the recipient may reveal or copy the raw code after claiming it.
One key is fine. A campaign list is fine too.
Add the key, group it, share it, and later see which record went where.
Personal vault
Keep gift cards, coupons, license codes, and subscription keys in one quiet place.
Team distribution
Track who received a license, API credit, access code, or internal key.
Games and communities
Distribute Steam, Epic, beta, and giveaway keys, then archive the finished campaign.
Add the key, then do not lose it.
The vault can start small. When keys, categories, and distribution needs grow, the workflow stays the same.
Add
The raw code becomes a masked record.
Group
Categories and tags keep it findable.
Share
Open a single-code or category link.
Track
Claimed and used records stay separate.
Archive
Finished distribution stops cluttering the vault.
Open beta, open code.
Vultkey is built as an open-source product. The encryption approach, data model, public-link logic, and claim limits can be reviewed or self-hosted.
During beta, the goal is not only adding features. It is also making security decisions and distribution behavior clearer through community feedback.
Auditable code
Encryption, public-link limits, claim records, and audit flows are visible instead of being a black box.
Self-hostable
Designed to run with your own Supabase and Upstash setup when you want infrastructure control.
Beta with feedback
Bug reports, product ideas, and security feedback are part of the product roadmap.