How are you operating AI infrastructure in production?
There are many open-source projects across inference, orchestration, observability, vector search, data pipelines, evaluation, and model management.
- ▪There are many open-source projects across inference, orchestration, observability, vector search, data pipelines, evaluation, and model management.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,445 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (AI / LLM) |
| Canonical URL | https://news.ycombinator.com/item?id=49163280 |
| Publication time | Tue, 04 Aug 2026 01:05:25 +0000 |
| Retrieval time | 2026-08-04T01:10:43.510Z |
| Last seen | 2026-08-04T01:10:43.510Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | fL24ZE7OeUd5 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
There are many open-source projects across inference, orchestration, observability, vector search, data pipelines, evaluation, and model management. Most are relatively easy to test, but production operation is a different problem.For those running open-source AI infrastructure in production:- What are you running, for what workload, and would you recommend?- Do you operate yourself versus consume as a managed service?- Have you replaced or abandoned any tools because they were too difficult or expensive to operate?- What problems only appeared after moving beyond the prototype stage?- Anything that you would do differently if rebuilding the stack today?Thanks
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).
Discussion
0 commentsMore from Hacker News (AI / LLM)
