Quickstart
-
Start the stack
Bring up Postgres + Neo4j + API + UI with one command.
-
Verify readiness
Confirm
/api/readyis green before indexing or querying. -
Index your first corpus
Index a folder on disk into chunks/embeddings (and optional graph context).
-
Search
Run tri-brid retrieval (
vector + sparse + graph) and inspect results before moving into eval/tracing workflows.
User manual UI tour API reference
Default dev URLs
- UI:
http://127.0.0.1:5173/web - API:
http://127.0.0.1:8012/api
Ports are configurable
./start.sh honors BACKEND_PORT and FRONTEND_PORT. If you change ports, update your curl examples accordingly.
1) Start everything
From the repo root:
Optional: add observability (Prometheus/Grafana/Loki) if you’re going to tune or benchmark:
Advanced: on Apple Silicon, you can run Postgres natively (skip Docker postgres) for lower overhead:
See Native Postgres (macOS) for setup steps.
2) Verify the API is ready
curl -sS "http://127.0.0.1:8012/api/ready" | jq .
curl -sS "http://127.0.0.1:8012/api/health" | jq .
If readiness is failing, jump to Troubleshooting.
3) Confirm provider keys (optional but recommended)
ragweld can run without every provider key, but many features (embeddings, generation, cloud reranking) require at least one provider configured.
You can also see this in the UI at Admin → Secrets.
4) Index your first corpus
Pick a folder on disk and a stable corpus id (lowercase slug).
Graph is optional
If you haven’t configured Neo4j (or you want faster bring-up), you can still index and search using the Postgres-backed legs. Graph retrieval will degrade gracefully when unavailable.
5) Watch indexing progress
When status becomes complete, you’re ready to search.
6) Search
Next steps
- Learn what a corpus really means: Corpus vs repo_id
- Understand the retrieval legs and tuning knobs: Searching & answering
- Use the UI effectively: UI tour