Map API Key Dependencies
Before They Expire
Upload your codebase or config files and instantly see which services depend on expiring API keys. Stop cascading failures before they happen.
Get Started — $49/moCancel anytime. Instant access.
Static Analysis
Scans source code and config files to detect API key usage patterns automatically.
Dependency Map
Visual graph showing which services rely on each key and the blast radius of expiry.
Expiry Timeline
Dashboard with countdown timers so your team knows exactly when to rotate keys.
Simple Pricing
Pro Plan
- ✓ Unlimited codebase scans
- ✓ Visual dependency dashboards
- ✓ Expiry alerts & notifications
- ✓ Supports .env, YAML, JSON, TOML
- ✓ Team collaboration (up to 5 seats)
- ✓ Priority support
FAQ
What file types does the scanner support?
We support .env files, YAML, JSON, TOML, and common source code files including JavaScript, TypeScript, Python, Go, and Ruby.
Is my code stored on your servers?
No. Files are analyzed in-memory and discarded immediately after scanning. We never persist your source code or secrets.
How does it detect expiration dates?
The scanner looks for expiry metadata in config files, comments, and known provider formats (e.g. JWT exp claims, AWS key creation dates via API).