6 ms·
Launch HN: Helicone.ai (YC W23) – Open-source logging for OpenAI
Hi HN - Justin, Scott, and Barak here. We're excited to introduce Helicone (https://www.helicone.ai https://www.helicone.ai) an open-source logging solution for OpenAi applications. Helicone's one-line integration logs the prompts, completions, latencies, and costs of your OpenAI requests. It currently works with GPT, and can be integrated with one line of code. There’s a demo at https://www.helicone.ai/video https://www.helicone.ai/video.
Helicone's core technology is a proxy that routes all your OpenAI requests through our edge-deployed Cloudflare Workers. These workers are incredibly reliable and cause no discernible latency impact in production environments. As a proxy, we offer more than just observability: we provide caching and prompt formatting, and we'll soon add user rate limiting and model provider back off to make sure your app is still up when OpenAI is down.
Our web application then provides insights into key metrics, such as which users are disproportionately driving costs and what is the token usage broken down by prompts. You can filter this data based on custom logic and export it to other destinations.
Getting started with Helicone is quick and easy, regardless of the OpenAI SDK you use. Our proxy-based solution does not require a third party package—simply change your request's base URL from https://api.openai.com/v1 https://api.openai.com/v1 to https://oai.hconeai.com/v1 https://oai.hconeai.com/v1. Helicone can be integrated with LangChain, LLama Index, and all other OpenAI native libraries. (https://docs.helicone.ai/quickstart/integrate-in-one-line-of-code https://docs.helicone.ai/quickstart/integrate-in-one-line-of...)
We have exciting new features coming up, one of which is an API to log user feedback. For instance, if you're developing a tool like GitHub Copilot, you can log when a user accepted or rejected a suggestion. Helicone will then aggregate your result quality into metrics and make finetuning suggestions for when you can save costs or improve performance.
Before launching Helicone, we developed several projects with GPT-3, including airapbattle.com, tabletalk.ai, and dreamsubmarine.com. For each project, we used a beta version of Helicone which gave us instant visibility into user engagement and result quality issues. As we talked to more builders and companies, we realized they were spending too much time building in-house solutions like this and that existing analytics products were not tailored to inference endpoints like GPT-3.
Helicone is developed under the Common Clause V1.0 w/ Apache 2.0 license so that you can use Helicone within your own infrastructure. If you do not want to self-host, we provide a hosted solution with 1k requests free per month to try our product. If you exceed that we offer a paid subscription as well, and you can view our pricing at https://www.helicone.ai/pricing https://www.helicone.ai/pricing.
We're thrilled to introduce Helicone to the HackerNews community and would love to hear your thoughts, ideas, and experiences related to LLM logging and analytics. We're eager to engage in meaningful discussions, so please don't hesitate to share your insights and feedback with us!
- Kkoala 4y agoHmm, so to integrate I have to basically send my api key to you on every request? Not great
- VWWHFSfQ 4y agoDoes this run afoul of OpenAI's terms of of service in any way? Using a commercial proxy/broker like this to access their API services instead of using directly.
- justintorre75 4y agoWe see a lot of applications on the market essentially "proxying" traffic to OpenAI, moving to a non-proxy implementation is not too hard if they have any issues with us doing this.
- VWWHFSfQ 4y agoI mean from your users' perspective, not yours. Since it's their OpenAI access that will get revoked for violating the TOS.
- 3np 4y agoMore direct concern: PII leaking from end-users will be a problem if the usage of this service isn't made clear and consented with from each individual. I really think the responsible thing by providers like OP is to remind their customers about this. If you have end-users in for example EU then integrating a service like Helicone would usually require new informed consent to be legal.
- ttul 4y agoI think you could dispense with this issue by just adding Helicone to your list of subprocessors in your GDPR disclosure.
- Hansenq 4y agoCongrats! We've been happy users of Helicone for the past few months--it literally helped us solve a bug with OpenAI's API where we didn't know why requests were failing and we failed to log some of their responses. Helicone helped us debug that it was a token limit issue really quickly, especially since the logging around hasn't been great. Love how easy it was to integrate too--just one line to swap out the OpenAI API with theirs.