Keys can end up in plaintext
Some apps ask you to paste a provider key into a config file. Copies can remain in local folders, backups or shared project files.
KeyFence is a planned Windows app for keeping AI API keys out of app configs and giving each app its own spend caps.
Get KeyFence launch updates. Confirm your email to finish joining.
Coming soon to the Microsoft Store
The problem
Some apps ask you to paste a provider key into a config file. Copies can remain in local folders, backups or shared project files.
Budget reporting and enforcement vary by provider. A displayed limit is not always an immediate stop for every app sharing a key.
If a shared provider key leaks, requests made with it can be charged to your account until access is stopped. Separating app access is the goal.
Planned workflow
These are the features we plan to build. They are not available yet.
KeyFence would keep your provider keys in Windows Credential Manager, with Windows Hello used to unlock access in the app.
Each connected app would receive a stand-in key with a daily or monthly spend cap for requests routed through KeyFence.
The planned leak scanner would check common local config locations for exposed API keys so you can move or rotate them.
The tray panic button would stop all requests through KeyFence-managed keys at once. Revoking a provider key itself would remain a separate step with the provider.
Founder interest
Register interest in a proposed one-time founder price. This is not an order or a price guarantee. No payment details are collected.
Email confirmation is still required. Check your inbox and confirm your address to finish joining the KeyFence waitlist.
KeyFence is still a plan. Join the waitlist to hear when it is ready for the Microsoft Store.
Get KeyFence launch updates. Confirm your email to finish joining.