See the real workload
Requests, submitted budgets, event queues, devices, and operational changes stay visible where decisions happen.
Enterprise command for high-pressure teams
SuruX
Available on web and mobile, SuruX connects public intake, security events, field response, finance controls, tenant environments, and field work from one precise operating layer.
Surveillance
Response
Finance
Web + mobile
1
operating picture
Live
events and workflows
Web + mobile
operator surfaces
Audit
ready by design
The problem SuruX solves
Operations break when the work is split across too many systems.
SuruX brings critical workflows into one controlled platform: public walkthrough intake, authenticated users, permissioned modules, live surveillance events, response work, finance approvals, nodes, assets, documents, notifications, and mobile attendance or tracking.
Control every action
Role and permission boundaries keep sensitive actions inside the right hands, with audit trails behind the work.
Move faster on the ground
Mobile-ready environment discovery, attendance, notifications, and tracking connect field work back to the tenant API.
Who SuruX serves
Built for teams that carry operational risk every day.
SuruX is designed for operators who need a live picture of people, assets, requests, approvals, and field activity without forcing every team into a different system.
Control rooms
Keep surveillance events, mapped devices, response work, and operator decisions visible from one command surface.
Field teams
Connect mobile attendance, tracking, notifications, and tenant-specific API access back to live operational work.
Finance and admin
Give budgets, invoices, quotes, bills, VAT, UIF, loans, documents, and approvals the same ownership and audit discipline.
Tenant operators
Run separate environments with their own branding, database, modules, permissions, integrations, and user boundaries.
Platform surface
Built around the workflows that cannot drift.
Event command
Ingest alarms, normalize event types, resolve device mappings, review queues, and guide operator actions from a focused console.
Live request flow
Bring technical requests, operational notifications, contacts, documents, and notes into the same workstream.
Approval discipline
Budgets, invoices, quotes, bills, loans, VAT, and UIF workflows can share status, ownership, audit, and document context.
Tenant-aware field work
Environment discovery routes mobile users to the correct SuruX API, keeping sessions, push, attendance, and tracking scoped.
Now connected
The public front door now feeds the operating system behind it.
Public walkthrough intake
Requests from this site submit directly into the configured SuruX tenant instead of stopping at a mailbox.
Operations follow-up queue
Teams can review marketing requests in Operations, assign ownership, and move each request through a clear follow-up status.
Mobile field surface
The mobile app connects field users to the right tenant API for attendance, tracking, notifications, and on-site context.
Bridge-ready integrations
Alarm, SMTP, tracking, and device bridges can move external signals into the same operational control layer.
Connected systems
SuruX sits above the systems your operation already runs.
Alarm platforms, camera infrastructure, tracking feeds, mobile activity, and messaging channels can be routed into tenant workflows so operators act from one controlled layer.
Ajax
Olarm
Hikvision
Dahua
SuruX
Events, devices, queues, response, audit
Ajax Systems
Alarm events, device signals, and security context can be brought into SuruX for mapping, review, and response workflows.
Olarm
Olarm site signals can feed operational queues so teams can track events, ownership, and follow-up inside the tenant.
Hikvision
Camera and recorder environments can sit alongside surveillance events, device records, and response context.
Dahua
NVR, channel, and device integrations can connect surveillance assets to event workflows and operational review.
Tracking and mobile
Location, attendance, push notifications, and field status can flow back to the correct tenant environment.
Email and notifications
SMTP, Graph, WhatsApp-ready messaging, and tenant notification settings can support the same operational follow-up chain.
Request journey
The walkthrough form is connected to tenant follow-up, not a disconnected lead form.
A public visitor can ask for a walkthrough here, and the configured SuruX tenant receives the request in Operations for review and next action.
Public request
Name, email, operation type, message, and source page are captured from the standalone marketing site.
Tenant intake
The request posts to the configured SuruX API and is stored inside the tenant operations data boundary.
Operations queue
The team reviews requests under Operations > Marketing requests, tracks follow-up status, and keeps ownership visible.
Expert response
An expert follows up with the requester while the tenant keeps the original request traceable.
Operator experience
A command surface designed for active decisions.
The marketing site is separate, but the story is the product: dense information, calm hierarchy, live state, and fast movement from signal to action.
- Dashboard queues for urgent requests, walkthrough intake, and finance approvals.
- Mapping workbenches for surveillance events and devices.
- Tracking and mobile context tied to the right tenant environment.
- Reusable documents, notes, contacts, and audit history.
Event Queue
AlarmClaimed
DeviceMapped
BudgetSubmitted
MobileSynced
Tenant profile
API matched
Control plane
The platform is serious about boundaries.
Identity, permissions, tenant settings, audit trails, data protection, and Microsoft sign-in are part of the foundation rather than an afterthought.
Identity first
SuruX credentials and optional Microsoft sign-in map back to active SuruX users and roles.
Permissioned modules
Module and action access can stay explicit across security, settings, finance, nodes, assets, surveillance, and vault workflows.
Traceable work
Budget workflow, authentication, documents, notes, and operational changes have room for durable audit context.
Deployment shape
Separate surfaces. Shared rules. Clean ownership.
The marketing website stands apart from the authenticated Web UI, API, workers, bridges, and mobile app. Product environments can keep their own databases, URLs, branding, and operational policies.
Marketing
Standalone site with tenant intake
Web
Authenticated Blazor UI
API
Tenant workflow boundary
Mobile
Environment-aware field app with tracking and attendance
Bridges
Alarm, SMTP, tracking, and device integrations
Walkthrough
See what SuruX can unify for your operation.
Use this page as the public marketing front door. Requests now land inside SuruX for follow-up, while the authenticated product remains completely separate across web and mobile surfaces.