Helicone takes the simplest possible approach to LLM monitoring: it's a proxy. Change your OpenAI base URL from api.openai.com to oai.helicone.ai, add your Helicone API key as a header, and every LLM request is logged — latency, tokens, cost, prompts, and completions. No SDK integration, no code changes beyond a URL swap. - Source: dev.to / about 1 month ago

You're monitoring production traffic. You need Langfuse / Phoenix / Helicone / Braintrust for that. Online eval is a different problem class: implicit feedback, drift detection, hallucination rates on your data, not on HellaSwag. - Source: dev.to / about 2 months ago

For many teams, especially those starting out or with simpler needs, commercial solutions like Portkey, Helicone, OpenPipe, or LiteLLM Proxy offer off-the-shelf capabilities that cover many common proxy use cases (caching, logging, cost tracking). NeuroLink itself can be seen as an SDK that complements these, allowing you to integrate with them or build similar features on top. - Source: dev.to / 4 months ago

TL;DR: Go with Langfuse if you want open-source and self-hosted. Pick Helicone if you want the fastest setup (2 minutes, no SDK). Stick with LangSmith if your stack already runs on LangChain. And if your org already pays for Datadog, their LLM module slots right in. - Source: dev.to / 5 months ago

Hey HN, we're Justin and Cole, the founders of Helicone (https://helicone.ai) or self-deploy with our new fully open-source helm chart (https://helicone.ai/selfhost). Yet even with detailed traces, probabilistic systems are notoriously hard to debug at scale. So, we released evaluators (either via LLM-as-judge or custom Python evaluators leveraging the CodeSandbox SDK - https://codesandbox.io/docs/sdk/sandboxes).... - Source: Hacker News / over 1 year ago

Now let's take the above code and modify it with a popular obfuscator for JS - obfuscator.io. As a result, we will get a code like this:. - Source: dev.to / over 1 year ago

You can use tools like JavaScript Obfuscator or UglifyJS to obfuscate your code. - Source: dev.to / almost 2 years ago

I know it's frowned upon here, but there are commercial and open source[1] javascript obfuscators with domain locking functionalities. If your site is already a SPA, they can make it very painful to just lift it (not impossible, obviously, because everything is reverse-engineerable, but the point is to discourage the majority of thiefs). You can be creative: for example, if whoever cloned your site is located in... - Source: Hacker News / almost 2 years ago

I don't need/use IDA, Nemlei just used https://obfuscator.io/, which just obfuscates the crap out of the code using various known methods (which I won't go into detail, it's public knowledge) and an un-obfuscation was cooked up by others. The one fucked-up thing the website does is randomizing function names, it just changes every variable/function name. We can't "un-obfuscate" those, so it's up to our brains to... Source: over 2 years ago

It's to purposefully makes your code harder to read so it prevents people from stealing your work. Here's a tool that does it: https://obfuscator.io/. Source: over 3 years ago