Why it is here: Quick notes and attachments with controlled account registration. Review each note visibility setting and keep uploaded files with the database.
Guide
A personal workspace on your server
Notes, a structured wiki, tasks and developer utilities, with an optional local AI interface. Start with one tool and keep account access and backups explicit.
Give each tool one job
Use Memos for short notes, BookStack for material with structure, and Vikunja for things that need an owner or a next action. You can start with one application; deploying every pick is not a prerequisite for a useful workspace. IT Tools is a separate browser toolbox rather than a shared account system.
Protect the working record
Keep private documents and attachments under the intended account permissions. Set up each administrator privately before enabling wider access. A password on one service does not protect the others. Backups must contain the database, uploaded files and relevant credentials; restore a note, a wiki page and a task on a clean destination before relying on the arrangement.
Add local AI only when it serves a clear need
Open WebUI adds model downloads, disk and RAM requirements and a separate model license. A local interface is not by itself proof that every feature keeps data local: external providers, web search and plugins change the data flow. The recipe’s small CPU inference test does not establish production quality, GPU performance or accurate document retrieval.
Sets
What is in the set
The sum of the minimums the recipes below declare. It is a floor, not a recommendation: leave room for the operating system, backups and growth.
Why it is here: Use books, chapters and pages when the material needs a stable structure and access roles. Recovery needs both the database and uploaded files.
Why it is here: Tasks and projects rather than another place to store documents. Preserve attachments with the database; reminders, recurring schedules and external login were not part of the current smoke coverage.
Why it is here: Small format and encoding utilities served locally. There are no native accounts and no server copy of browser preferences or persisted inputs. The latest stable upstream image is from 2024.
Why it is here: Optional chat interface backed by a separately stored local model. The recipe verified a small CPU model, not GPU capacity, answer quality or retrieval accuracy. Review model licenses and external integrations before adding private documents.
Categories in this guide
Other guides
- A home server that earns its keepA modular home-server starter set: passwords, DNS, sync, monitoring, notifications, media and household recipes. Choose the services you need and add them gradually.
- Applications with a minimum of 1 GB RAM or lessSmall declared resource requirements for a VPS or thin client, with new metrics, notifications, notes and utility recipes. The limit applies to each application separately.
- What a Raspberry Pi can actually runA shortlist for 32-bit ARM systems, plus the newer options a 64-bit Pi can consider. Check the actual architecture test result before choosing a recipe.
- Services that never need a public addressKeep household services behind loopback, a private network or a VPN. Private access still needs application authentication, safe initialization and backups.
- A family cloud without the subscriptionFiles, photos and device sync for a household. Decide who holds each copy, how access is granted and where the off-server backup lives.
- A media library you ownFilms, music, audiobooks, podcasts and photographs from your own files. Match clients, storage and transcoding needs before choosing the server.
- Knowing when your server stopsAvailability checks, server-resource history, notification delivery and a shared dashboard serve different jobs. Build only the layers you need and monitor from outside the server.