Unearth separates its public website and documentation from the application runtime. The core application accepts provider-neutral configuration and can run on Docker hosts or Node.js infrastructure with PostgreSQL and Redis.
Repositories
| Repository | Owns |
|---|---|
| Website and docs repository | The marketing website at unearth.chat and documentation for docs.unearth.chat |
unearth-chat-app | Authenticated Next.js web app, Fastify API, workers, shared server packages, schema migrations, and deployment configuration |
Runtime services
| Service | Responsibility |
|---|---|
| Web | Authenticated research workspace and account interface |
| API | Authentication, organization access, research requests, and queue producers |
| Worker | Background jobs, ingestion, and recurring work |
| PostgreSQL | Application records, research state, and published dataset metadata |
| Redis | Queues and shared runtime coordination |
| Artifact store | Source artifacts shared by the API and worker |
| Migration job | Pending database schema changes before application startup |
Deployment choices
Docker Compose provides a complete starting point. Services can also run separately on infrastructure that provides their runtime, storage, and network requirements. Railway is an optional deployment adapter; it is not required by the core application.
Marketing and documentation have their own deployment lifecycles. Updating either does not deploy the application, change its database, or activate ingestion.