Infrastructure
Services are separated by responsibility, failure domain, and data ownership.
The topology supports independent frontend, API, agent, ingestion, graph, vector, cache, and object-storage concerns while keeping the backend as the operational control plane.
Runtime responsibilities
The frontend runs on Vercel with global CDN delivery. The backend API, PostgreSQL with pgvector, and Redis are deployed on Render Cloud as Docker containers. Neo4j runs in development via Docker Compose and is disabled on the free Render tier. Document storage uses S3-compatible object storage (MinIO in development, configurable in production). A standalone cross-encoder reranker can be deployed on Hugging Face Spaces for production use. Migration execution is isolated from API startup.