Services on JUNC1
JUNC1 runs a full self-hosted service stack inside its Ubuntu VM, as Docker Compose stacks. Quorra integrates with these services — she doesn’t replace them; she talks to their local APIs on your behalf.
This page is the deployment view: what runs on the box. For how Quorra uses each service — the tools, permission tiers, and integration design — see Quorra’s service integrations reference.
The stack
| Service | Purpose | Quorra integration |
|---|---|---|
| llama.cpp | Local LLM serving (Qwen 3 14B) | Core — Quorra’s inference runtime |
| Authentik | SSO / identity provider | Infrastructure — canonical user identity |
| Synapse | Messaging — Quorra’s chat interface | Integrated — Matrix bot adapter |
| Actual Budget | Personal finance | Integrated — conversational logging |
| Nextcloud | File storage, calendar, contacts | Planned |
| Jellyfin | Media streaming | Planned |
| Radarr / Sonarr | Movie / TV management | Planned |
| Home Assistant | Home automation | Deferred |
| Gitea | Code hosting | None planned |
Immich (photos.juncyard.com) | Photo backup + ML | Planned (low priority) |
Open-WebUI (quorra.juncyard.com) | ChatGPT-style LLM chat | Integrated — Pipe adapter |
QuorraAPI itself — the service that is Quorra — runs in its own Compose stack alongside these. It’s documented in the Quorra section, not here.
Integration status
| Status | Meaning |
|---|---|
| Core | The service Quorra fundamentally depends on |
| Integrated | Quorra can act on this service today |
| Planned | Service is running; Quorra integration designed but not yet built |
| Deferred | Integration intentionally postponed |
| None planned | Service runs on the junc, but no Quorra integration is intended |
Integration work is tracked in Quorra’s milestone tracker (milestone M4).