See what matters.Move with certainty.

Signal Intake lets your team inspect what arrived, link source identities, set parsing rules and event mappings, and test them against a stored sample.

Suggested mappings are never applied without review, and reprocessing asks you to confirm how many records it will touch.

Operators pick events from the Event Workbench queues, check the context, then acknowledge, dismiss or escalate.

Event types turn incoming signals into consistent events, and repeat signals can be grouped into one event.

Search number-plate sightings, see which cameras saw a vehicle, open the supporting evidence and export the result as a PDF.

Wanted-vehicle entries go from draft to submission to approval or rejection. Approving is its own permission, and a rejection needs a reason.

Only the community image is shared, never the confidential PDF, and later report changes do not alter the snapshot.

Viewers confirm a one-time code and accept versioned terms before they see an update.

Choose which clients receive alarm messages. Every subscription starts as a dry run, so you can review the decisions before turning delivery on.

Switching a subscription on never sends a backlog of old alarms.

The Occurrence Book logs numbered occurrences against a client and site. Classifying or closing an entry needs its own permission.

Armoury items record serial number, calibre, licence number, storage location and condition, with consumable stock and each issue or return.

One record per trading party, and it can be a client, a supplier or both.

A client record holds contacts, sites, recurring services, installed equipment, invoices, quotes, documents and history. A supplier record holds bills.

Budgets move from draft to submission, then to approval or rejection with a recorded reason. They can also be retracted and marked as paid.

Create, issue and track client invoices, quotes and credit notes, and capture supplier bills.

Design camera positions for a client site on a map, then review the bill of materials that results.

Write the introduction, scope, assumptions, terms and acceptance, preview the proposal as PDF or Word, and link it to a finance quote.

Requests move across a board of status lanes, with owners, priorities, search and filters, and a lane switcher on phones.

Dependencies hold a request open until every blocker is completed or rejected, and the owner is notified when the last one finishes.

Versioned templates for generated invoices, quotes and statements.

Templates put your organisation's name, banking details and accounts email into generated documents.

Prepare and review VAT periods.

Keep traceable, effective-dated rule sets for PAYE, UIF, SDL and COIDA. UIF rates and caps feed payroll calculations.

Employee profiles track onboarding state, departments, contact details and terms.

A guided onboarding wizard takes the ID number, employee details and an optional ID document, and adds the employee only after a review step.

Add a payroll run for a period, calculate it, then move it through controlled statuses that depend on permission.

Recalculate a run after source data is corrected, before it moves on.

An asset register lists equipment, stock, vehicles, devices, SIM cards and armoury records in one searchable view, beside a page for each kind.

Reusable equipment is tracked through stock, issues and asset types.

Device Health gives health, needs-attention, recent-changes and maintenance views of the fleet.

Each device shows its identities, heartbeats, recent signals, open events, Flow requests and maintenance context, and a Flow request can be raised from it.

The tracking map shows the latest reported position of each tracker your role can see.

Select a tracker to see its identity, position time and movement state, then open its device record.

Forms are captured from published, versioned definitions, and each submission keeps the version it was created with.

Save drafts as you work. Required fields are checked on completion, and a completed form reopens only for an authorised user, with a reason.

Switch Verge on for your organisation, then for each site. Gates, guards, gate devices, visitor types and rules are set per site.

Guards check visitors in and out on an enrolled Android gate phone.

Manage users, group permissions into reusable roles, and add custom permissions.

People see only the areas and actions their role allows, and the menu follows the same rules as the pages behind it.

Registered systems report health, checks, metrics and events, with a page for each system.

Port checks measure how long a connection to a remote host and port takes, without installing anything on that host.

Built-in team chat: direct and group conversations between your SuruX users, with search, mute and archive.

Each messaging account your organisation registers gets its own inbox of customer conversations, with delivery and read receipts.

One notifications inbox gathers the updates that need your attention, filtered to what your role can see, and each opens the record it is about.

Guide me, in a page's help menu, opens the shortest relevant guide for that page and lists only tasks within your access.

Your organisation's name, logo and accounts email appear throughout navigation, documents, reports and guides.

Switch areas, and the pages inside them, on or off. Set one menu order for everyone, and find any page from the menu search.

One catalogue of reports, grouped by the areas your organisation has switched on, with access following role permissions.

Set date and status filters, and review the on-screen totals before exporting to PDF or CSV.