A worker cooperative · open source · NixOS

Your home server.Your data. Your rules.

Fortress replaces Google Docs, Dropbox, Netflix and Ring with a self-hosted box in your house — reachable from anywhere, with every key on your own hardware.

Own your data★Remote access built in★One login for everything★No subscription lock-in
Replaces:
Google Docs → CryptPadNetflix → Jellyfin+ Radarr, Sonarr, Lidarr, ProwlarrGoogle Drive → Nextcloud

Your keys, your hardware

01

TLS and WireGuard keys never leave your house. Nobody else can decrypt your traffic — not even us.

Reachable anywhere

02

One encrypted tunnel to a box in the cloud. Jellyfin, docs, photos — from any phone, on any network, no port forwarding.

One login for everything

03

Every service signs in with the same account. Add a user once, they get every app — no per-app password sprawl.

Two ways in

Zero setup

Buy a box

We assemble, install and ship a pre-configured Fortress. Plug it in, connect ethernet, and claim it with your account in under five minutes.

  • Pre-installed NixOS + all services
  • Encrypted offsite backups included
  • Support from real humans
Bring your own hardware

Install on your machine

Fortress is a service stack, not a package. One config.nix, one apply. No setup wizard, no app store.

  • Free forever, AGPL-3.0
  • Run as many machines as you like
  • Same remote access as a box

Install on your own machines

Two ways to run fortress (ADR-035) — no Docker. Linux runs natively; macOS/Windows run a Linux VM.

1

Linux — native

system-manager applies the fortress services to your host's systemd (in place). OS/kernel updates stay yours.

curl https://proletariat.tech/install.sh | bash
2

macOS / Windows — a Linux VM

One Linux VM runs the fortress stack (system-manager inside); your Mac/PC is just hardware. Nix/systemd don't run on those hosts.

curl https://proletariat.tech/install.sh | bash
3

One config folder

Fortress lives in /etc/fortress/config — a git-versioned config.nix + sealed secrets. The dashboard edits it; applying re-reads it; git revert rolls config AND secrets back together.