Skip to main content
You do not need to be a server expert to use StackKits, but a few ideas make the first hour much easier. This page explains them and tells you what to prepare.

​
What a homelab is

A homelab is a computer that stays on and runs programs for you and your household. Instead of storing photos, files or passwords with a company, you keep them on a machine you own. StackKits installs and connects the programs for you. A kit is the starting point. A Basement Kit is for a computer in your home. A Cloud Kit is for a server you rent and already operate. If you are unsure, start with the Basement Kit. See Choose a kit.

​
What you need

1

A computer that can stay on

Any computer you control that can run day and night, for example a mini PC. Check the list of operating systems that have been tested in OS compatibility. Use one of the listed systems.
2

Access to the command line on that computer

The setup is one command that you paste into a terminal. You do not need to understand it, but you must be allowed to run it on the computer.
3

Your home network

The computer and your phone or laptop must be on the same network at first. StackKits does not change every device or your router on its own. The default local domain is home.test, so your devices must be able to resolve names under it before the addresses open.
4

A private place for the access details

Setup creates access details in the file .stackkit/access.json. Keep them private and do not send them in chat or by e-mail.
You do not need a kombify account, a credit card or a rented server.

​
What happens during setup

  1. The installer downloads the released StackKits and the software it needs.
  2. It creates a folder, ~/my-homelab, and a local owner for your homelab.
  3. It checks the configuration and starts the default services.
  4. You open the Node Hub and finish protecting it. See Node Hub.
You can read the same steps in more detail in the Quickstart.

​
What to do right after

  1. Create your owner passkey in PocketID as shown in the Node Hub guide.
  2. Set up a backup and try one restore: Back up and restore.
  3. Add one use case. Documents & Files is a good first one.

​
Where you can get stuck

StackKits is software you operate yourself. You decide what runs, you approve changes that alter the stack and you keep the backups. The documentation says for each use case how well it has been tested.