Persona: The Self-Hosting Tinkerer¶

Summary¶

A software developer or DevOps engineer who runs a home server as both a hobby and a principled stance on data sovereignty. They enjoy configuring infrastructure, optimizing Docker stacks, and owning every byte of their personal data. They chose Loryth because it replaces a patchwork of self-hosted apps (Firefly III, Mealie, Vikunja) with a single integrated platform.

Demographics¶

• Age range: 28-40
• Occupation: Software developer, DevOps engineer, or sysadmin
• Technical comfort: Expert
• Household: Lives alone or with a partner
• Devices: Linux desktop, Android phone, home server (Intel NUC or Raspberry Pi cluster)

Goals¶

• Consolidate fragmented self-hosted apps into one platform with a unified data model
• Maintain full control over personal data — no cloud dependency, no telemetry
• Contribute to an open-source project they actually use daily
• Automate recurring workflows (grocery reordering, budget alerts) via APIs

Frustrations¶

• Each self-hosted app has its own auth, database, backup process, and update cadence
• Data lives in silos — shopping list app can't talk to the budget tracker
• Most "unified" platforms are either proprietary or too opinionated about hosting
• Poor API documentation in many OSS projects makes automation painful

Loryth Usage¶

• Self-hosting reality: Runs Docker Compose on a dedicated home server with automated backups and Watchtower for updates
• Primary device: Linux desktop (web app) for planning; Android phone for quick capture
• Usage frequency: Daily
• Typical session: Morning — review wallet dashboard and grocery inventory; evening — log expenses and plan tomorrow's meals

Key Scenarios¶

Scenario 1: Weekend Grocery Run¶

Checks the grocery inventory for items running low. Plans three recipes for the week, and Loryth generates a shopping list from missing ingredients. After the trip, marks the shopping trip as completed — inventory updates automatically, and the total spend appears in the wallet as a categorized expense.

Scenario 2: Monthly Financial Review¶

Opens the wallet dashboard on the first of the month. Reviews spending by category, compares against the budget, and checks progress on the "emergency fund" savings goal. Notices the grocery category is over budget and drills into individual transactions to understand why.

Scenario 3: Contributing a Bug Fix¶

Encounters a bug in the KB search feature. Clones the repo, reproduces the issue with the integration test suite, fixes it, and opens a PR. References the relevant issue from the issues service — they're also tracking their own backlog in Loryth itself.

Relevant Services¶