Local selective proxy
Intercept only sensitive API traffic while normal browsing and low-risk calls stay direct.
Placeholder logo
Start self-hostingKeyRelay
Keep agents fast.Keep secrets out of reach.
KeyRelay routes sensitive API calls through a secure relay so agents can take action without ever touching real provider keys.
No raw keys on endpoints
100%
Typical added latency
20–100ms
Approval channels
Email · SMS · WhatsApp
Quickstart
terminal
curl -fsSL https://get.keyrelay.dev/install.sh | bash keyrelay login keyrelay proxy start --mode enforce keyrelay policy apply default-supabase.yml
What it does
Remote key relay
Real provider keys stay in a remote vault. Your agent never sees raw credentials.
Policy + approvals
Apply allow, deny, or approval rules by host, path, method, and process identity.
Email / SMS / WhatsApp
High-risk actions can require one-tap human approval before execution.
Audit trail
Correlation IDs and immutable events give full visibility over who did what and when.
Open source core
Self-hostable architecture with optional managed hosting for teams that want less ops.
Works with your stack
OpenAIAnthropicSupabaseStripeSlackGmailGitHubNotionTwilioCloudflare
Security model
- • Local proxy enforces selective routing and policy matching.
- • Remote relay injects keys server-side and executes requests.
- • Signed policy bundles + short-lived credentials.
- • Immutable audit logs with end-to-end correlation IDs.
Self-host or managed
Run KeyRelay on your own infrastructure, or use managed hosting as soon as it lands. Either way, the architecture keeps real secrets off endpoints.