SentrixShield
Home Platform Solutions Pricing Trust Company Contact Book a scan
Home/Platform
The platform

Five layers between a camera nobody watches and an answer you can act on.

Every surveillance analytics product on the market starts at the camera. We start at the room. That single inversion is what makes the rest of this affordable for a business with one location and no IT department.

System architecture · what runs where

YOUR PREMISES SENTRIXSHIELD · INDIAN REGION Your CCTV RTSP or ONVIF Existing NVR Untouched SentrixEdge appliance Detection, tracking, counting Region grounding & rules Clip buffer (local only) RAW VIDEO STOPS HERE events · TLS 1.3 <1 GB / cam / month SentrixTwin Gaussian splat + camera map Watch registry Your prompts, compiled Event store Structured, retention-bound You Twin console (browser) WhatsApp & email alerts Weekly digest REST API & webhooks
Layer 01

SentrixScan

One walkthrough. No drilling, no downtime, no rewiring.

A technician walks your premises once with a 360° rig, following a route that captures every surface from at least three angles. Roughly a minute per sixty square feet. You stay open throughout — customers in shot are irrelevant to the reconstruction and are not retained.

Typical duration20–90 minutes
Disruption to tradingNone
Hardware left behindOne edge appliance
Re-scan after a refitOnce a year, included
CoverageTamil Nadu & neighbouring states
A 360-degree scanning camera on a tripod with the surrounding room resolving into a point cloud
A shop interior rendered as a glowing point-cloud digital twin with one region highlighted
Layer 02

SentrixTwin

A photoreal 3D model of your actual premises — and the only interface you will ever need to learn.

We reconstruct the walkthrough as a Gaussian splat: millions of small, soft, coloured volumes rather than flat polygons. The practical difference is fidelity. Reflections, clutter, signage and shelf contents all survive, so the model looks like your shop rather than like a floor plan of your shop.

Every camera you own is then solved into that model — position, orientation and field of view. The system knows which camera can see which physical place, which is what lets you stop thinking about cameras entirely.

  • Runs in any modern browser. Nothing to install.
  • Camera coverage is shown as a shaded volume, so blind spots become obvious.
  • Regions are 3D volumes, not 2D boxes — a shelf and the floor in front of it are different places.
  • Move or replace a camera and every watch keeps working. The place did not change.
Layer 03

SentrixPrompt

Draw a box. Write a sentence. That is the entire configuration language.

A Watch is a region plus a question. You draw the region on the twin and type the question the way you would explain it to a new employee. The prompt is compiled into a detection graph — what to look for, where, when, and what threshold matters — and pushed to the edge appliance.

Ambiguity is resolved by asking you, not by guessing. If you say “busy”, it will come back with “busy meaning more than how many people, for how long?” and remember your answer.

A violet selection frame hovering inside a dense aqua point cloud
Anonymous luminous silhouettes trailing motion paths that resolve into structured data
Layer 04

SentrixVision

The models run on your premises. Only the answers leave.

Detection, tracking, pose, dwell accumulation and threshold evaluation all happen on the SentrixEdge appliance sitting beside your recorder. It draws about as much power as a router and needs nothing from your IT setup beyond a network port.

What crosses the internet is a structured event: a count, a duration, a breach, a bracket estimate. Not a frame. That single architectural choice is what makes the privacy position on this site credible rather than aspirational.

On-premWhere inference runs
<1 GBPer camera per month
ContinuesThrough an internet outage
TLS 1.3Events in transit
Layer 05

SentrixAlert

Backtested before it is armed, so it never becomes noise you learn to ignore.

Write the rule in English. Before it goes live we replay it against your own last thirty days of footage and tell you precisely how many times it would have fired, and when. If the answer is forty times a day, you find out before your phone does.

Alerts arrive on WhatsApp, SMS, email or a webhook, each carrying a still frame and an optional twenty-second clip so you can judge it in two seconds without opening anything.

Backtest preview

rule: queue > 5 people for > 3 min @ billing_counter

11Would have fired · 30d
0.4Per daylow noise
17:40Most common time
A quiet point-cloud field with a single zone flaring amber and pulsing
The prompt library

Watches, written the way people write them

Every line below is a real, working prompt — not a template with blanks. Filter by what you are trying to find out. Click any prompt to copy it.

Something not on this list? Describe it to us — if it is visible on camera and you can say it in a sentence, it is usually a watch.

How this differs

Against the two things you are probably already considering

Your current NVRBoxed video analyticsSentrixShield
How you address a placeCamera number2D zone drawn on one camera's frameA 3D region in a twin of your building
Adding a new questionNot possibleVendor request, weeksA box and a sentence, ~30 seconds
Question vocabularyNoneFixed feature listOpen-ended, plain English
If a camera movesn/aZones must be redrawnWatches keep working
Where video is processedLocalUsually cloudLocal, on the edge appliance
Alert tuningMotion onlyTrial and error, liveBacktested against your 30 days first
Facial recognitionSometimes offeredOften central to itNot offered, by design
Realistic entry costSunkEnterprise contractOne site, one month, no lock-in
It does not sit on its own

Send the signal wherever you already work

Watches emit structured events. Where they land is up to you.

  • WhatsApp, SMS and email for the people who will never open a dashboard.
  • Webhooks into anything — a POS, a roster tool, a Google Sheet, your own script.
  • REST API for pulling raw event series into your own reporting.
  • Weekly digest — one email on Monday with what changed and what to look at.
  • CSV export, because sometimes that is genuinely the right answer.

Example webhook payload

{
  "event": "watch.threshold_breached",
  "site":  "madurai-kknagar-01",
  "watch": "billing_queue_over_3min",
  "region": "Billing counter",
  "at": "2026-08-31T17:42:11+05:30",
  "metric": "queue_depth",
  "value": 7,
  "threshold": 5,
  "sustained_s": 218,
  "clip": "https://api.sentrixshield.shop/c/9f2a…",
  "contains_pii": false
}

See it against your own floor plan.

Book a scan and we will build the twin. Thirty-day pilot, one site, no lock-in.