Reference deployment. Cognitum's white-label platform, shown in Cognitum branding with a placeholder operator brand in the console. A partner build carries the partner's own tokens throughout. Demonstration data only — nothing here is sensing, inferring, or reading live device state.
White-label reference deployment

Your hardware. Your brand. Our intelligence layer.

This is the platform as a hardware partner receives it. The landing page speaks as Cognitum; the console behind it is deliberately branded “Your Brand”, because that is the only thing a partner build changes. Sensing and inference run on the device — no camera, nothing worn by the subject, no cloud round-trip.

65Capability demos
116In the catalog
11Categories
On-deviceInference and storage

What a hardware partner gets

You keep the hardware, the channel and the customer. Cognitum supplies the intelligence layer as bounded, signed, replaceable objects behind a surface that stays yours — shown here with placeholder tokens in place of yours.

Rebranding is data, not code

Brand tokens live in one replaceable file. No layout or behaviour changes when they are swapped — the partner concepts on this platform differ by that file and their copy, nothing else.

Runs on the CPE you already ship

Presence, occupancy and safety derive from channel-state measurements the Wi-Fi radio already computes to beamform. No camera, no wearable, no added sensor in the bill of materials.

You keep the control plane

WAN, LAN, Wi-Fi, mesh, cellular, voice, RF and firewall stay authoritative in your own management system. Cognitum renders a bounded service-posture panel, not a second control plane.

Signed, reproducible, auditable

Capabilities are signed and pinned by digest; images build reproducibly with an SBOM and a component lock, so what ships is what can be proven to have shipped.

The operator console

Static snapshots of a real running build. Same navigation, same data model — shown here in its reference theme; a Cognitum build would carry Cognitum branding throughout. Controls are not wired to a live device.

Capability catalog

65 capability demonstrations, grouped by what they do, with the categories most relevant to Cognitum first. Search or filter, then open any demonstration.

HomeCore surfaces5 featured

Role-scoped household and installer surfaces over HomeCore state (ADR 018). Each renders a bounded view; HomeCore owns the domain state.

Health & wellbeing8 featured

Contactless physiological sensing from ambient radio: no camera, and nothing worn by the subject.

Security & safety5 featured

Intrusion, tailgating, weapon and anomaly detection for premises protection.

Fleet & mesh10

Coordination across many devices — consensus, replication, load balancing and orchestration between nodes rather than inside one.

On-device intelligence7

Inference, attention and continual-learning primitives that execute on the device instead of round-tripping to a cloud.

Research methods7

Advanced and experimental techniques — sparse recovery, temporal logic, hyperbolic embeddings and other frontier work.

Developer tooling5

Surfaces for building, deploying and debugging capabilities against a real device.

Industrial & workplace5

Plant-floor and site safety: proximity, confined space, structural and equipment monitoring.

Building & energy5

Occupancy-driven HVAC, lighting and energy behaviour for commercial and residential space.

Signal processing4

The RF layer the rest of the catalog builds on — compression, coherence and interference handling.

Retail & spaces4

Footfall, dwell, engagement and turnover analytics for physical retail and hospitality.

No capabilities match that search.

About these pages. Each is the demonstration interface for that capability, served exactly as it ships on the device. They render representative data — nothing here is sensing, inferring, or reading live device state.