Documentation
Overview
What Prometheus is, what it does, and the moving parts you should know about before you wire it up.
Prometheus is a sovereign, EU-hosted code-context engine for AI agents. It gives your agent typed, scoped, governable access to a codebase via the Model Context Protocol — without shipping the source to a third-party SaaS.
The three components
@prometheus/context-mcp— a small MCP server that runs on the developer machine (or in CI) and speaks stdio. It exposes six tools:search_code,get_symbol,find_references,expand_context,get_file,list_changed_since.prometheus-indexer-worker— a hosted HTTP service that walks a workspace, parses it with Tree-sitter, chunks per symbol, embeds the chunks with Voyage AI (voyage-code-3, 1024-dim), and persists into Supabase Postgres withpgvector. Public endpoint:https://api.prom.codes(Vercel Edge proxy in Frankfurt, forwarding to the Railway-hosted worker).- Supabase Postgres (eu-central-1) — multi-tenant storage for symbols, references, embeddings, and per-workspace metadata. Row-level security keeps tenants isolated.
Where the data lives
| Stage | Provider | Region |
|---|---|---|
| MCP server (your machine) | local stdio | wherever you sit |
| Indexer worker | Railway | Frankfurt (EU) |
| Storage | Supabase Postgres + pgvector | eu-central-1 |
| Embeddings (default) | Voyage AI voyage-code-3 | us |
| Web + waitlist | Vercel fra1 | Frankfurt (EU) |
The only US hop is the embedding call. We document this explicitly in
Region mode and ship eu-strict as a
per-tenant override that swaps Voyage for an EU embedding endpoint
(RunPod-hosted, planned for general availability in Phase 3).
Status
Prometheus is in private beta. The indexer worker, MCP server, embeddings bench, and Supabase schema are live; the authenticated dashboard, the CLI agent, and the VS Code plugin are still in the build queue. The Quickstart walks you through the working surface today.