Runs on your infrastructure
A single machine for one site, or your Kubernetes cluster for a fleet — the same software either way. Nothing about it lives in someone else's cloud, and nothing leaves your premises unless you send it.
Yours to run
LandauOne is software you deploy, not a service you rent. It runs where your data is allowed to be — and the bill does not grow with your success.
A single machine for one site, or your Kubernetes cluster for a fleet — the same software either way. Nothing about it lives in someone else's cloud, and nothing leaves your premises unless you send it.
No per-seat, per-sensor, per-camera or per-site meters — and every component the product ships with is free for commercial use, with a written inventory your procurement team can file. The only running costs are your own machines. Licensed per deployment — one flat licence for a site or a cluster, whatever it carries; pricing on request.
Air-gapped sites are a supported deployment, not an exception. Even the world maps keep working offline, drawn from map data you host yourself — no outside service in the loop, nothing phoning home.
Readings arrive from your existing message brokers — on premises or cloud-managed — or from a plain HTTP call. Corporate certificate authorities and mutual-TLS broker policies are configuration, not a change request.
A brief outage does not become silent data loss: sources are asked to redeliver, and anything that genuinely could not be kept is counted and shown rather than forgotten. One command produces a verified backup; the restore procedure is written down and tested.
Your data rests in a standard open-source database you can query, back up and take with you using ordinary tools. Growing from one machine to many is a documented path, not a re-purchase.
Access
A shared key, or a personal sign-in through your own identity provider. The console shows which one is in use at all times — a shared key means shared dashboards, and someone who forgot that would otherwise wonder where their own work went.
Looking things up, saving dashboards, watching cameras and administering the camera registry are separate permissions. An administrator who can delete a camera can also see it — deliberately, because the alternative is a credential that deletes what it cannot look at.
Nothing is reachable without a credential unless it was deliberately opened. Video is protected exactly like the registry it belongs to, and camera passwords are stored encrypted rather than in the clear.