Code context
Tree-sitter parsing, semantic chunking on symbol boundaries, hybrid retrieval (BM25 + vector + 1-hop symbol graph). Not naive sliding-window RAG.
How retrieval works →Prometheus is an EU-hosted MCP server and indexer worker that gives your AI agents typed, scoped, governable access to your codebase. Bring your own model — Claude, Gemini, OSS via vLLM. No data leaves the EU without your per-tenant opt-in.
Three pieces, one substrate. Each is replaceable; together they let an agent reason about a real codebase without dragging the entire repo through every prompt.
Tree-sitter parsing, semantic chunking on symbol boundaries, hybrid retrieval (BM25 + vector + 1-hop symbol graph). Not naive sliding-window RAG.
How retrieval works →MCP server with six typed tools (search_code, get_symbol, find_references, expand_context, get_file, list_changed_since). Stdio + HTTP-SSE.
Browse the tools →Supabase eu-central-1, Railway europe-west4, Resend eu-west-1. Per-tenant region mode pins which providers may ever see your code.
Region modes explained →Your IDE talks to a local MCP client. The client speaks MCP-over-stdio to Prometheus, which fans out to the hosted indexer-worker on Railway EU and Supabase pgvector in Frankfurt.
We ship in narrow vertical slices and document each one in the changelog. The pieces below are public-beta-quality; the rest is on the way.
Proprietary, EU-hosted, no data leaves the EU without a per-tenant opt-in. Embeddings, vectors, symbol graphs and source snippets stay inside the Supabase project you point us at. Provider keys are tenant-scoped; you can rotate or revoke any time.
We're onboarding agentic-coding teams in small waves. Drop your email — we'll send setup instructions and an API key when your tenant is ready. No marketing, no tracking, no third-party scripts.