Softwr

APIs · head to head

Hasura vs Zipkin

Hasura logo

Hasura

APIs

GraphQL engine that instantly creates production-ready GraphQL API from databases

From
Free
Rated
-
Full reviewWebsite
Zipkin logo

Zipkin

Cloud

Distributed tracing system for microservice latency

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Hasura active model definition: model/command accessed more than 1,000 times monthly; Zipkin less active development and smaller community momentum than Jaeger
  • They diverge on capability: Hasura covers GraphQL API, Zipkin covers Trace collection and search.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Hasura and Zipkin actually diverge.

Attributes where Hasura and Zipkin differ
AttributeHasuraZipkin
Pricing modelfreemiumOpen source, no licence fee
PlatformsWebLinux, Docker, Kubernetes, Self-hosted
CategoryAPIsCloud
Founded2017Unknown

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 Hasura

  • GraphQL API
  • Real-time subscriptions
  • Access control
  • PostgreSQL
  • MySQL
  • Webhooks
  • REST APIs
  • Cloud support

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.

Hasura

  • Automatic GraphQL API generation from existing databasesnot Zipkin
  • Real-time data subscriptions for modern applicationsnot Zipkin
  • Backend infrastructure for web and mobile applicationsnot Zipkin
  • Event-triggered webhooks for database changesnot Zipkin

Zipkin

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

Where each one falls short

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

Hasura

  • Active model definition: model/command accessed more than 1,000 times monthly
  • Private DDN requires Base or Advanced plan

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

Hasura

Free
  • DDN FreeFree
    • Unlimited models
    • 1 supergraph developer
    • 15-minute observability retention
  • DDN Base$5/month
    • Per active model billing
    • Unlimited developers
    • 30-day observability retention
  • DDN Advanced$30/month
    • Per active model billing
    • Federated collaboration
    • Multi-repo CI/CD

Zipkin

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

Which should you pick?

Choose Hasura if

  • You need graphql api.
  • You want to start without paying.
  • You also want real-time subscriptions.
Hasura review

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.
Zipkin review

Questions people ask

Is Hasura or Zipkin better?
Neither clearly leads. Hasura 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, Hasura or Zipkin?
Hasura starts at Free and Zipkin at Free.
Does Hasura or Zipkin run on more platforms?
Hasura runs on Web. Zipkin runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Hasura for free?
Both have a free tier, so you can try either at no cost before committing.
What is Hasura best used for?
Hasura is most often used for automatic graphql api generation from existing databases, real-time data subscriptions for modern applications, backend infrastructure for web and mobile applications, event-triggered webhooks for database changes. Of those, automatic graphql api generation from existing databases and real-time data subscriptions for modern applications are not what Zipkin is typically brought in for.
What can Hasura do that Zipkin cannot?
Hasura covers GraphQL API, Real-time subscriptions, Access control, PostgreSQL. Zipkin covers Trace collection and search, Dependency diagram, Simple deployment, Pluggable storage.

Answered from the vendors’ own pages

Hasura: How much does Hasura cost?

Hasura DDN Free is free. DDN Base starts at $5/active model/month, and DDN Advanced starts at $30/active model/month.

Source
Zipkin: Is Zipkin free?

Yes, open source with no licence fee.

Hasura: What is an active model in Hasura pricing?

An active model is defined as any model or command accessed more than 1,000 times monthly.

Source
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.

Hasura: Is there a free version of Hasura?

Yes, Hasura DDN Free is always free and includes unlimited models, 1 supergraph developer, and 15-minute observability retention.

Source
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

More on Hasura

More on Zipkin

Keep looking

Other head to heads