Skip to main content
A use case is something your household relies on, such as a photo library or a password vault. Each one runs as a workload on a kit you already verified, and one or more applications provide it. Your kit brings sign-in, routing, the Node Hub and backups; a use case adds the application on top. No use case is selected by the initial StackSpec. You choose the ones you want.

​
The twelve main use cases

Marketplace is owned by StackKits. Techstack presents its selection card when the pinned published catalog makes it available. You run third-party applications on your own homelab, including owned hardware or rented cloud servers; kombify does not host them. A separately named managed serverless offering is the exception. Komodo is an operations platform without a store. “Available, lifecycle-verified” means the current release has a public Depot producer receipt: install through restore passed on the tested operating system, and the run’s support grade is published on stackkit.cc/compatibility. “Available, not yet lifecycle-verified” means you can select it in the catalog today, but no lifecycle receipt covers it yet. “In development” means the release declares it but it is not installable yet. “Planned” means it is a target design with no release yet and no committed date. The use-case catalog lists every use case the current release declares, generated from the published manifest. It has no maturity field of its own; read status from this page. OS compatibility has the lifecycle evidence behind “lifecycle-verified”.

​
How a use case is added

  1. Start from a verified kit. The Quickstart sets up a Basement Kit.
  2. Plan storage and recovery on the use-case page.
  3. Select the workload in your StackSpec, then follow Add a workload to establish secret custody, generate, apply and verify.
  4. Finish the setup on the application page and try one real task, such as uploading a photo.
  5. Practice a restore before the use case holds data you cannot replace. See Back up and restore.
Documents & Files is a good first use case, because Cloudreve’s standalone selection needs no secret reference.