Skip to main content
Why Zerix

The architectural moat
legacy CAFM cannot cross.

Three reasons Zerix wins evaluations against vendors many times our size, and why those vendors can’t catch up without rebuilding from scratch.

Pillar 01

Built by FM, not coders.

01 of 03

Zerix is built by people who have operated, audited and been accountable for safety-critical estates. Every module solves a real day-to-day FM problem we have lived. The data model maps to how compliance evidence is actually generated and consumed in the field, not how a software vendor imagines it should work.

  • Founder Dan Vaughan: 20+ years in FM delivery and consultancy across NHS, education, healthcare property, nuclear, utilities, logistics, hospitality, property management and B&I.
  • Built after seeing compliance failures first-hand, not as a software vendor surveying a market.
  • Every screen reviewed by FM professionals before it ships.
Pillar 02

AI-safe by architecture.

02 of 03

Zerix is built on a modern database engine with native Row-Level Security enforced at the engine itself. RLS policies are applied before any query reaches the application layer. AI models, API calls, anything that touches the data can only see what the requesting user is authorised to see. The security is structural, not procedural.

  • Multi-tenant data isolation enforced at the database, not in application code.
  • Cross-tenant data leakage is structurally impossible, even if the application has a bug.
  • Legacy CAFM platforms cannot match this without rebuilding their entire database. That takes years.
Database engine
Native engine-level RLS
Tenant isolation
Row-level, applied pre-query
AI runtime
Sees only RLS-authorised data
Pillar 03

Compliance-led by design.

03 of 03

Every module ties back to statutory evidence. PPM activity, audit findings, contractor work and asset condition all link to the compliance record, so a missed inspection becomes a tracked risk rather than a buried row in a spreadsheet. Designed for the post-Building Safety Act accountability environment.

  • Binary compliance logic: every status is compliant, expired, due or missing.
  • Audit trail of every action by every user, defensible to regulators and boards.
  • Aligned to UK statutory regimes: BS 7671, LOLER, gas safety, fire safety, water hygiene, asbestos and more.
The structural moat

Legacy CAFM can’t catch up. Not without rebuilding the database.

Adding AI safely is not a feature decision. It is an architectural one. Zerix was built on engine-level Row-Level Security from day one. Legacy vendors would need to replatform their entire database to match. That takes years.

Aspect
Legacy CAFM
Zerix
Database architecture
Legacy SQL or proprietary, no native row isolation
Modern engine with native row-level isolation
AI safety
AI queries can leak across tenants, often pulled back after testing
AI sees only what RLS policies allow, safe by construction
Time to deploy
6 to 24 months, dedicated implementation teams
Weeks. Bulk CSV import, document ingest by Zerix AI Assistant
Commercial model
Six-figure deploy plus rolling maintenance and integration spend
Annual subscription, modular by building, no implementation lock-in
Built by
Software vendors who have never operated an estate
FM professionals who have been accountable for compliance

See the moat in action.

A live demo of Zerix against our example data. See compliance, CAFM, contracts and the AI Assistant in action.