Helicone frozen post-acquisition: an enterprise user maps proxy-shaped alternatives
_ashishojha · reddit · 2026-10-15
An enterprise user who self-hosted Helicone for a year (request logs + per-feature cost attribution) found it in maintenance mode since Mintlify's March acquisition — security fixes and new model support only, roadmap frozen — and their security team is uneasy about a static component in the request path.
Key takeaway: the migration path depends on how you used Helicone. Proxy-shape options include LiteLLM proxy (open source, self-hosted, per-virtual-key budgets), Portkey, and Orq AI's gateway (logs + evals in one place); if SDK/OTel tracing is acceptable, Langfuse and Phoenix come up most.
Enterprise wrinkles: SSO, per-team cost attribution, and EU data-residency concerns — self-hosting sidestepped them, hosted options reopen the question.
More from Infra
- Cadence announces sovereign AI cloud for European chip designers — karlfreund · 2026-10-23
- SGLang Deep-Dive Blog Series Breaks Down KV Cache, Posts up to 15.5x Throughput Gains — BanghuaZ · 2026-10-23
- DynaLM: Open-Source CPU-First LLM Inference Engine Seeks Feedback — Unlikely_Safety_7456 · 2026-10-23
- Capital Is Now the AI Buildout Bottleneck, Says Analyst Citing Jensen Huang — JOBhakdi · 2026-10-23
- Cerebras explains how it deploys trillion-parameter models on wafer-scale chips — bookwormengr · 2026-10-23
- IFM open-sources RL360, the agentic RL infra behind K2 Horizon's training — rupspace · 2026-10-23