IceGate
Observability data lake engine
Details
- External ID
- 47753261
- Source
- HN
- Company
- —
- Product
- IceGate
- Website domain
- github.com
- Launched
- April 13, 2026
- Cohort
- —
- Upvotes
- 15
- Upvotes percentile
- 0.7062982005141388
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
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/
Enrichment
- Theme
- developer infrastructure and monitoring utilities
- Vertical
- Horizontal
- Function
- Observability & eval
- Audience
- B2B
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- data lake engine for observability
- Manually corrected
- False
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 — 104 launches clear the similarity bar, closest 8 shown.
Attention rank: #44 of 105 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 166 days after the earliest competitor.
- OpenObserve · ph · 2026-03-18 · 304 upvotes · similarity 0.49
- Public Apache Iceberg datasets via a REST catalog · hn · 2026-01-15 · 13 upvotes · similarity 0.45
- Rapid-rs · hn · 2025-11-20 · 9 upvotes · similarity 0.45
- I made an open-source Rust program for memory-efficient genomics · hn · 2025-11-13 · 17 upvotes · similarity 0.42
- Glintlog · hn · 2026-02-04 · 10 upvotes · similarity 0.42
- Superlog (YC P26) · hn · 2026-05-19 · 74 upvotes · similarity 0.42
- Artifact Keeper · hn · 2026-02-06 · 166 upvotes · similarity 0.40
- Oodle.ai · hn · 2026-07-14 · 31 upvotes · similarity 0.39
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a observability & eval tool for Media & entertainment yet.