Nicheloom visits: 57,933 all-time · 7,694 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

IceGate

Observability data lake engine

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Today we're (@sprosvirnin and I) launching the first open-source release of IceGate - a Rust-native engine that stores logs (metrics and traces coming soon) in Apache Iceberg tables on your own object storage.Observability costs are out of control. Teams pay per GB ingested, get locked into proprietary formats, and can't use their own data outside the vendor's UI. We built the first observability data lake engine to fix this.This is our first release under Apache 2.0. We're building in the open and looking for contributors and early adopters who want observability without the markup.Star us on GitHub: https://github.com/icegatetech/icegateMore info on https://icegate.techDocumentation: https://docs.icegate.techLinkedIn: https://www.linkedin.com/company/icegatetech/

HN · launched Apr 13, 2026 · 15 upvotes (top 29%) · 0 views

Niche: database management systems and engines · 162 launches, 6 in the last 7 days ▼ -25% · Explore this niche →

Category and tags

  • Horizontal
  • Data infrastructure
  • Developer
  • Not AI
  • Commercial product

Visit website ↗ Source listing ↗

Could you build this?

No Building a high-throughput observability engine in Rust that converts streaming telemetry into Apache Iceberg tables and Parquet files on object storage demands specialized systems and distributed data lake engineering.

What it would actually take: Requires a high-performance ingestion pipeline in Rust (e.g., Tokio, Arrow, Apache Iceberg Rust crate) with buffering, compaction, and schema evolution. The system must implement efficient Parquet encoding, Iceberg metadata management (manifests, snapshots, commit conflicts with optimistic concurrency), and low-latency S3/GCS multipart uploads under high-throughput log ingestion conditions.

Discussion

5 comments analyzed.

Competitors mentioned: Loki, Grafana, Trino, Spark, Flink

Concerns raised: Lack of public benchmarks to verify 3x speed claim, Fault tolerance architecture and guarantees unclear, State management and failure recovery details needed

Competitors

Other products that read as similar to this one : 256 launches clear the similarity bar, closest 8 shown.

Attention rank: #97 of 257 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 166 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.