Softwr

Web Development · head to head

Preact vs Zipkin

Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-
Zipkin logo

Zipkin

Cloud

Distributed tracing system for microservice latency

From
Free
Rated
-

The short version

  • Each has a real cost: Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose; Zipkin less active development and smaller community momentum than Jaeger
  • They diverge on capability: Preact covers 3kB runtime, Zipkin covers Trace collection and search.
  • Prices and features above were last checked on 29 August 2026.

Where they differ

Only the attributes on which Preact and Zipkin actually diverge.

Attributes where Preact and Zipkin differ
AttributePreactZipkin
PlatformsWebLinux, Docker, Kubernetes, Self-hosted
CategoryWeb DevelopmentCloud

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 Preact

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

Only in Zipkin

  • Trace collection and search
  • Dependency diagram
  • Simple deployment
  • Pluggable storage

What people use each for

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

Preact

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

Zipkin

  • Adding distributed tracing quickly without standing up heavy infrastructurenot Preact
  • Java and Spring Boot estates, where instrumentation support is long-establishednot Preact
  • Small deployments where Jaeger is more than the problem requiresnot Preact

Where each one falls short

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

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

Zipkin

  • Less active development and smaller community momentum than Jaeger
  • Fewer features: sampling, storage options and UI are all more limited
  • The interface is dated and slower to work with on large trace volumes
  • Tracing alone still leaves metrics and logs in separate tools during an incident

Pricing, plan by plan

Preact

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

Zipkin

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

Which should you pick?

Choose Preact if

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

Choose Zipkin if

  • You need trace collection and search.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want dependency diagram.

Questions people ask

Is Preact or Zipkin better?
Neither clearly leads. Preact starts at Free and Zipkin at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Preact or Zipkin?
Preact starts at Free and Zipkin at Free.
Does Preact or Zipkin run on more platforms?
Preact runs on Web. Zipkin runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Preact for free?
Both have a free tier, so you can try either at no cost before committing.
What is Preact best used for?
Preact is most often used for embedded widgets that load inside someone else’s page and must stay small, marketing and content sites where javascript payload affects core web vitals, applications targeting low-bandwidth or low-powered devices. Of those, embedded widgets that load inside someone else’s page and must stay small and marketing and content sites where javascript payload affects core web vitals are not what Zipkin is typically brought in for.
What can Preact do that Zipkin cannot?
Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering. Zipkin covers Trace collection and search, Dependency diagram, Simple deployment, Pluggable storage.

Answered from the vendors’ own pages

Preact: Is Preact free?

Yes, open source under the MIT licence.

Zipkin: Is Zipkin free?

Yes, open source with no licence fee.

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.

Zipkin: Zipkin or Jaeger?

Jaeger has more momentum, more features and CNCF backing. Zipkin is lighter and quicker to stand up, and remains well supported in the Java and Spring ecosystem.

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.

Zipkin: Does Zipkin work with OpenTelemetry?

Yes. OpenTelemetry can export to Zipkin, which is now the usual way to instrument for it.

Share

Related pages

Other head to heads