Qryn logo

Qryn

Polyglot observability stack on ClickHouse providing drop-in replacements for Loki, Prometheus, Tempo and Datadog APIs.

-

Our Verdict

Ambitious polyglot observability on ClickHouse; great for cost savings if you can operate it.

Pros

  • ClickHouse backend supports Loki, Prom, Tempo, DD APIs
  • Single storage across telemetry types cuts costs
  • Open-source core with commercial support
  • No vendor lock-in via standard APIs

Cons

  • ClickHouse ops skills needed for self-hosting
  • Smaller team than Grafana Labs
  • Managed service less mature than Grafana Cloud
  • Query tuning can surprise Prometheus veterans
Best for: Teams wanting unified ClickHouse storage for LGTM stack without Grafana Cloud bills. Not for: Teams without ClickHouse expertise or wanting turnkey hosted experience.

When to Use Qryn

Good fit if you need

  • Drop-in Loki, Prometheus, and Tempo on ClickHouse
  • Datadog-compatible API with open-source stack costs
  • Unified polyglot observability with one storage backend
  • Cost-efficient log storage with ClickHouse compression

Qryn Pricing

Pricing Model
free
Free Tier
Yes
Entry Price
β€”
Enterprise Available
No
Transparency Score
β€”

Beta β€” estimates may differ from actual pricing

1,000
1001K10K100K1M

Estimated Monthly Cost

$25

Estimated Annual Cost

$300

Estimates are approximate and may not reflect current pricing. Always check the official pricing page.

Project Health

B

Health Score

1.7k 89
Bus Factor

6

Last Commit

12 days

Release Freq

37d

Open Issues

21

Issue Response

0d

License

AGPL-3.0

Last checked: 2026-04-21

Lock-in Assessment

Low 5/5
Lock-in Score
5/5

πŸ”„ Thinking about migrating off Qryn?

Get an AI-drafted migration plan + a copy-paste email to Qryn support requesting a data export. Pick where you're moving to and tell us your context.

Looking for alternatives to Qryn?

Answer 4 quick questions β€” get an AI-ranked shortlist of tools that match your stack and requirements.

Open AI Tool Finder

Community Discussion

Comments powered by Giscus (GitHub Discussions). You need a GitHub account to comment.