Softwr

Cloud · head to head

OpenTelemetry vs Spring Cloud Gateway

OpenTelemetry logo

OpenTelemetry

Cloud

Vendor-neutral standard for traces, metrics and logs

From
Free
Rated
-
Spring Cloud Gateway logo

Spring Cloud Gateway

APIs

API gateway built on Project Reactor for building microservices

From
Free
Rated
-

The short version

  • Each has a real cost: OpenTelemetry genuinely complex to adopt: collectors, pipelines, samplers and exporters are a system to run in their own right; Spring Cloud Gateway released under the Apache 2.0 license, free and open source with no commercial tier
  • They diverge on capability: OpenTelemetry covers Vendor-neutral SDKs, Spring Cloud Gateway covers Routing.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which OpenTelemetry and Spring Cloud Gateway actually diverge.

Attributes where OpenTelemetry and Spring Cloud Gateway differ
AttributeOpenTelemetrySpring Cloud Gateway
Pricing modelOpen source, no licence feeopen-source
PlatformsLinux, macOS, Windows, Kubernetes, DockerJava, Spring Boot
CategoryCloudAPIs
FoundedUnknown1998

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in OpenTelemetry

  • Vendor-neutral SDKs
  • Collector
  • Three signals
  • Auto-instrumentation

Only in Spring Cloud Gateway

  • Routing
  • Path Rewriting
  • Circuit Breaker
  • Spring Boot
  • Spring Security
  • Spring Cloud
  • Java support
  • Spring Boot support

What people use each for

The jobs each tool is most often brought in to do.

OpenTelemetry

  • Instrumenting once and keeping the option to change observability vendor laternot Spring Cloud Gateway
  • Standardising telemetry across services written in different languagesnot Spring Cloud Gateway
  • Routing and filtering telemetry centrally to control observability spendnot Spring Cloud Gateway

Spring Cloud Gateway

  • API Developmentnot OpenTelemetry
  • API Gatewaynot OpenTelemetry
  • API Testingnot OpenTelemetry
  • API Documentationnot OpenTelemetry
  • Microservicesnot OpenTelemetry

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

OpenTelemetry

  • Genuinely complex to adopt: collectors, pipelines, samplers and exporters are a system to run in their own right
  • Language SDKs mature at different rates, so a polyglot estate gets uneven support
  • It produces and moves telemetry but does not store or visualise it, so a backend is still required and still billed

Spring Cloud Gateway

  • Released under the Apache 2.0 license, free and open source with no commercial tier

Pricing, plan by plan

OpenTelemetry

Free
  • OpenTelemetryFree
    • Full functionality
    • No usage limits
    • Community support

Spring Cloud Gateway

Free
  • Open SourceFree
    • Core Spring Cloud Gateway
    • Community support

Which should you pick?

Choose OpenTelemetry if

  • You need vendor-neutral sdks.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Kubernetes, Docker.
  • You also want collector.

Choose Spring Cloud Gateway if

  • You need routing.
  • You want to start without paying.
  • You work on Java, Spring Boot.
  • You also want path rewriting.

Questions people ask

Is OpenTelemetry or Spring Cloud Gateway better?
Neither clearly leads. OpenTelemetry starts at Free and Spring Cloud Gateway at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, OpenTelemetry or Spring Cloud Gateway?
OpenTelemetry starts at Free and Spring Cloud Gateway at Free.
Does OpenTelemetry or Spring Cloud Gateway run on more platforms?
OpenTelemetry runs on Linux, macOS, Windows, Kubernetes, Docker. Spring Cloud Gateway runs on Java, Spring Boot.
Can I use OpenTelemetry for free?
Both have a free tier, so you can try either at no cost before committing.
What is OpenTelemetry best used for?
OpenTelemetry is most often used for instrumenting once and keeping the option to change observability vendor later, standardising telemetry across services written in different languages, routing and filtering telemetry centrally to control observability spend. Of those, instrumenting once and keeping the option to change observability vendor later and standardising telemetry across services written in different languages are not what Spring Cloud Gateway is typically brought in for.
What can OpenTelemetry do that Spring Cloud Gateway cannot?
OpenTelemetry covers Vendor-neutral SDKs, Collector, Three signals, Auto-instrumentation. Spring Cloud Gateway covers Routing, Path Rewriting, Circuit Breaker, Spring Boot.

Answered from the vendors’ own pages

OpenTelemetry: Is OpenTelemetry free?

Yes, open source under the CNCF. What you pay for is the backend you export to.

Spring Cloud Gateway: Is Spring Cloud Gateway free?

Yes, Spring Cloud Gateway is free and open-source software. It is part of the Spring ecosystem and available through GitHub repositories with open-source dependencies like spring-cloud-starter-gateway-server-webflux and spring-cloud-starter-gateway-server-webmvc.

Source
OpenTelemetry: Does OpenTelemetry replace Datadog or Grafana?

No. It replaces their proprietary agents and instrumentation libraries. You still need a backend to store and query the data.

Spring Cloud Gateway: What enterprise support is available for Spring Cloud Gateway?

Tanzu Spring provides optional enterprise support including Day 0 access to security patches for organizations requiring guaranteed support, but specific pricing is not published on the Spring Cloud Gateway project page.

Source
OpenTelemetry: Why adopt a vendor-neutral standard?

Because instrumentation is the expensive part. Once code emits OTel, changing observability vendor is a collector config change instead of re-instrumenting every service.

Share

Related pages

Other head to heads