Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Glintlog

Self-hosted log aggregation in a single binary

Details

External ID
46883970
Source
HN
Company
—
Product
Glintlog
Website domain
glintlog.com
Launched
Feb. 4, 2026
Cohort
—
Upvotes
10
Upvotes percentile
0.5316711590296496
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Hello all!I built Glintlog because I wanted a simple way to aggregate logs without spinning up Elasticsearch, Loki, or a SaaS that costs my kidney…What it is: A self-hosted log aggregation tool that runs as a single binary. No Docker, no dependencies, no config files required.How it works: ``` curl -fsSL https://raw.githubusercontent.com/ibero-data/glintlog/main/s... | bash ```That's it. Open localhost:8080 and you have a log viewer with search, filtering, and live tail.Tech: - Go backend with embedded DuckDB for storage - Native OTLP support (gRPC on 4317, HTTP on 4318) - Works with any OpenTelemetry SDK out of the boxWhy I built it:I run small side projects and wanted observability without the complexity. Existing solutions either require too much infrastructure (ELK), are SaaS-only, or don't support OpenTelemetr natively. Glintlog is meant to be the SQLite of log aggregation – simple, embedded, good enough for most use cases. I use a lot for ETL’s now… (I’m a data engineer too)…It's not meant to replace SaaS that has a 500-person company. It's for small teams, and enthusiasts who want logs without the overhead, also covering all we need for it…Docs: https://glintlog.com/docs GitHub: https://github.com/ibero-data/glintlogWould love feedback. What features would make this useful for you? Would you pay per year?

Enrichment

Theme
database infrastructure and developer tools
Vertical
Horizontal
Function
Data infrastructure
Audience
B2B
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
self-hosted log aggregation
Manually corrected
False

Could you build this?

Partial A lightweight single-binary log receiver with an embedded web UI and SQLite/duckdb storage can be built quickly, but high-throughput concurrent ingestion with zero external dependencies is tricky.

What it would actually take: The architecture typically uses Go or Rust with an embedded columnar or append-only time-series storage engine (like DuckDB, SQLite with WAL, or a custom LSM tree) paired with a lightweight web frontend. The difficult parts are building efficient streaming ingestion that won't exhaust memory or lock the database under high ingest volume, alongside fast indexing and inverted search across unformatted logs. It requires solid systems programming and storage engineering knowledge.

Discussion

No comments on this launch.

Competitors

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

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

Launched 95 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a data infrastructure tool for Media & entertainment yet.