SecureEyes Hub

The always-on half of your cameras.

A small service on a machine you own. It pulls each camera once, records to your own disk, and lets you reach the house from anywhere without opening a port. It needs a Pro licence.

What it does

Four jobs, all of them yours.

Nothing here reaches our servers. The Hub is on your network, the disk is in your house, and the one server involved carries traffic it cannot read.

01

One camera session for the house

Every viewer opening its own connection is what makes a camera stutter. The Hub pulls each camera once and serves everyone from that. On our own bench that took 26 sessions down to 15, and the two cameras on Wi-Fi stopped dropping out.

02

Records to a disk you own

Continuous recording, with a segment index and retention you set. It refuses to record onto the disk it boots from, because that wears the card out and the footage would be the thing you lose.

03

Answers why there is a gap

A hole in the timeline says which kind it is: the camera was not answering, recording was off, the disk stopped taking writes, or the Hub itself was down. A gap with no explanation is the thing that makes people stop trusting a recorder.

04

Your cameras from anywhere

Sealed end to end to your own Hub. The relay that carries it has no key for what it forwards, refuses anything unsealed, and stores nothing. No ports opened on your router.

Ready when you are

One line on the box.

Debian packages for arm64 and amd64, currently 0.3.22. The installer works out which one your machine needs, checks it against a signed manifest, and installs it.

Downloads and instructions →
Before you install
  1. 01
    A Pro licenceThe Hub validates a signed token and will not run without one.
  2. 02
    64-bit Linux with aptDebian, Ubuntu or Raspberry Pi OS, on arm64 or amd64.
  3. 03
    A route to your camerasSame network, or a route to the VLAN they sit on.
  4. 04
    A separate diskNot the one the Hub boots from. It will refuse, and say SE-STA-015.