Skip to content

What each application is for

These are the services you actually use — the reason for the server rather than part of it. Every one of them expects Traefik to be running first; they publish no ports themselves and are reached through it.

Each one has a guide: installation, a Verify section, what to back up, how to update it, and the failures that service really produces. Each guide opens with when the stack last ran on a host; where its data has been restored from a backup, the guide and the catalogue say so. Every stack the repository ships, with or without a guide, is in the catalogue.

Most also ship a docker-compose.local.yml, which runs the service on your own machine with no proxy, DNS or certificate — see what every server needs. Adminer is the exception, because it needs a database to point at rather than one of its own.

The applications

Section titled “The applications”
Solves Also needs
Adminer a web interface onto a database another stack already runs a database to point it at
BookStack a wiki with real structure: shelves, books, chapters, pages nothing beyond the proxy
Cal.diY appointment booking pages people can self-serve — the Cal.com community edition SMTP for confirmation mail; Cloudflare recommended if it faces the internet
Collabora opening office documents in the browser inside Nextcloud, on LibreOffice, in one small container Nextcloud to embed it
Dashy one page linking everything you run, configured in a single YAML file nothing beyond the proxy
Documenso document signing you host yourself, with a signing certificate you generate SMTP, OpenSSL for the certificate
Easy!Appointments appointment booking on a PHP stack, with no build step nothing beyond the proxy
Ghost publishing with newsletters and paid memberships built in SMTP, which also gates the first login
Heimdall a launcher page for your services, with optional per-service status nothing beyond the proxy
Homarr a dashboard whose tiles show live state rather than only links API tokens for what it displays
Homepage a dashboard described in YAML files, reloaded on change nothing beyond the proxy
Immich photo and video backup from phones, searchable by what is in the picture storage for the library
Invoice Ninja invoices and quotes, what has been paid, and a portal where each client can view and settle them SMTP
IT-Tools formatters, generators and converters that never leave the browser nothing beyond the proxy
Listmonk newsletters, subscriber lists and double opt-in an SMTP relay entered after setup
Mailpit reading the mail a stack sends without a relay or a mailbox — accepted, kept, shown, never delivered nothing beyond the proxy
n8n chaining HTTP calls, webhooks and scheduled jobs into workflows visually nothing beyond the proxy
Nextcloud files, calendars and contacts on your own server, synced to desktops and phones, with sharing on top SMTP
NocoDB a spreadsheet interface and an API over a database nothing beyond the proxy
Ollama language models on your own hardware, pulled by name and served over an OpenAI-compatible API memory for the models; an NVIDIA GPU is optional
OnlyOffice opening .docx, .xlsx and .pptx in the browser, embedded inside another application an application to embed it — it is not used on its own
Open WebUI a chat interface with accounts, history and document upload in front of a model endpoint an OpenAI-compatible endpoint, such as Ollama
OpenProject work packages, Gantt charts, boards and time tracking nothing beyond the proxy
OpnForm a form builder with conditional logic, uploads and webhooks SMTP for notifications
Paperless-ngx scanned paper becoming a searchable archive, via OCR and a consume folder the OCR language packs you need; SMTP is optional
PhotoPrism a photo library that indexes and classifies itself disk space for the models
PrivateBin handing someone a password or a token through a link that is encrypted in the browser and can burn after reading nothing beyond the proxy
Seafile file sync and sharing with desktop and mobile clients SMTP for invitations
Seafile Pro file sync built for large directory trees, with full-text search and antivirus scanning a commercial licence; OnlyOffice for in-browser editing
Tymeslot booking pages against your own calendar, with the confirmation and reminder mail SMTP; provider credentials for Google, Outlook or Zoom
Vaultwarden credentials in one vault, synced to browser, phone and desktop, instead of a third party holding everything you log into SMTP, for email verification
Vikunja task management — boards, lists, Gantt and table views a local build step
Wiki.js a wiki organised by path, with per-page permissions and its own sign-in modules nothing beyond the proxy
WordPress the CMS, with PHP and Apache hardened an SMTP relay via plugin

Every guide names the version it is written against and what has not been exercised. Where a check against a specific version is on record, the date is shown with it; where none is, the guide says so instead. Read that before trusting a service with data.

Where the choice is not obvious

Section titled “Where the choice is not obvious”

Several of these solve overlapping problems. Nextcloud and Seafile both do file sync — one is a suite, the other is a sync engine, and the decision is not a matter of taste. Four dashboards differ mainly in how you configure them. Cal.diY, Easy!Appointments and Tymeslot book appointments with very different appetites for host resources.

Choosing between services →

What is deliberately absent

Section titled “What is deliberately absent”

The repository ships more stacks than have a guide. The table above lists the ones a guide has been written for; being on it says nothing about how much of a stack has been exercised — that is what each guide’s evidence line is for. Every stack, guided or not, is in the catalogue, grouped by purpose, with what has been checked on a host.

Where to go from here

Section titled “Where to go from here”

© 2026 SecDockBlueCode Apache-2.0Site content CC BY-NC 4.0