TailHome
Install

Your cloud. At home.

A private cloud
that feels effortless.

One command turns your home server into a secure, observable service stack—available anywhere on your Tailscale network.

Copy the install command See the walkthrough

Linux full stack

curl -fsSL https://tailhome.blackielabs.com/install.sh | bash

No port forwarding No subscription MIT licensed
01

Install

Run one inspectable shell command on a supported Linux host.

02

Connect

Sign in to Tailscale and add the host to your private tailnet.

03

Operate

Use the tailhome CLI to check, update, and back up the stack.

Installation walkthrough

See the whole setup
before you run it.

Follow the real TailHome path from the hosted command and interactive choices to a healthy private service dashboard.

24 second walkthroughCommand → setup → running services

Start building

Copy one command. Run it on Linux.

The default install is the complete TailHome stack. macOS and Windows get the CLI; service profiles stay available after install when you want a lighter host.

Installer

Shell command for the Linux full stack installer.

Use the same Linux installer on x86, ARM, and Raspberry Pi hosts.
curl -fsSL https://tailhome.blackielabs.com/install.sh | bash

After you copy it

  1. Paste the command on a supported Linux host: Raspberry Pi OS, Debian, Ubuntu, x86, or ARM.
  2. Complete the Tailscale login prompt so the host joins your tailnet.
  3. Open Homepage with tailhome urls; it prints the resolved local and private URLs.

Fresh Linux installs enable monitoring, uptime, management, and DNS by default. For a lighter install, run with TAILHOME_PROFILES=monitoring for a subset or TAILHOME_PROFILES= for core-only.

Inspect the installer source and documentation before running it.

Installation ledgerEverything the command changes, in the open.
03 checks
01

Deploy

Checks ports, installs dependencies when needed, creates the Compose stack, and starts the enabled services.

02

Store

Keeps Compose files, configuration, and environment values together in /opt/tailhome; the CLI lives in /usr/local/bin.

03

Protect

Generates credentials for Grafana and Pi-hole when those services are enabled, and hides secrets when the CLI prints environment values.

Full stack host Raspberry Pi OS · Debian · Ubuntu · Linux ARMRemote CLI macOS · Windows

The private path

Reach home.
Never expose it.

Your device reaches TailHome through Tailscale’s encrypted mesh. The host stays yours, and services remain on your hardware instead of moving into someone else’s cloud.

No port forwarding required. Access is governed by membership and policy in your tailnet. TailHome does expose ports on the host, so keep your firewall rules limited to trusted networks.
YouPhone or laptop
encrypted
Your tailnetTailscale mesh
private
Your hardwareTailHome host
Homepage · coreCaddy · coreMonitoring · profileDNS · profile
Identity-aware access in. Private Docker services behind your TailHome host.

Everything connected

Your essential services,
already talking.

Install the full current TailHome stack by default: dashboard, gateway, monitoring, uptime, container management, and DNS. Compose profiles stay available when you want to opt out of a group.

H

Homepage

tailhome:3000

core
C

Caddy

tailhome:8088

core
G

Grafana

tailhome:3001

profile
P

Prometheus

tailhome:9090

profile
N

Node Exporter

tailhome:9100

profile
U

Uptime Kuma

tailhome:3002

profile
P

Portainer

tailhome:9443

profile
P

Pi-hole

tailhome:8080

profile

One calm interface

Control the whole house from one command.

A small, fast Go CLI handles the everyday work. Human-readable output, predictable commands, zero dashboard hunting.

statusSee every container at a glance
urlsOpen private service endpoints
updatePull, restart, and keep moving
backupArchive the complete install
uninstallRemove the stack, files, and CLI

tailhome — status

$ tailhome status

TailHome

home server control plane

SERVICEPORTSTATEhomepage:3000● runningcaddy:8088● runninggrafana:3001● runninguptime-kuma:3002● runningpihole:8080● running

✓ default stack healthy in 18ms

Proof, not promises

Infrastructure you can inspect and own.

TailHome keeps the machinery visible: Compose files you can reproduce, commands you can read, and backups you control.

Inspect the source
01

Open source

The installer and CLI are published under the MIT License.

02

Self-hosted

Services and their data run on hardware you control.

03

Generated passwords

Service credentials are created at install, not shipped as shared defaults.

04

Portable backups

tailhome backup archives the complete install directory with a timestamp.

Questions, answered

Clear before you commit.

From a first Raspberry Pi to an established home server, the same configuration remains readable and yours.

What can I use TailHome for?
Run a private dashboard, monitoring, uptime checks, DNS filtering, container management, and reverse-proxy shortcuts for your household or homelab.
Does it open my server to the internet?
TailHome does not require router port forwarding. Services bind on the host, so use Tailscale and appropriate firewall rules to restrict who can reach them.
Can I see or change the configuration?
Yes. The generated Docker Compose and service configuration live under /opt/tailhome by default, making the install inspectable and reproducible.
How do updates and backups work?
Use tailhome update to pull and restart services, and tailhome backup to create a timestamped archive of the complete TailHome directory.
How do I uninstall?
Run tailhome uninstall --yes. That stops the Compose stack and volumes, removes /opt/tailhome, the CLI binary, and TailHome’s Tailscale systemd drop-in. Docker and Tailscale stay installed.
Where is the documentation?

Your cloud starts at home

Ready to make your server yours?

Copy the install command View on GitHub