An existing homelab usually contains valuable decisions, experiments, and running services. StackKits should help you make that environment clearer, not force a rebuild.
This guide is for the moment when the user does not need a blank slate. They need a safer way to understand what already exists and decide what should become managed, documented, or replaced.
What this guide helps you decide
- which parts of the existing setup should stay untouched
- which responsibilities StackKits should take over first
- whether the environment is still one coherent setup or already hybrid
- how to avoid mixing generated resources with manual experiments
Before you add StackKits
Inventory what already exists:
- servers and operating systems
- Docker or compose projects
- DNS names and reverse proxies
- identity or auth layers
- backups
- monitoring
- public routes
Keep manual and generated resources separate
The safest adoption path is to keep StackKits-generated resources separate from manually managed stacks until you are ready to migrate.
Use clear boundaries:
- one project directory for generated StackKits output
- separate compose projects for manual experiments
- documented DNS ownership
- explicit backup ownership
Start with one responsibility
Do not migrate every service at once. Choose one responsibility:
- expose a Node Hub
- standardize monitoring
- add local DNS
- add a password vault
- deploy a new app platform
The best first responsibility is the one that makes the whole homelab easier to understand. For many setups, that is service discovery, monitoring, local DNS, or backup clarity.
Recommended direction
Most existing homelabs should start with Base Kit and selectively enable capabilities. Move toward Modern Homelab only when local and cloud environments both matter.
If your current setup is fragile, use StackKits first as a reference and
planning model. Deploy after you understand which services should move.
How this maps to the finder
Selecting “Add to an existing setup” increases the fit for Modern Homelab when you also select hybrid infrastructure, multiple servers, or many use cases. If the setup is still one environment, Base Kit remains the safer first step. 