Octosec
EN ES
Self-contained NVR · up to 511 cameras · 1,022 streams

Security footage you really own.

Octosec records the cameras you already own, on hardware you already own. One event bus ingests every stream and fans it out to the recorder, the detector, the live wall and your phone. No cloud, no account, no subscription.

See the app How it works
511 cameras supported — main and sub per camera, 1,022 streams; a 512th is refused at boot, not lost
255 1080p cameras tested — detection at 3 fps each, zero frames dropped: 639 inferences/s, 1.6 cores, one GPU at 89%
127 4K cameras tested — H.265 with motion and detection, zero frames dropped: under 4 cores, ~260 MB/s to disk

Test hardware · Zen 5 9970X, 32 cores · NVIDIA RTX 5090, 32 GB VRAM · virtual cameras over real RTSP

The live wall screen: eight cameras and three vcams as tiles, each at its true aspect, with the fleet event rail alongside. A design render, not a live capture.
The live wall at 1366 pt · tiles carry each camera's true aspect · design render, not a live capture
I

It is yours

The recordings are files on your disk, in your building. There is no account to create, no cloud to trust and no server of ours between you and your cameras.

II

It is small

One event loop; no libc in the core. Measured to 255 cameras of 1080p with detection and 127 of 4K on one GPU workstation, with zero frames dropped; the same code runs our own fleet in about 5% of a 20-core NAS and under 1 GiB of RAM. Every number on this site carries the box it was measured on.

III

Documented at the seams

One documented bus that anything can subscribe to, and one documented camera vocabulary that anything can implement. The phone app is just another subscriber — and so is whatever you build.

Four questions, four answers

Pick the one you arrived with

“Will this show me what happened at my house?”
See it →
“Can I deploy and support this across sites?”
For integrators →
“What can I integrate with, and what happens when it breaks?”
For security providers →
“What do I build so my camera works here?”
For camera vendors →

What we are not doing

The list is short and it is public. Everything else on this site is a fact the system can stand behind, measured on a stated machine.

No ONVIF. Reolink is the shipped driver; any vendor can implement the ABI.
Discovery finds, it does not enrol. The sensor reports a camera the config does not list and never attempts a login; adding it stays your decision.
No app push notifications. Alerts go out by Telegram or email from a watchdog rule; there is no cloud to relay a push through.
No multi-site management and no relay between sites. One site, one stack.
One production site: ours. Running our own eight-camera fleet since July 2026.
Pricing on request. Contact us for pricing and licensing information; a person answers.