Self-hosted workspace
Your own
workspace.
Docs, tasks, files, diagrams, spreadsheets and chat - running on your hardware. A working Docker Compose stack, pinned and documented, instead of ten READMEs and a per-seat bill.
The stack
The tools your team uses daily.
Knowledge, work, files, diagrams, communication. Every component is MIT, Apache-2.0 or MPL-2.0, verified by SPDX id.
Knowledge
Wiki that non-technical people will use
Spreadsheet that behaves like a database
Work
Simple, fast kanban task boards
Files
Peer-to-peer file sync, no cloud
Web interface over your storage
Diagrams
Hand-drawn style whiteboard
Technical diagramming engineers know
Communication
Threaded chat by topic, not channel
Video meetings with no time limits
Personal
Envelope budgeting you host yourself
Pricing
Start with docs and tasks. Add as you grow.
One-time purchase, instant delivery, free updates. Each tier ships its own bundle and its own course.
Notes & Tasks
Documentation and a task board you own.
- 2 components: BookStack, Kanboard
- Working docker-compose.yml
- verify.sh health check
- RUNBOOK.md
- Pinned source fetch
Files & Diagrams
Adds file sync, a file manager and a whiteboard.
- 5 components: adds Syncthing, File Browser, Excalidraw
- Everything in Notes & Tasks
- Sync setup guide
- Diagram guidance
Full Workspace
Spreadsheets and real chat on top.
- 8 components: adds Grist, Draw.io, Zulip
- Everything in Files & Diagrams
- Threaded chat explained
- Workspace architecture guide
Comms + Support
Video meetings and budgeting, plus help.
- 10 components: adds Jitsi, Actual Budget
- Everything in Full Workspace
- Jitsi reverse-proxy setup
- 30 days priority support
Complete + Onboarding
All ten, plus a 1:1 session.
- All 10 components
- Everything in Comms
- 1:1 onboarding session
- Lifetime updates
What's inside
The integration layer, done properly.
docker-compose.ymlThe stack, wired and health-checked.env.examplePinned image tags for reproducible deploysverify.shProves each service is serving, not just runningRUNBOOK.mdTroubleshooting, backups, sizing, Jitsi setupATTRIBUTION.mdEvery licence and pinned commitfetch-sources.shUpstream source at exact commitsdocs/One page per componentStop paying per seat for your own knowledge.
Bring the stack up, keep your documents and conversations where they belong.
Get the stackFAQ
Straight answers.
Why not Nextcloud, Immich, Mattermost or Cal.com?
Licence. All are AGPL or source-available, which means they cannot be redistributed in a paid bundle. Several are excellent - Nextcloud and Immich especially. It's a licensing constraint, not a quality judgement. Every component here is MIT, Apache-2.0 or MPL-2.0, verified by SPDX id.
Isn't this all free anyway?
Yes. Every component is open source and freely available upstream. What you're buying is the integration: a stack that comes up, the runbook, the setup guides for the parts that catch people out, and the knowledge of what to install first.
What hardware do I need?
2 GB RAM for notes and tasks. 4 GB adding files and diagrams. 8 GB adding chat. Jitsi needs a real domain and TLS, plus UDP 10000 for media.
Do I need all ten?
No. BookStack and Kanboard cover the first two things every team needs. Add files when they follow, chat when it outgrows a group message, and video last - it's the most operationally demanding piece here.
Is Syncthing a backup?
No. Sync propagates deletions - if you delete a file on one machine it disappears on the other. Turn on per-folder versioning and keep separate backups. The runbook says so explicitly.
Is my data really private?
Your documents, files, conversations and financial records stay on your hardware. That's the point. It doesn't make you secure by default - several of these ship with default credentials, so change them and put a reverse proxy in front before exposing anything.