Download SecureEyes Hub

Put the Hub on a Raspberry Pi, a mini PC or a Proxmox host, and it records your cameras around the clock to a disk you own. It connects to each camera once and shares that stream with the whole house. It needs a Pro licence, and viewing from outside the house arrives when our relay opens.

Looking for the iPhone, iPad or Mac app? Get SecureEyes on the App Store.

$ curl -fsSL https://get.secureeyes.app | sudo sh
== downloading secureeyes-hub_0.12.6_arm64.deb
== sha256 verified
== installing
SecureEyes Hub is installed and running.

Install with one command

The installer is POSIX shell, so it runs on whatever the machine already has. Nothing of ours needs to be installed first.

curl -fsSL https://get.secureeyes.app | sudo sh
  1. 01Open a shell on the Linux machine that will run the Hub. It needs to stay on, and it needs to reach your cameras.
  2. 02Run the command above as root. It works out whether the box is arm64 or amd64, verifies the signed release manifest, downloads the matching package, checks its sha256, and installs it.
  3. 03Scan the code on the Hub's screen, or on its web page at port 8443, with SecureEyes on the device that has Pro. The app claims the Hub and activates Pro for it over the internet.

Step by step, with what the screen shows and what to do when a scan fails: Set up a new Hub.

To install by hand instead, download the package for your architecture below and install it with sudo apt install ./secureeyes-hub_0.12.6_<arch>.deb.

Builds for arm64 and amd64

Version 0.12.6, published 30 Oct 2026. Every package is named by a signed manifest and carries the sha256 below, so you can check what you downloaded before you install it.

Archived builds →

Linux arm64 v0.12.6

Raspberry Pi 5 and other ARM boards running Raspberry Pi OS, Debian or Ubuntu.

Linux amd64 v0.12.6

Intel and AMD mini PCs and servers running Debian or Ubuntu, and Proxmox hosts.

Coming later: the Hub on Mac and Windows

Today the Hub runs on Linux: a Raspberry Pi, a mini PC or a Proxmox host. Versions for Mac and Windows follow once the Linux release has settled.

How much disk, and what box?

Answer four things and this gives you the disk, the memory and the class of machine. The bitrate the sums need is carried by the quality choice, and shown under Advanced if you want to change it.

What are you recording?

What the Hub records unless you tell it otherwise. Measured between 0.4 and 1.5 Mbps across the reference cameras.

Does the Hub also show them on a screen?
Per day43 GB5.4 GB per camera
14 days605 GBof footage
Disk637 GBthe disk this needs, with the free space the Hub always keeps
What will run itAny of themRecording is a copy of what the camera sent, so the box barely notices. Every host family the Hub knows will do it. No GPU needed: recording is a copy of what the camera already sent, so nothing is decoded.

These are a starting point, not a promise. On the reference hub two cameras of the same model shipped substreams three times apart, so no table can tell you what your own footage costs. Your Hub measures what your own cameras cost once they have recorded, on the Storage tab.

What the Hub needs

It is a compiled Dart service that drives go2rtc and FFmpeg, with a separate renderer for a wall on a screen. Any always-on 64-bit Linux machine with systemd that can reach your cameras will do.

What the Hub does →