AI-agentic intelligent platform for managing facility operations
AI agents that help facility teams run the day.
Orbit, Pulse, Atlas, and Nova sit on one product line — tickets, assets, attendance, security, and energy. An intelligence layer across the work. Agents recommend. People still close the job. Not IoT charts-only. Not a society-only app.
Detect → Diagnose → Act → Verify → Learn
- 01 Detect A person or a sensor raises work.
- 02 Diagnose Asset, location, and history attach.
- 03 Act The right person does the job on mobile.
- 04 Verify Evidence and outcome are visible.
- 05 Learn The next similar job is faster.
On sites today
Teams already running MatriqGo
01 / Who it’s for
Facility and property teams — not a society-only app.
Day users are FM, security, technicians, and vendors. Owners buy outcomes. If you run a building, a campus, or a plant, you’re in the frame.
-
RWA
Residential societies
You’re a fit if the society office, guards, and vendors still close work in WhatsApp groups.
-
Commercial
Commercial buildings
You’re a fit if tenants raise issues by email and you cannot see SLA or asset history in one place.
-
Campus
Campuses
You’re a fit if one estate team runs hostels, labs, and plant rooms across many buildings.
-
Manufacturing
Manufacturing
You’re a fit if production waits on a breakdown that should have been a planned job.
-
Warehouse
Warehouses
You’re a fit if docks, HVAC, and night security live in three different notebooks.
-
Hospital / school
Hospitals and schools
You’re a fit if visitors, critical assets, and after-hours tickets cannot miss a handoff.
02 / The problem
Ops data is scattered. Nobody sees the same building.
WhatsApp, Excel, paper, visitors, biometrics, AMC, vendors, inventory, BMS and email — each holds a slice. Agents and people work the same record so the building is visible.
- Excel
- Paper registers
- Visitor books
- Biometrics
- AMC folders
- Vendor chats
- Inventory sheets
- BMS / email alerts
03 / How it works
Five steps. Named people. Then the system learns.
You start by raising work the way the site already does — a person or a sensor. Agents recommend. People still close the job.
-
01
Resident, employee, guard, or sensor
Someone raises work
A complaint, a patrol exception, or a meter alert — not a forwarded screenshot.
-
02
Admin or the system
Asset, location, and history attach
The job already knows which asset, which floor, and what failed last time.
-
03
Orbit
Priority and assignee are recommended
Orbit says what is stuck, who should take it, and why the SLA is at risk.
-
04
Technician or guard
Work happens on the phone, with evidence
Photos, scans, and notes stay on the job — not in a personal chat.
-
05
Manager, then the system
Outcome is visible. The system learns.
Close is verified. The next similar job starts with that history.
04 / Six modules
The work you turn on. Not a twenty-module catalogue.
Tickets, assets, attendance, visitors, patrolling, and IoT / energy. RBAC is how access is gated — it is not a module.
-
Tickets Tickets
Agent Orbit Pain. Jobs die in WhatsApp. Assigned → Closed tells you nothing. Outcome. Every ticket carries the asset, past failures, AMC, SLA, parts, and evidence.
How to use Tickets -
Assets Assets
Agent Atlas Pain. The register is an Excel sheet. Health is a guess. Outcome. A health score from age, failures, PM, and sensors — before the breakdown.
How to use Assets -
Attendance Attendance
Agent Pulse Pain. Present / Absent does not tell you if the shift did the work. Outcome. Shift connects to tickets and patrols, so you see productivity — not a tick in a register.
How to use Attendance -
Visitors Visitors Pain. A gate QR is not a visitor system if it never meets the job. Outcome. A visit linked to the work order, asset, and authorized zone.
How to use Visitors -
Patrolling Patrols Pain. Paper checklists can be filled from the control room. Outcome. NFC, QR, or GPS proof — plus a missed checkpoint or an odd route.
How to use Patrolling -
IoT / Energy IoT / Energy
Agent Nova Pain. Live charts that nobody turns into work. Outcome. Anomaly → ticket → assign → verify, in the same system.
How to use IoT / Energy
05 / Agents
Named agents. People still close the work.
Orbit first. Then Pulse, Atlas, and Nova. Each has one job. They recommend and hand off — they do not replace the technician, guard, or manager.
Orbit · first
Shows what’s stuck, why an SLA broke, and what to do next.
Shows what’s stuck, why an SLA broke, and what to do next.
Tickets
06 / Deployments
Live sites. Same product line.
Residential, commercial, and plant deployments from the MatriqGo field book — no metrics beyond what is already published.
-
Residential · 2025
Lotus 300
Noida, India · Premium Residential Community
Comprehensive IoT retrofit for a premium residential society targeting 20-30% energy cost reduction through Automated Scheduling, Water Pump Management, and Data-driven Insights.
-
Residential · 2025
Greenview Residential Township
Ghaziabad, India · 2,500+ Apartments
Complete smart society automation including smart water management, energy management, genset management, and a dashboard serving administrator with the complete monitoring at one place.
-
Industrial · 2025
Apex Manufacturing Plant
Noida, India · 150,000 sq.ft
Industrial IoT deployment for Genset Telematics, HVAC Management, and Energy Management across 8 production lines, resulting in 26% efficiency improvement.
-
Commercial · 2025
Horizon Business Park
Gurgaon, India · 12 Buildings
Integrated Building Management system for a 12-building business park, including HVAC optimization, Water Management, and centralized Energy Management.
-
Residential · 2025
Sunrise Gated Community
Noida, India · 800 Villas
Premium villa community with perimeter security implemented, Genset Management, Water Management, and community-wide Energy Monitoring system.
07 / Platform
How the platform is gated and proven.
These are not modules. They are the permission, site, audit, and mobile plumbing every module already uses.
-
RBAC
Who can see which site, module, and record. Platform permission plumbing — not a module in the grid.
-
Multi-site
One login across buildings, campuses, or plants. Roles stay scoped to the sites they own.
-
Audit
Who did what, when, with evidence. A close record you can show, not a memory.
-
Mobile apps
Android and iOS for the floor. Same tenant as the web console — not a second product.
08 / Outcomes
What owners buy. What the floor can show.
-
SLA you can defend
Intake, owner, and evidence on the same ticket — not Assigned → Closed.
-
Asset risk you can see
Health from age, failures, PM, and sensors, before the breakdown writes the job.
-
Patrol proof
NFC, QR, or GPS at the point — plus a missed checkpoint or an odd route.
-
Energy waste that becomes work
Anomaly → ticket → assign → verify. Charts are not the end of the story.
-
Visitor ↔ work order
A service visit can attach to the asset and the authorized zone, not only a gate QR.
09 / Mobile
The floor already has the app.
Tickets, punches, patrol scans, and visitor check-in happen on Android and iOS — the same system as the web console. Not a seventh module.
See your facility in one system.
Get started on the product, or start on the Android and iOS apps the floor already uses. Call or email if you already know the sites.