Infrastructure

Observability data storage without vendor lock-in

Tarn · Keep logs, metrics and traces in your own bucket, in open tables you can query

WatchingDraft scoreMature market · since 2010 · AI estimate

38PWAS score

Confidence

Based on 8 of 9 factors

Overview

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem: Teams pay per-GB ingestion fees for observability platforms and face vendor lock-in through proprietary formats, preventing them from using their own observability data outside the vendor's interface.
Solution concept: An open-source observability data lake engine that stores logs, metrics, and traces in open table formats (Apache Iceberg) on customer-owned object storage, eliminating per-GB costs and vendor lock-in while preserving data portability and access through standard tools.
Who has it: Software teams and engineering organizations using observability platforms (logs, metrics, traces) at scale.
How they handle it today: Today, teams send observability data (logs, metrics, traces) to hosted observability vendors who charge based on ingestion volume and store data in proprietary formats accessible only through the vendor's UI.
Why now: Observability costs have become prohibitive at scale due to per-GB ingestion pricing models used by dominant vendors, making cost-effective alternatives timely.
How it could charge: This inference based on the signal: commercial support, managed hosting, hosted versions of the open-source engine, or value-added tooling around the data lake (query optimization, analytics, alerting integrations).

Verdict

Computed from the factor scores below, never written by a model. It decides nothing on its own: only the gate makes an opportunity a build candidate.

Score breakdown

A model sorted each factor into a rubric bucket; code turned buckets into numbers. Unknown factors are left out of the score and lower confidence instead.

Market validation

Confidence 95 · 2 evidence · A Hacker News post showing modest engagement (15 points, 5 comments) and explicit claims of demand for lock-in-free observability solutions indicate scattered interest, but no established products or broad market data yet.

Revenue evidence

Unknown

The evidence shows demand claims and an inferred monetization model, but no public data on whether anyone currently pays for observability data lake solutions or lock-in-free alternatives.

Growth

Confidence 30 · Judged from the description · The opportunity description notes vendor lock-in as a problem and mentions observability as a growing category generally, but the evidence shows only modest engagement on one Hacker News post, not breakout growth signals.

Problem severity

Confidence 70 · 1 evidence · Per-GB ingestion costs create recurring friction and direct financial loss for teams at scale; vendor lock-in prevents data portability and forces continued use of expensive proprietary platforms.

Economic proximity

Confidence 30 · Judged from the description · The solution directly reduces observability costs (per-GB savings) and enables cost recovery by moving to customer-owned storage; it sits close to cost-saving decisions teams make on observability spend.

Distribution

Confidence 30 · Judged from the description · The open-source engine and hosted versions could be shared within engineering teams and across organizations, but usage is primarily internal observability infrastructure unlikely to organically reach non-users.

Buildability

Confidence 30 · Judged from the description · Building requires integrating Apache Iceberg, supporting multiple signal types (logs, metrics, traces), and ensuring compatibility with standard query tools—more than a simple MVP but less than breakthrough research.

Differentiation

Confidence 70 · 1 evidence · The clear gap is vendor lock-in through proprietary formats; open table formats and customer-owned storage offer a structural differentiation that incumbents do not emphasize, addressing a named user pain point.

Retention and timing

Confidence 30 · Judged from the description · Observability is a recurring, essential workflow for engineering teams managing production systems; lock-in concerns are persistent and timing aligns with growing data costs and multi-vendor strategies.

Risk penalties

Depends on one platformWhile the product aims to avoid vendor lock-in, its adoption depends heavily on cloud object storage platforms (AWS S3, GCS, Azure Blob) and Iceberg ecosystem maturity; a shift in these dependencies could limit portability.−6
Extreme competitionEstablished observability vendors (Datadog, New Relic, Elastic, Grafana Loki) are large and well-funded; breaking into their customer base requires overcoming inertia and entrenched integrations.−6

Score history

38 · confidence 44 · config v1First score · 30 Oct 2026

Observability data storage without vendor lock-in

Overview

Verdict

Build this business

Score breakdown

Risk penalties

Score history

Validation gate

Evidence · 5 items

Market validation

Revenue evidence

Problem severity

Differentiation

Market

Existing products

Build

Legal reconstruction check

Community