Near-Zero Cash Technical Self-Host
Trade skilled operator time for a minimal self-hosted control plane
A near-zero software-license architecture for a technical independent operator who can maintain a small server, document manual controls, and keep payments outside the stack.
Budget band
near-zero · self-host heavy
Components
| Tool | Role in stack | Required |
|---|---|---|
| caddy | TLS termination and reverse proxy | yes |
| vaultwarden | Staff credential vault | yes |
| bookstack | SOP and member FAQ source | yes |
| uptime-kuma | Service availability checks | yes |
| restic | Encrypted offsite-capable backups | yes |
| espocrm | Tour and sales pipeline record | yes |
| listmonk | Optional newsletter delivery through approved SMTP | optional |
| freescout | Optional shared support inbox | optional |
Assumptions
- A named person can maintain Linux and containers.
- Manual payment reconciliation is acceptable during the pilot.
Risks
- A single-host outage can interrupt several workflows.
- Labor and email-delivery costs can exceed a small SaaS subscription.
Getting started
- inventory-current-records
- choose-one-pilot-workflow
- deploy-with-test-data
- prove-backup-restore
- train-staff-before-member-data
Audience
Roles: owner-operator, technical-operator, operations-manager
Problems: reduce-software-cost, self-host-for-data-control, replace-spreadsheets, disaster-recovery
Workflows: member-onboarding, tour-to-close, backup-restore-drill, incident-response
Last reviewed: 2026-07-18