Traceloop Review (2026)
The company behind OpenLLMetry, acquired by ServiceNow in March 2026 to power AI Control Tower. The Apache-2.0 SDK is safe and still actively developed - the managed platform's standalone future is the open question.
Rating
Starting Price
Custom
Free Plan
Yes
SDKs & Frameworks
7
Deployment
5
Best For
Teams that want vendor-neutral OpenTelemetry LLM instrumentation via OpenLLMetry, which is genuinely safe to adopt. The managed platform suits existing ServiceNow customers, or teams needing air-gapped deployment who can get contractual clarity on the roadmap.
Last Updated:
10 Things You Should Know About Traceloop
- 1 ServiceNow acquired Traceloop in March 2026, announced on Traceloop's own blog
- 2 Calcalist estimated the deal value at $60 to $80 million, terms undisclosed
- 3 It was ServiceNow's third Israeli acquisition in under three months, after Armis Security and Pyramid Analytics
- 4 Traceloop had raised $6.1M from Sorenson Capital, Ibex Investors, Samsung NEXT, Y Combinator and Grand Ventures
- 5 Customers at acquisition included IBM, HiBob, Miro and Dynatrace
- 6 OpenLLMetry is Apache 2.0 and the team publicly committed it will stay that way
- 7 The integration shipped into ServiceNow AI Control Tower at Knowledge 2026 in May 2026
- 8 The free cloud tier is 50,000 spans per month
Pros & Cons
Pros
- ✓ OpenLLMetry is Apache 2.0 and cannot be retroactively closed - the team committed publicly that it stays that way
- ✓ The SDK works without Traceloop at all, exporting to Datadog or any of 25+ backends, so adopting it carries very little lock-in
- ✓ Genuinely OpenTelemetry-native and tracking the OTel GenAI semantic conventions closely
- ✓ The free cloud tier at 50,000 spans a month is more generous than Datadog's
- ✓ Air-gapped and on-prem deployment is available, which is rare in this category
- ✓ Repository remained actively maintained through the acquisition
Cons
- ✕ Acquired by ServiceNow in March 2026, and the standalone managed platform's roadmap is now subject to a much larger owner's strategy
- ✕ The acquisition's stated purpose is powering ServiceNow AI Control Tower, not growing an independent observability product
- ✕ Enterprise pricing is not publicly disclosed, and post-acquisition pricing is an open question
- ✕ Third-party sources disagree with the vendor's own page on free-tier seat and retention limits
- ✕ The Ruby SDK is explicitly early-alpha
- ✕ Evaluation tooling is thinner than a dedicated eval platform
Features
Read this as two products
Traceloop is now two things with very different risk profiles, and conflating them is the mistake to avoid.
OpenLLMetry is an Apache-2.0 open-source project that extends OpenTelemetry to LLM applications. It is safe.
Traceloop the managed platform is now owned by ServiceNow, which bought it to power a governance product. Its independent future is an open question.
You can use the first without touching the second. That is the whole strategic point of this page.
The ServiceNow acquisition
We verified this against primary sources because it changes the recommendation. Traceloop’s own site carries a prominent “Traceloop is joining ServiceNow!” banner linking to a post from the CEO, and ServiceNow’s newsroom documents the resulting product expansion.
The facts:
- Announced March 2026. Terms undisclosed; Israeli outlet Calcalist estimated $60 to $80 million.
- ServiceNow’s third Israeli acquisition in under three months, after Armis Security and Pyramid Analytics.
- Traceloop had raised $6.1M from Sorenson Capital, Ibex Investors, Samsung NEXT, Y Combinator and Grand Ventures.
- Customers at acquisition included IBM, HiBob, Miro and Dynatrace.
- The integration shipped at Knowledge 2026 in May, giving AI Control Tower runtime observability into agent behaviour - how agents reason, where they decide, when to course-correct.
Here is the part that matters for a buyer. ServiceNow did not acquire Traceloop to sell more standalone LLM observability. It acquired Traceloop to make AI Control Tower a credible enterprise AI governance platform - alongside identity governance via Veza, agent kill switches, 30 new enterprise integrations, and cost and ROI dashboards.
That is a coherent and probably good strategy. It is also a different business from serving application teams who want a tracing tool.
This is not the Helicone situation. Nothing indicates maintenance mode, the site actively promotes signups, and development continued. But when a small product is bought to become a feature of a large platform, its standalone roadmap stops being set by its standalone customers. Weight that accordingly.
Why OpenLLMetry is genuinely safe
Most “the open-source part is fine” reassurances are thin. This one holds up, for three specific reasons.
The license cannot be revoked. OpenLLMetry is Apache 2.0. Whatever ServiceNow decides, the code you have today remains usable forever. The team also committed publicly and early that everything is Apache 2.0 “and will stay that way.”
It does not need Traceloop. This is the strongest argument. OpenLLMetry connects to 25+ supported observability platforms - Datadog among them. You can instrument your application with OpenLLMetry and ship the traces to a backend that has nothing to do with Traceloop or ServiceNow. Adoption carries almost no lock-in, which is a rare property in this category.
It stayed maintained through the acquisition. Version 0.60.0 shipped instrumentation updates for OTel GenAI semantic convention support, including Groq alignment with GenAI semconv v1.40.0, with issues continuing to be filed into April 2026. Roughly 7,100 stars and 947 forks. That is an active project, not a parked one.
Coverage spans Python, TypeScript, Go and Ruby, with 20+ providers (OpenAI, Anthropic, Gemini, Bedrock, Ollama), vector databases (Pinecone, Chroma) and frameworks (LangChain, LlamaIndex, CrewAI). The Ruby SDK is explicitly early-alpha - treat it accordingly.
What OpenLLMetry adds over plain OpenTelemetry
Worth being precise, because people conflate these.
Vanilla OpenTelemetry has no concept of a prompt, a completion, a token count or a vector search. OpenLLMetry supplies the instrumentation and semantic conventions for those concepts while keeping everything standard underneath - which is exactly why it can export anywhere.
The project tracks the OTel GenAI semantic conventions closely rather than inventing a private format. You are betting on a standard, not a vendor. Of everything in this category, that is among the most defensible bets you can make.
Pricing, with a caveat
| Tier | Price | Included |
|---|---|---|
| OpenLLMetry SDK | $0 | Apache 2.0, exports to 25+ backends |
| Cloud Free | $0 | 50,000 spans/mo, no seat limit, all features |
| Enterprise | Custom | On-prem, air-gapped, marketplace purchase |
The vendor’s own pricing page states the free tier is 50,000 spans per month with no seat limit and all features open. One third-party aggregator lists it more restrictively as 50,000 spans with 5 seats and 24-hour retention.
We trust the vendor on its own limits, but verify at signup - post-acquisition pricing changes are precisely the kind of thing that ships without an announcement. Enterprise pricing is not publicly disclosed, and what it looks like under ServiceNow is unknown.
One genuine strength: air-gapped deployment. Traceloop runs on-premise in AWS, GCP, Azure or any Kubernetes, including restricted and air-gapped environments, and is purchasable through all three major cloud marketplaces. Very little in this category supports true air-gapped operation, and ServiceNow ownership arguably strengthens the enterprise procurement story rather than weakening it.
Should you use it?
Use OpenLLMetry if you want vendor-neutral OpenTelemetry instrumentation for LLM applications. It is close to a free option with no downside, and you can point it at whatever backend you already run.
Use the managed platform if you are already a ServiceNow customer and the AI Control Tower story fits, or you need air-gapped deployment and can get written clarity on standalone availability and pricing.
Don’t use the managed platform if you need a vendor whose roadmap is driven by application-team customers rather than an enterprise governance strategy, and you cannot get that clarity contractually.
Bottom line: adopt the SDK without hesitation - it is one of the lowest-risk instrumentation choices available and it works with backends that have nothing to do with ServiceNow. Treat the platform as an enterprise procurement decision requiring answers in writing. The rating here reflects the platform’s roadmap uncertainty; judged alone, OpenLLMetry would score considerably higher.
Acquisition verified against Traceloop’s own site, ServiceNow’s newsroom and contemporaneous press reporting on 31 July 2026. Deal value is a press estimate, not a disclosed figure. This is a researched directory entry - we have not yet instrumented this platform with our reference application.
Pricing Plans
OpenLLMetry SDK
$0
- Apache 2.0, permanently open source
- Connects to 25+ observability backends
- Python, TypeScript, Go and Ruby
- No Traceloop account required
Traceloop Cloud (Free)
$0
- 50,000 spans per month
- No seat limit per the vendor's pricing page
- All features open
- Third-party aggregators quote tighter limits - trust the vendor page
Enterprise
Custom
- On-premise in AWS, GCP, Azure or any Kubernetes
- Air-gapped and restricted environments supported
- Available via AWS, GCP and Azure Marketplaces
- Pricing not publicly disclosed
SDKs & Frameworks
Deployment
Eval Methods
Standards
Corporate Status
Our Verdict
Split this decision in two, because the SDK and the platform now carry very different risk. OpenLLMetry - the Apache-2.0 OpenTelemetry extension - is one of the safest things you can adopt in this category. It is permissively licensed, the team publicly committed it stays that way, it exports to 25+ backends including Datadog, and it remained actively maintained through the acquisition. You can instrument with it and never create a Traceloop account. The managed platform is a different question. ServiceNow acquired Traceloop in March 2026, reportedly for $60 to $80 million, and shipped the integration into AI Control Tower at Knowledge 2026 in May. The stated strategic purpose is enterprise AI governance inside ServiceNow, not an independent observability product. The site still promotes signups and nothing suggests a Helicone-style wind-down, but a standalone product whose parent bought it for a different purpose is a roadmap you do not control. Use the SDK freely. Get contractual clarity before you build on the platform.
Similar Tools
Helicone
Almost nobody new - existing users who need a light open-source logging proxy and understand it's frozen. New buyers should look elsewhere.
New Relic AI Monitoring
Organisations already standardised on New Relic for APM, logs, Kubernetes and SRE workflows, running relatively low-volume LLM features, who need correlation more than evaluation.
Sentry
Error tracking and front-end debugging, which it does superbly. It is not the right tool for observing or evaluating LLM applications, and should be paired with one rather than substituted for one.
WhyLabs
Almost nobody as a platform. whylogs and LangKit remain defensible as libraries if you specifically need privacy-preserving statistical profiling and are prepared to maintain them yourself.
Frequently Asked Questions
Did ServiceNow really acquire Traceloop?
Yes, and we verified it against primary sources rather than relying on aggregators. Traceloop's own site carries a prominent "Traceloop is joining ServiceNow!" announcement linking to a blog post from the CEO, and ServiceNow's newsroom documents the AI Control Tower expansion that the acquisition enabled. The deal was announced in March 2026. Terms were not disclosed, though Israeli outlet Calcalist estimated $60 to $80 million. It was ServiceNow's third Israeli acquisition in under three months, following Armis Security and Pyramid Analytics.
Is OpenLLMetry still safe to use?
Yes, and this is the most important distinction on the page. OpenLLMetry is Apache 2.0 licensed, and an Apache 2.0 license cannot be retroactively revoked - the code you have today stays usable forever regardless of what ServiceNow decides. The team also committed publicly and early that everything stays Apache 2.0. The repository remained actively maintained through the acquisition period, with version 0.60.0 shipping instrumentation updates for OTel GenAI semantic convention support and issues continuing to be filed into April 2026. Crucially, OpenLLMetry exports to 25+ observability backends including Datadog, so you can instrument with it and never depend on Traceloop's platform at all.
Should I build on the managed platform?
Only with contractual clarity. Nothing we found suggests a Helicone-style wind-down - the site actively promotes signups and the product is being developed. But the strategic logic of the acquisition is worth reading honestly. ServiceNow bought Traceloop to power AI Control Tower, its enterprise AI governance product. That is a different business from selling standalone LLM observability to application teams. When a small product is acquired to become a feature of a large platform, the standalone offering's roadmap stops being set by its own customers. If you are considering the paid platform, ask ServiceNow directly about standalone availability and pricing commitments, and get the answer in writing before you migrate.
What is the free tier actually?
The vendor's own pricing page states 50,000 spans per month with no seat limit and all features open. One third-party aggregator lists it more restrictively as 50,000 spans with 5 seats and 24-hour retention. These conflict, and we would trust the vendor's own page on its own limits - but verify at signup, because post-acquisition pricing changes are exactly the kind of thing that lands without an announcement. For context, a span is any event in a trace, so every LLM call and every vector database query counts individually.
Can I run it air-gapped?
Yes, and this is genuinely unusual. Traceloop can be deployed on-premise in any environment - AWS, GCP, Azure or any Kubernetes setup - including air-gapped and other restricted environments, and it is purchasable through the AWS, GCP and Azure marketplaces. Very little in this category supports true air-gapped deployment. If that is your constraint, Traceloop is one of a small number of options, and being owned by ServiceNow arguably strengthens rather than weakens the enterprise procurement story.
How does OpenLLMetry differ from just using OpenTelemetry?
OpenLLMetry is a set of extensions built on top of OpenTelemetry rather than a replacement for it. Plain OTel has no idea what a prompt, a completion, a token count or a vector search is. OpenLLMetry adds the instrumentation and semantic conventions for those concepts while keeping everything standard underneath, which is why it can export to any OTel-compatible backend. The project tracks the OTel GenAI semantic conventions closely - recent releases aligned instrumentation with GenAI semconv v1.40.0 - so you are betting on a standard rather than a vendor format.