Architecture
Indexlume 0.1.0 runs six cooperating services on one Compose host:
| Service | Responsibility |
|---|---|
| Web | Next.js operator console. |
| API | Authentication, RBAC, configuration, search proxy, and job commands. |
| Worker | Upload, PostgreSQL sync, projection snapshot, and reconciliation processing. |
| PostgreSQL | Accounts, workspaces, configuration, encrypted credentials, jobs, and audit data. |
| Redis | Durable job queue and operational state. |
| Typesense | Search collections and documents; bundled or external. |
The API applies pending Prisma migrations before it starts. The worker waits for healthy API, PostgreSQL, Redis, and Typesense services. Upload staging is a named volume shared by API and worker.
Data boundaries
Connector credentials are encrypted before entering PostgreSQL. Public search keys are shown once and stored as keyed hashes. Indexed source records are processed by the worker and stored in Typesense. Aggregate analytics omit raw query text.
Supported deployment model
The documented production boundary is one self-hosted Compose machine. Horizontal API/worker scaling, managed object staging, and orchestrated multi-node deployments require deployment-specific work and are not described as supported defaults.