Lightstep (now ServiceNow Cloud Observability) pricing guide details
Pricing Overview
Lightstep, now rebranded as ServiceNow Cloud Observability, has shifted from a transparent self-serve pricing model to a sales-driven structure under ServiceNow's umbrella. Before the acquisition, Lightstep offered three clear tiers: a free Community plan, a Teams plan, and a custom Enterprise plan. Today, all pricing requires a direct quote from ServiceNow sales, which makes it harder to evaluate costs upfront. The platform is built on OpenTelemetry and focuses on distributed tracing, metrics, and change intelligence. We recommend contacting ServiceNow directly for current pricing, but we can outline what the historical tiers looked like and how they compare to alternatives in the observability space. Understanding these legacy prices gives teams a useful baseline for negotiations and helps contextualize what ServiceNow may offer during the sales process.
Plan Comparison
Before ServiceNow acquired Lightstep, the pricing structure was straightforward and publicly available. Here is what the legacy tiers included:
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Feature | Community (Free) | Teams | Enterprise (Custom) |
|---|---|---|---|
| Price | $0 | Not published | Custom quote |
| Projects | 1 project | Multiple projects | Unlimited projects |
| Span Ingestion | Limited | 100M spans/month | Custom volume |
| Distributed Tracing | Yes | Yes | Yes |
| Change Intelligence | Basic | Full | Full + Advanced |
| Data Retention | 7 days | 30 days | Custom retention |
| OpenTelemetry Support | Yes | Yes | Yes |
| SSO / SAML | No | No | Yes |
| Dedicated Support | Community only | Standard support | Premium support + SLA |
| Custom Dashboards | Limited | Yes | Yes + Advanced |
The Community tier was genuinely useful for small teams or individual developers exploring distributed tracing on a single project. With 7-day data retention and basic change intelligence, it served as a solid introduction to the platform without any financial commitment. The Teams plan included 100M spans and was aimed at mid-size engineering teams that needed longer retention and full access to change intelligence features. Enterprise pricing was negotiated based on data volume, retention needs, and support requirements, and typically included SSO/SAML integration and premium SLAs.
Since the ServiceNow acquisition, these tiers are no longer publicly listed. Current pricing is bundled into ServiceNow's broader ITOM (IT Operations Management) licensing, which typically involves annual contracts and volume-based negotiations. Teams migrating from legacy Lightstep plans should expect significant changes to how pricing is structured and billed.
Hidden Costs and Considerations
Several cost factors deserve attention when evaluating Lightstep under the ServiceNow umbrella. Span overage charges were a real concern under the old Teams plan once you exceeded the 100M spans allocation, and similar volume-based overages likely persist under ServiceNow's model. With ServiceNow's sales-driven approach, contract lock-in periods are common, often requiring annual or multi-year commitments with limited mid-term flexibility. Data egress fees may apply depending on your deployment model. Additional ServiceNow modules like ITSM integration or advanced AIOps features carry separate licensing costs that can add up quickly. We also recommend budgeting for onboarding and OpenTelemetry instrumentation setup time, which can represent a meaningful upfront investment.
Cost Estimates by Team Size
Lightstep's legacy Teams rate appears in no source we hold, so no cost estimate is given for it.
For teams above 25 engineers, the Enterprise tier typically became more cost-effective due to volume discounts. Under ServiceNow's current model, we expect pricing to be based more on data volume and platform usage rather than strict per-seat licensing, though exact structures vary by contract.
How Lightstep Pricing Compares
The observability market has become increasingly competitive since Lightstep's acquisition. Here is how ServiceNow Cloud Observability stacks up against major alternatives:
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Platform | Starting Price | Pricing Model | Free Tier | Key Differentiator |
|---|---|---|---|---|
| Lightstep (ServiceNow) | Custom quote | Sales-driven | No longer available | OpenTelemetry-native, change intelligence |
| New Relic | $0 (free tier) | Usage-based | Yes, 100 GB/month | Full-stack observability, generous free tier |
| Observe | — | Usage-based | No | Unified data lake approach, simple pricing |
| Elastic Observability | — | Tiered | No | Open-source foundation, self-hosting option |
New Relic stands out with its free tier, making it the most accessible option for teams that want to start without a sales call. Observe offers straightforward pricing, which appeals to teams that want predictable costs tied directly to data volume. Elastic Observability offers a self-hosted open-source option that can reduce licensing costs significantly.
Lightstep's strength remains its OpenTelemetry-native architecture and change intelligence capabilities, but the lack of public pricing under ServiceNow makes direct cost comparisons difficult without engaging their sales team. For teams that prioritize pricing transparency and self-serve onboarding, New Relic or Observe may be stronger choices. For organizations already invested in the ServiceNow ecosystem, bundling Cloud Observability into an existing ITOM contract could yield better overall value.