Install Bitsmith

Bitsmith installs as a native Linux service with one command. The installer sets up the Bitsmith service plus the system packages it relies on (Docker, Samba, and ZFS), then starts serving its web interface over HTTPS.

Requirements

• A 64-bit machine running Ubuntu 22.04+ (amd64 or arm64). A Raspberry Pi works if it’s running Ubuntu for ARM, not Raspberry Pi OS.
• An amd64 or arm64 processor.
• Root access (the installer runs with sudo).
• One or more drives for storage, separate from the disk the OS runs on.

Install

Run the installer as root:

curl -fsSL https://downloads.bitsmith.app/install.sh | sudo bash

If you prefer wget:

wget -qO- https://downloads.bitsmith.app/install.sh | sudo bash

The installer detects your distribution and processor, installs dependencies, registers the bitsmith service, and starts it.

Options

Pass flags through to the installer:

curl -fsSL https://downloads.bitsmith.app/install.sh | sudo bash -s -- --skip-deps

• --version <tag> installs a specific release, for example v2026.4.19.
• --skip-deps skips installing Docker, Samba, and ZFS. Use this if you manage them yourself.
• --skip-start installs the files but doesn’t start the service yet.
• --yes accepts package installs without extra prompts.

Open the web interface

Once the service is running, open Bitsmith in a browser at your server’s address:

https://<your-server-ip>

Bitsmith serves over HTTPS with a self-signed certificate on first run, so your browser warns you the first time. That’s expected for a fresh local server. Continue past the warning to reach the setup screen.

Tip

Not sure of your server’s address? On the server, run hostname -I and use the first address it prints.

The certificate warning

The warning appears because the certificate is self-signed (created by your server, not a public authority your browser trusts). The connection is still encrypted; the browser just can’t vouch for who issued it. To remove the warning, from simplest to most polished:

• Accept it once per browser and move on. Fine for a server only you use.
• Trust the certificate on your devices by adding Bitsmith’s certificate to the system trust store. The warning disappears on those devices.
• Use a real certificate. If you reach your server through a domain name, install a certificate from a public authority (for example via your reverse proxy or DNS provider) so every device trusts it with no extra setup.

Reaching it from outside your home

Bitsmith is built to live on your home network. To reach it while away, prefer a private network like Tailscale or a VPN rather than exposing it directly to the internet. That keeps the server private and gives you an encrypted path in, which also covers the MCP endpoint.

Next step

The setup screen walks you through your license, your admin account, the network bridge, and your first storage. Continue with First-run setup.