haystack
Open-source AI orchestration framework for building context-engineered, production-ready LLM applications. Design modular pipelines and agent workflows with explicit control over retrieval, routing, memory, and generation. Built for scalable agents, RAG, multimodal applications, semantic search, and conversational systems.
Runssource: GitHubhomepagePythonApache-2.0commit 124b668001cd
Python, Apache-2.0 licensed. The project labels itself: agent framework, agentic ai, agentic rag, agents, ai, ai agents, context engineering and framework.
haystack runs. An Argusic agent installed it in 5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Haystack 3.3.0-rc0 installed and buildable, 6569 unit tests pass, Pipeline/InMemoryDocumentStore/retrievers/ChatMessage/serialization all work correctly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 5 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest -m 'not integration' --no-header -q exited 0, 6569 passed, 10 skipped; hatch build produced wheel+sdist; verification script exercised Pipeline creation, DocumentSplitter, InMemoryDocumentStore read/write, InMemoryEmbeddingRetriever, ChatMessage, and serialization roundtrip without errors
- Model tokens used
- 204,869
- Exact commit tested
- 124b668001cd
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# Estimate total run time from available output # First command started approximately when hatch env prune ran print(\"Approximately 4 minutes total elapsed\") PYEOF python3 /tmp/check_time.py" in /work/repo succeeded in 0ms: 1790353506 Approximately 4 minutes total elapsed Here's the compilation of my results: tokens used 204,869 Here's the compilation of my results:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 5 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 agent-framework projects Argusic has installed and timed, haystack was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 5 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-frameworkagentic-aiagentic-ragagentsaiai-agentscontext-engineeringframeworkgenaigenerative-aiinformation-retrievallarge-language-modelsllmmcpmulti-agentorchestrationpythonragretrieval-augmented-generationsemantic-search
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/haystack)Questions
- Does haystack run?
- Yes. haystack runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test haystack?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 124b668001cd. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test haystack?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does haystack take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does haystack need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing haystack?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does haystack compare with the alternatives?
- Of the 5 agent-framework projects Argusic has installed and timed, haystack was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
- Where is the evidence for haystack?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.