HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
skaldlabs
skald
TypeScript2025–2026
skaldlabs / skald · Archived

skald

Context layer platform in your infrastructure

3Distinct people
5Mentions
0Explicit recommenders
564GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Context layer platform in your infrastructure

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 week5 dated mentions

Observed mentions: 2025-11-19 12:28:32 UTC to 2026-01-18 01:43:45 UTC. Weeks start Monday, UTC.

0122025-11-17 00:00:00 UTC to 2025-11-24 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 172025-11-24 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-12-01 00:00:00 UTC to 2025-12-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-08 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-12-15 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 152025-12-22 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 00:00:00 UTC to 2026-01-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-12 00:00:00 UTC to 2026-01-19 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 12

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
Nov 172025-11-17 00:00:00 UTC2025-11-24 00:00:00 UTC110
Nov 242025-11-24 00:00:00 UTC2025-12-01 00:00:00 UTC110
Dec 12025-12-01 00:00:00 UTC2025-12-08 00:00:00 UTC000
Dec 82025-12-08 00:00:00 UTC2025-12-15 00:00:00 UTC110
Dec 152025-12-15 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-29 00:00:00 UTC000
Dec 292025-12-29 00:00:00 UTC2026-01-05 00:00:00 UTC000
Jan 52026-01-05 00:00:00 UTC2026-01-12 00:00:00 UTC000
Jan 122026-01-12 00:00:00 UTC2026-01-19 00:00:00 UTC202

What Hacker News says

5 sources
Some feedback from me (not a likely user though): - It was easier to find a link to where you worked at than your repo (https://github.com/skaldlabs/skald?tab=readme-ov-file), you should have linked it visibly - I had no idea what / why I should use it so I looked at the demo video and it didn't seem to solve any particular use case for any particular problem, it was more a ,,config'' video instead of a demo video - From reading the (quite interesting) article it seemed like you are focusing on pivoting instead of iteration speed. Have you tried for example to just query an LLM to build the whole project that you have done? How much time would be to vibe code it? I know that HN is mostly against vibe coding, but if the project could have been created in 1-3 days and you took 3 month, that's a bigger issue than growth itself. In that case
Read the rest
the metric that should be looked at is iteration speed instead of just growth (both are super important though!)
In Raising money fucked me up

Show HN: Skald – open-source context layer API that runs in your VPC

Hey HN! We built an open source context layer to power AI agents and apps even in air-gapped infra setups. TL;DR: Use our API (or one of the 6 SDKs) to push context into the Skald platform, and get semantic search and AI chat out of the box. We’ve seen companies spend months building a context layer system internally, only for it to have subpar performance and require active maintenance. Skald gives you the plumbing to get started really fast when building context-aware agents and AI apps (customers have gone to prod in a day with us) but is still highly extensible and configurable to fit individual needs. Our core is entirely MIT-licensed and you can even run it with a fully self-hosted stack (document parsing, chunking, vector search, LLM, etc) in your VPC. We think solutions in this space must be open source, and not just “open source
Read the rest
but bring 6 API keys to get started”. Our customers have used Skald to quickly build features for their own users, as well as for internal tooling. The self-hosted MIT version is completely fully-featured, so much so that it’s what we run on our Cloud offering today. We do also have an enterprise license for larger customers that runs on their infra and has a few enterprise-focused features on top of the MIT version. Keen to hear your feedback and I’ll be around to answer questions! GitHub: https://github.com/skaldlabs/skald
5 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.