Rachis

Pain map

What breaks in document AI

290 production incidents from public threads. Every quote links to its source. Pick a category and check it yourself.

  • “we have had teams create the same agents using dspy, langgraph compete with pure agent loops and the agent loops come across as so much better by a wide margin”
    Hacker News · 28 September 2026 · in production · open the thread
  • “We used it for months. Eventually, we removed it completely.”
    dev.to · 27 July 2026 · in production · open the thread
  • “We also might consider the self-hosted options once we have a more reliable stream of users.”
    LangChain forum · 13 July 2026 · in production · open the thread
  • “Eventually I discovered DBOS and now all my personal projects are on DBOS.”
    Hacker News · 4 May 2026 · open the thread
  • “I know this because I used LangGraph in 8 out of 10 AI projects I built”
    dev.to · 23 April 2026 · open the thread

  • Hit this one too? We are building for it. Join the waitlist.

  • “I switched to the Vercel AI SDK with a hexagonal architecture”
    dev.to · 23 April 2026 · open the thread
  • “I chased this demon early-days in my multi-agent orchestrated harnesses. you'll need a state machine. i used locally hosted temporal.io.”
    Hacker News · 26 February 2026 · open the thread

  • Hit this one too? We are building for it. Join the waitlist.

Method

We collected 448 public posts published after 1 November 2025 in which a builder describes document AI failing. Each link was re-opened on 8 November 2026. We kept the 290 where the quote is on the page, the author describes an incident and not an opinion, and has no tie to a vendor. Quotes are verbatim and trimmed after 420 characters. The grouping is ours. A complaint is not a measurement.