Guides
Keep your API keys from costing you
Step-by-step setups tested on real hosts, and short answers for when a key leaks, before it does, and when you build something that needs one.
Set up your app without code changes
- Connect your app to Vallkey without code changesHow auto-connect works in Node.js, Bun, Python, Ruby, Java and .NET, which host needs what, and the one setting that breaks builds.
- Vallkey on Vercel: Next.js, Node.js, Bun, Python and RubyStep by step for each language Vercel runs, tested on real deployments: where auto-connect goes, how to check it works, and how to fix a failed build.
- Vallkey on Railway: Node.js, Python, Ruby, Java and .NETStep by step for each language, with and without Docker, tested on real deployments: start commands, railpack.json, and checking every request.
Keep keys safe
- My API key leaked: what to do in the next 10 minutesA leaked OpenAI, Stripe, Anthropic, Google or GitHub key: how to stop the damage, check what it cost, and make the next leak harmless.
- How to put a spending limit on an API keyWhy account budgets are not enough, and how to cap what each key can spend on AI tokens or move in payments, per day and per month.
- How to hide an API key in React, Next.js, Vite and ExpoWhy NEXT_PUBLIC_, VITE_ and EXPO_PUBLIC_ variables end up in the browser, and the two safe ways to call an API from a web or mobile app.
- Free tool: is your website leaking API keys?Check your site's JavaScript for secret keys in a few seconds.
Your next leaked key can be a non-event
Protect your first key in five minutes. Free plan, no card needed.