RAXA Sentinel

Ref	Entry	Post / site	Raised	Respond by	State
INC-2026-00391	Unattended bag, Gate 3 concourse	Screening point	17:02	17:07	SLA 5 min
TOUR-04118	Perimeter beat — 14 of 14 checkpoints	Airside perimeter	16:30	—	Complete
ARM-00219	12 bore DBBL issued — 5 rounds	Armoury, T3	14:00	22:00	Out
VP-2026-004417	Contractor, Siemens India — escort required	Main gate	16:48	—	Inside

What it replaces

The operation already keeps records. They are just on paper.

The muster roll, the gate register, the armoury register, the occurrence book, the beat card. Each one is a real control — and each one is invisible to everybody who is not standing next to it. Sentinel keeps every register intact and makes it readable from anywhere.

Muster roll: Geo-fenced attendance from the guard’s own phone. A check-in from outside the site radius is refused, with the distance stated. Present / absent / relief, per post, per shift.
Occurrence book: Twenty incident types, each carrying the contracted response and resolution clock, the SOP the guard must run, and an escalation ladder that reaches the client’s own head of security.
Armoury register: Weapon out, rounds out, weapon in, rounds in. A return that does not reconcile is recorded as a discrepancy rather than quietly accepted. The document an arms officer asks for.
Beat card: Rounds generated from the beat plan before the shift. Each checkpoint scanned by QR or NFC and validated against its own position. A missed round is detected, not merely unreported.
Gate register: Visitor and vehicle passes, material movement with weighbridge readings, and a watchlist that blocks a pass outright at the gate and records the denial.

Four surfaces

One platform, met where each person actually stands.

A regional head at a desk, a client in their own office, and a security officer on a gate at two in the morning need different things from the same data.

Console

Operations

Twelve modules from the command dashboard to the growth console. The screen RAXA’s own people work from all day.

Portal

The client

Their sites, their incidents, their score against the service levels in their contract. Scoped so an account sees only its own.

Field app

The guard

Attendance, incident with location, SOS, patrol scanning, leave and payslip. Built for a low-end handset on a poor connection.

No app at all

The same five actions over WhatsApp, in English, Hindi, Telugu, Tamil and Kannada. The cheapest terminal RAXA will ever deploy.

A guard’s token is scoped to their own record: the platform refuses another officer’s service file, and a client never sees a guard’s CTC, KYC or bank details at all.

Only here

The parts a facility platform does not have.

Most of this exists because a security business is regulated, armed and audited — and a generic operations tool has no place to put any of it.

PSARA, state by state

A licence for Telangana does not permit deployment in Karnataka. Every state licence is held with its validity and renewal status, so “can we bid for this site” has an answer that is not somebody’s memory.

Police verification that expires

The Act requires it and it lapses. The force view lists whose verification falls due before the client’s auditor finds it.

Round-level reconciliation

Rounds issued, returned and fired are counted against each other on every weapon movement. A mismatch becomes a discrepancy record, not a rounding error.

An escalation that leaves the building

In facility management a breach is a credit note. In security someone senior must know within minutes — so the ladder has a rung for the client’s head of security.

The client’s view

The service level, argued from the data rather than a spreadsheet.

Every client contract carries numbers. The portal scores them continuously, from the same records the operation runs on, and prints the statement.

Contracted service levels — last 30 daysGrade A · 96.5%

Metric	Target	Actual	Variance	Outcome
Deployment fulfilment	98.0%	98.4%	+0.4	Met
Patrol round completion	95.0%	97.0%	+2.0	Met
Electronic security uptime	99.0%	98.1%	−0.9	Below
Incident response SLA	95.0%	91.5%	−3.5	Below

Two of these are short. That is the point of showing them: a scorecard that is green everywhere is a scorecard nobody checks.

Commercial

Two screens built to be opened in a client meeting.

Cross-sell whitespace

Scores every account against all twelve service lines by segment fit — an airport reads 95 on techno security, a mall reads 90 on event security — and ranks what each has not bought yet, with the play: prove the base, show the gap, price the fix, pilot one site for ninety days, roll out on the proven number.

Value engineering

Models what the technology layer is worth in rupees: guard posts displaced by a camera cluster, overtime removed by roster automation, attrition against the industry baseline, false-alarm handling, SLA penalty exposure. Every assumption is an input, so the account team re-runs it on the client’s contracted rates instead of arguing with a default.

The model states plainly that its figures are model outputs rather than billed savings, and names any part of the operation that did not report, so a number is never quietly understated.

Under it

Fourteen services, one entrance.

MongoDB, Express, React and Node. Each service owns its own database and is deployable on its own; every request enters through one gateway that verifies the token and scopes it to the caller’s tenant.

Verified, not asserted: 52 end-to-end behavioural checks and 117 create/read/update/delete checks across 28 entities run against a throwaway database on every change. A delete only passes when the record actually leaves the working list.
Deleting keeps the record: A removed row is retired rather than erased — it leaves the working list and stays on file. Permanent removal is a separate, administrator-only act, because a security operation has to keep its trail.
Integration seams: Video and access control arrive through one event endpoint; biometric attendance, SMS, email and push each sit behind an adapter. Milestone, Genetec, Honeywell and Matrix plug in where the mock provider sits today.

Service lines

Everything RAXA sells, in one operating picture.

The platform models all twelve lines, so an account’s scope, its people, its equipment and its compliance sit together instead of in four systems.

        Manned guardingTechno securityAviation security
        Fire safetyCyber securityDrone & anti-drone
        Canine unitsExecutive protectionEvent security
        Security consultancyTraining academyInvestigation & BGV
      

The Anantapur academy runs inside the same platform: programmes with their regulatory basis, batches, certificate expiry, and module content in up to ten languages — because the compliance number an auditor asks for is a training number.