Helicone
Logs every model call by sitting in the request path, so nothing in your code has to be instrumented
What is Helicone?
Most tracing tools ask you to wrap your calls, which is fine until the code you need to see is inside a library, a background job or a service somebody else owns. Helicone takes the other route: point the base URL at it and every request is logged on the way through, with no SDK in the path. Because it is already in that position it does gateway work too — one key for many providers, automatic fallback when one is down, caching for repeated prompts. The trade is the position itself: a proxy is now between your application and the model, which is a component to run and a hop to account for. Agent runs group into sessions so a multi-step trace reads as one thing rather than thirty unrelated calls.
What can you do with Helicone?
- Log without changing the calling code — Changing the base URL is the whole integration, so calls made deep inside a library or another team's service are captured too.
- Read a multi-step run as one thing — Related calls group into a session, so an agent that made thirty requests to finish a task appears as one trace instead of thirty rows.
- Keep working when a provider does not — Because it is already in the request path, it can route across providers and fall back automatically when one starts failing.
- Stop paying twice for the same prompt — Repeated requests can be served from a cache, which matters in agent loops where the same context is resent on every turn.
- Turn logged traffic into a dataset — Recorded requests can be collected for evaluation or fine-tuning, so real usage becomes the test set rather than invented examples.
- Run it yourself if the data cannot leave — The platform is open source and self-hostable, which is the deciding factor when prompts contain material that must stay inside.
Before you choose Helicone
- A proxy in the request path is a component you now operate and a hop in every call — the reason to accept that is coverage you cannot get by instrumenting code you do not control.
- Self-hosting the full platform is a heavier proposition than adding a tracing library: it is a web application with its own datastores, not a package you import.
Star history
29 Aug to 30 Oct · +133
Frequently asked questions
Is Helicone free for commercial use?
Helicone is released under the Apache-2.0 licence — OSI-approved open source, which permits commercial use.
How can Helicone be deployed?
Helicone is available as Self-hosted / Managed cloud / Runs locally.