HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
evansinho
Lumina
TypeScript2026–2026
evansinho / Lumina

Lumina

A lightweight observability platform for LLM applications. Track costs, latency, and quality across your AI systems with minimal overhead.

2Distinct people
2Mentions
0Explicit recommenders
10GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A lightweight observability platform for LLM applications. Track costs, latency, and quality across your AI systems with minimal overhead.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval2 dated mentions

Observed mentions: 2026-01-25 07:08:52 UTC to 2026-01-27 16:00:06 UTC.

012026-01-25 06:00:00 UTC to 2026-01-25 09:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 25, 06:002026-01-25 09:00:00 UTC to 2026-01-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-25 12:00:00 UTC to 2026-01-25 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-25 15:00:00 UTC to 2026-01-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-25 18:00:00 UTC to 2026-01-25 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-25 21:00:00 UTC to 2026-01-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 00:00:00 UTC to 2026-01-26 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 03:00:00 UTC to 2026-01-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 06:00:00 UTC to 2026-01-26 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 09:00:00 UTC to 2026-01-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 26, 09:002026-01-26 12:00:00 UTC to 2026-01-26 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 15:00:00 UTC to 2026-01-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 18:00:00 UTC to 2026-01-26 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 21:00:00 UTC to 2026-01-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 00:00:00 UTC to 2026-01-27 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 03:00:00 UTC to 2026-01-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 06:00:00 UTC to 2026-01-27 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 09:00:00 UTC to 2026-01-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 12:00:00 UTC to 2026-01-27 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 15:00:00 UTC to 2026-01-27 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 27, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 25, 06:002026-01-25 06:00:00 UTC2026-01-25 09:00:00 UTC110
Jan 25, 09:002026-01-25 09:00:00 UTC2026-01-25 12:00:00 UTC000
Jan 25, 12:002026-01-25 12:00:00 UTC2026-01-25 15:00:00 UTC000
Jan 25, 15:002026-01-25 15:00:00 UTC2026-01-25 18:00:00 UTC000
Jan 25, 18:002026-01-25 18:00:00 UTC2026-01-25 21:00:00 UTC000
Jan 25, 21:002026-01-25 21:00:00 UTC2026-01-26 00:00:00 UTC000
Jan 26, 00:002026-01-26 00:00:00 UTC2026-01-26 03:00:00 UTC000
Jan 26, 03:002026-01-26 03:00:00 UTC2026-01-26 06:00:00 UTC000
Jan 26, 06:002026-01-26 06:00:00 UTC2026-01-26 09:00:00 UTC000
Jan 26, 09:002026-01-26 09:00:00 UTC2026-01-26 12:00:00 UTC000
Jan 26, 12:002026-01-26 12:00:00 UTC2026-01-26 15:00:00 UTC000
Jan 26, 15:002026-01-26 15:00:00 UTC2026-01-26 18:00:00 UTC000
Jan 26, 18:002026-01-26 18:00:00 UTC2026-01-26 21:00:00 UTC000
Jan 26, 21:002026-01-26 21:00:00 UTC2026-01-27 00:00:00 UTC000
Jan 27, 00:002026-01-27 00:00:00 UTC2026-01-27 03:00:00 UTC000
Jan 27, 03:002026-01-27 03:00:00 UTC2026-01-27 06:00:00 UTC000
Jan 27, 06:002026-01-27 06:00:00 UTC2026-01-27 09:00:00 UTC000
Jan 27, 09:002026-01-27 09:00:00 UTC2026-01-27 12:00:00 UTC000
Jan 27, 12:002026-01-27 12:00:00 UTC2026-01-27 15:00:00 UTC000
Jan 27, 15:002026-01-27 15:00:00 UTC2026-01-27 18:00:00 UTC110

What Hacker News says

2 sources
Evanson·Jan 27, 2026Submission

Show HN: Lumina – Open-source observability for AI systems(OpenTelemetry-native)

Hey HN! I built Lumina – an open-source observability platform for AI/LLM applications. Self-host it in 5 minutes with Docker Compose, all features included. The Problem: I've been building LLM apps for the past year, and I kept running into the same issues: - LLM responses would randomly change after prompt tweaks, breaking things. - Costs would spike unexpectedly (turns out a bug was hitting GPT-4 instead of 3.5). - No easy way to compare "before vs after" when testing prompt changes. - Existing tools were either too expensive or missing features in free tiers. What I Built: Lumina is OpenTelemetry-native, meaning: - Works with your existing OTEL stack (Datadog, Grafana, etc.). - No vendor lock-in, standard trace format. - Integrates in 3 lines of code. Key features: - Cost & quality monitoring – Automatic alerts when costs spike, or r
Read the rest
esponses degrade. - Replay testing – Capture production traces, replay them after changes, see diffs. - Semantic comparison – Not just string matching – uses Claude to judge if responses are "better" or "worse." - Self-hosted tier – 50k traces/day, 7-day retention, ALL features included (alerts, replay, semantic scoring) How it works: ```bash # Start Lumina git clone https://github.com/use-lumina/Lumina cd Lumina/infra/docker docker-compose up -d ``` ```typescript // Add to your app (no API key needed for self-hosted!) import { Lumina } from '@uselumina/sdk'; const lumina = new Lumina({ endpoint: 'http://localhost:8080/v1/traces', }); // Wrap your LLM call const response = await lumina.traceLLM( async () => await openai.chat.completions.create({...}), { provider: 'openai', model: 'gpt-4', prompt: '...' } ); ``` That's it. Every LLM call is now tracked with cost, latency, tokens, and quality scores. What makes it different: 1. Free self-hosted with limits that work – 50k traces/day and 7-day retention (resets daily at midnight UTC). All features included: alerts, replay testing, and semantic scoring. Perfect for most development and small production workloads. Need more? Upgrade to managed cloud. 2. OpenTelemetry-native – Not another proprietary format. Use standard OTEL exporters, works with existing infra. Can send traces to both Lumina AND Datadog simultaneously. 3. Replay testing – The killer feature. Capture 100 production traces, change your prompt, replay them all, and get a semantic diff report. Like snapshot testing for LLMs. 4. Fast – Built with Bun, Postgres, Redis, NATS. Sub-500ms from trace to alert. Handles 10k+ traces/min on a single machine. What I'm looking for: - Feedback on the approach (is OTEL the right foundation?) - Bug reports (tested on Mac/Linux/WSL2, but I'm sure there are issues) - Ideas for what features matter most (alerts? replay? cost tracking?) - Help with the semantic scorer (currently uses Claude, want to make it pluggable) Why open source: I want this to be the standard for LLM observability. That only works if it's: - Free to use and modify (Apache 2.0) - Easy to self-host (Docker Compose, no cloud dependencies) - Open to contributions (good first issues tagged) The business model is managed hosting for teams that don't want to run infrastructure. But the core product is and always will be free. Try it: - GitHub: https://github.com/use-lumina/Lumina - Docs: https://docs.uselumina.io - Quick start: 5 minutes from `git clone` to dashboard I'd love to hear what you think! Especially interested in: - What observability problems are you hitting with LLMs - Missing features that would make this useful for you - Any similar tools you're using (and what they do better) Thanks for reading!
1 points · Open discussion

Show HN: Lumina – Open-source observability for LLM applications

Hey HN! I built Lumina – an open-source observability platform for AI/LLM applications. Self-host it in 5 minutes with Docker Compose, all features included. The Problem: I've been building LLM apps for the past year, and I kept running into the same issues: - LLM responses would randomly change after prompt tweaks, breaking things - Costs would spike unexpectedly (turns out a bug was hitting GPT-4 instead of 3.5) - No easy way to compare "before vs after" when testing prompt changes - Existing tools were either too expensive or missing features in free tiers What I Built: Lumina is OpenTelemetry-native, meaning: - Works with your existing OTEL stack (Datadog, Grafana, etc.) - No vendor lock-in – standard trace format - Integrates in 3 lines of code Key features: - Cost & quality monitoring – Automatic alerts when costs spike or responses
Read the rest
degrade - Replay testing – Capture production traces, replay them after changes, see diffs - Semantic comparison – Not just string matching – uses Claude to judge if responses are "better" or "worse" - Self-hosted tier – 50k traces/day, 7-day retention, ALL features included (alerts, replay, semantic scoring) How it works: Start Lumina git clone https://github.com/use-lumina/Lumina cd Lumina/infra/docker docker-compose up -d // Add to your app (no API key needed for self-hosted!) import { Lumina } from '@uselumina/sdk'; const lumina = new Lumina({ endpoint: 'http://localhost:8080/v1/traces', }); // Wrap your LLM call const response = await lumina.traceLLM( async () => await openai.chat.completions.create({...}), { provider: 'openai', model: 'gpt-4', prompt: '...' } ); That's it. Every LLM call is now tracked with cost, latency, tokens, and quality scores. What makes it different: 1. Free self-hosted with limits that work – 50k traces/day and 7-day retention (resets daily at midnight UTC). All features included: alerts, replay testing, semantic scoring. Perfect for most development and small production workloads. Need more? Upgrade to managed cloud. 2. OpenTelemetry-native – Not another proprietary format. Use standard OTEL exporters, works with existing infra. Can send traces to both Lumina AND Datadog simultaneously. 3. Replay testing – The killer feature. Capture 100 production traces, change your prompt, replay them all, get a semantic diff report. Like snapshot testing for LLMs. 4. Fast – Built with Bun, Postgres, Redis, NATS. Sub-500ms from trace to alert. Handles 10k+ traces/min on a single machine. What I'm looking for: - Feedback on the approach (is OTEL the right foundation?) - Bug reports (tested on Mac/Linux/WSL2, but I'm sure there are issues) - Ideas for what features matter most (alerts? replay? cost tracking?) - Help with the semantic scorer (currently uses Claude, want to make it pluggable) Why open source: I want this to be the standard for LLM observability. That only works if it's: - Free to use and modify (Apache 2.0) - Easy to self-host (Docker Compose, no cloud dependencies) - Open to contributions (good first issues tagged) The business model is managed hosting for teams who don't want to run infrastructure. But the core product is and always will be free. Try it: - GitHub: https://github.com/use-lumina/Lumina - Demo video: [YouTube link] - Docs: https://docs.uselumina.io - Quick start: 5 minutes from `git clone` to dashboard I'd love to hear what you think! Especially interested in: - What observability problems you're hitting with LLMs - Missing features that would make this useful for you - Any similar tools you're using (and what they do better) Thanks for reading!
6 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.