An organization should choose where its video lives
Recordings, retention and access decisions belong to the organization, not to a service it rents.
About Karnux
Karnux started from a simple position. A video management system should not force everything through a cloud service. Organizations should choose where footage lives, what infrastructure runs it, and who controls the system.
Why Karnux exists
Recordings are evidence. They carry real obligations around privacy, retention and who can see them, and for many organizations that material belongs on their own infrastructure, under their own policies.
That is the answer Karnux is written for. It records to storage you register, runs on Linux servers your team administers, and serves live view, playback and export from your own systems.
What we believe
Recordings, retention and access decisions belong to the organization, not to a service it rents.
A gap in coverage is reported as a gap, and stale data is marked stale, rather than averaged into something reassuring.
Running your own video system should still feel straightforward day to day, and the limits should be on the table from the start.
In practice
Recording, indexed footage, playback and export stay with the system that owns the camera.
A recording node keeps recording through a temporary loss of central coordination.
Coverage gaps, storage pressure and stale observations are shown to operators as they are.
Device behavior, codecs and network paths are tested in the deployment context before being relied on.
Capabilities that depend on configuration or hardware are labelled. Anything not implemented is left out. Confirm software access, device compatibility and deployment requirements before production use.
Talk to us
If you are evaluating video management, planning a deployment or validating devices, share the context and we will assess the fit honestly.