About
FrenyTech
FrenyTech builds developer tooling and API infrastructure with one non-negotiable rule: sensitive data belongs on the server. The API Console is our reference implementation of that rule.
Why the API Console exists
Developer dashboards often hit third-party APIs directly from the browser. That habit leaks base URLs, API keys and credential payloads into network tabs, browser extensions and page state. The FrenyTech API Console shows a better pattern: the front end calls one internal endpoint, the server performs the upstream request, validates and sanitizes the response, and the UI works only with data that is safe to display.
The console is intentionally small — one action, one endpoint — so the security model is easy to audit and easy to copy into your own projects.
Principles
Secure by default
Credentials never reach the browser. Redaction is enforced on the server, not left to UI discipline.
Honest tooling
No mocked data, no fake states. Every result you see came from a real request through the proxy.
Observable
Live API status, typed errors and durations make it obvious what happened and why.
Deploy anywhere
A single server runtime with no external services, ready for Vercel or any edge platform.
Try it live
Run a real request through the secure proxy and inspect the sanitized result.