Softwr

Cloud · head to head

Jaeger vs Preact

Jaeger logo

Jaeger

Cloud

Open-source end-to-end distributed tracing

From
Free
Rated
-
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-

The short version

  • Each has a real cost: Jaeger tracing is only as good as the instrumentation, and partial instrumentation produces misleading gaps; Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • They diverge on capability: Jaeger covers Distributed trace search, Preact covers 3kB runtime.
  • Prices and features above were last checked on 29 August 2026.

Where they differ

Only the attributes on which Jaeger and Preact actually diverge.

Attributes where Jaeger and Preact differ
AttributeJaegerPreact
PlatformsLinux, Kubernetes, DockerWeb
CategoryCloudWeb Development

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Jaeger

  • Distributed trace search
  • Dependency graph
  • Adaptive sampling
  • Pluggable storage

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What people use each for

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

Jaeger

  • Finding which service in a request path causes the latencynot Preact
  • Understanding real service dependencies rather than the diagram on the wikinot Preact
  • Debugging failures that only appear under production traffic patternsnot Preact

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot Jaeger
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Jaeger
  • Applications targeting low-bandwidth or low-powered devicesnot Jaeger

Where each one falls short

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

Jaeger

  • Tracing is only as good as the instrumentation, and partial instrumentation produces misleading gaps
  • Storage is the real operational cost: high-volume tracing on Elasticsearch or Cassandra is a cluster to run and pay for
  • Traces alone, without correlated metrics and logs, leave you switching between tools during an incident

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

Pricing, plan by plan

Jaeger

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

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

Choose Jaeger if

  • You need distributed trace search.
  • You want to start without paying.
  • You work on Linux, Kubernetes, Docker.
  • You also want dependency graph.

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.

Questions people ask

Is Jaeger or Preact better?
Neither clearly leads. Jaeger starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Jaeger or Preact?
Jaeger starts at Free and Preact at Free.
Does Jaeger or Preact run on more platforms?
Jaeger runs on Linux, Kubernetes, Docker. Preact runs on Web.
Can I use Jaeger for free?
Both have a free tier, so you can try either at no cost before committing.
What is Jaeger best used for?
Jaeger is most often used for finding which service in a request path causes the latency, understanding real service dependencies rather than the diagram on the wiki, debugging failures that only appear under production traffic patterns. Of those, finding which service in a request path causes the latency and understanding real service dependencies rather than the diagram on the wiki are not what Preact is typically brought in for.
What can Jaeger do that Preact cannot?
Jaeger covers Distributed trace search, Dependency graph, Adaptive sampling, Pluggable storage. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Jaeger: Is Jaeger free?

Yes, open source and CNCF-graduated. Costs are the storage backend you run.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Jaeger: Do I use Jaeger or OpenTelemetry?

Both, usually. Instrument with OpenTelemetry and use Jaeger to store and query the traces.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

Jaeger: Does Jaeger handle metrics and logs?

No. It is a tracing system. Metrics and logs need Prometheus, Loki or an equivalent.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

Share

Related pages

Other head to heads