Capture
Sensor → ISP tuning → H.265/H.264 encoder
CAMERA / MEDIA PIPELINEOwn the foundation.
Connect the experience.
NetraOS is our embedded Linux platform in development. Around it, we’re building the apps, cloud and installer tools that make a complete surveillance system.
FROM SENSOR TO SCREEN
The complete signal path.
Every stage has a purpose: image quality on the device, useful events at the edge, recoverable local recording and a connected viewing experience.
Understand
Edge detector → tracked events → rules and alerts
HUMAN / VEHICLE ROADMAPRecord
Video segments → crash-safe index → local playback
NVR / DVR / EDGE STORAGEConnect
Device registry → WebRTC → app / desktop
LAN-FIRST / INDIA CLOUDEMBEDDED ENGINEERINGSmall footprint.
Small footprint.
Deliberate choices.
Our stack is designed for constrained camera hardware. C/C++ handles the media path where vendor SDKs require it; Rust is the planned choice for new network-facing device services.
Read the security architectureBUILD SYSTEMBuildroot / Linux
UPDATESRAUC · signed A/B architecture
VIDEO CONNECTIONWebRTC · RTSP / ONVIF roadmap
RECORDINGfMP4 segments · SQLite-WAL index
DEVICE IDENTITYPer-device X.509 · factory provisioning
MODEL STRATEGYSigned, separately managed AI models
BEYOND THE DEVICE
One connected experience.
Software is part of the product from the start. These applications are in our development roadmap.
Your system in your hand.
A planned Flutter mobile app for secure pairing, live grids, two-way talk, unified playback and useful event alerts. LAN-first viewing is a core design objective.
- QR pairing and secure activation
- Local and remote WebRTC viewing
- Hindi and regional-language interface roadmap
Built for the people on site.
The installer and dealer workflow: set up devices, manage customer sites with consent, diagnose problems and keep service moving.
- Batch setup and configuration templates
- Device, storage and firmware health
- Warranty and RMA workflow roadmap
A cloud with a defined role.
An India-hosted control plane for device identity, connection services, event clips and fleet updates. Continuous cloud recording is outside the initial scope.
- Certificate-based MQTT connectivity
- WebRTC signaling and India relay infrastructure
- Staged OTA campaigns and lifecycle-managed clips
Your sites, on a bigger screen.
The Windows-first desktop roadmap for camera walls, multi-site navigation, coordinated playback and evidence export.
- Saved layouts and multi-monitor viewing
- GPU-assisted decode design target
- Playback and installation health across sites
WHERE WE ARE TODAYArchitecture defined.
Architecture defined.
First foundations running.
The current engineering work includes protocol contracts, development PKI, licence and unsafe-API gates, and a Buildroot skeleton with a saved QEMU proof of boot. Sensor integration, media services and the applications remain ahead.
NETRA PRODUCT STUDIO
Take a closer look.
Inspect the NETRA studio imagery in detail, or switch to the interactive 3D view to explore the form and mounting arrangement.
NETRA PRODUCT STUDIO / DETAILS01 — 03
HIGH-RESOLUTION PRODUCT IMAGE
Precision at the centre
ENGINEERED FOR THE WHOLE LIFECYCLESetup is only
Setup is only
the beginning.
The NetraOS roadmap connects first activation, daily operation and long-term service through one device lifecycle.
A distinct identity.
Per-device certificates and secure provisioning establish which device is joining the system. First-use setup is designed around explicit activation rather than shared default credentials.
A local foundation.
Device services, media handling and local storage form the core. Remote viewing is an additional connection path, with network conditions and relay requirements handled explicitly.
Updates with recovery.
Signed A/B firmware updates and staged rollout controls are design goals. Firmware versions, device health and storage status make faults easier to diagnose and service.
Access with a purpose.
Role boundaries, consent-based partner access and auditable administration guide the application roadmap. Viewing, configuration and service should have clearly defined permissions.