Integrations · Shipping with GA
Plug into the systems you already run.
Rivolq is designed to connect to the CMMS, BMS, ERP, and data warehouse your team already uses — not replace them. Risk intelligence layers on top of your existing stack, and enriched outputs flow back into the systems your team works in every day.
Integration status
Custom-built for pilot customers today.
Standard catalog connectors ship with GA. Until then, every pilot gets a scoped integration build tailored to their stack.
Custom CSV/Excel ingestion for pilot deployments
SQL database direct-connect (Postgres, MSSQL, MySQL)
REST API framework with authenticated endpoints
SSO via SAML 2.0 and OIDC
Top-5 CMMS integrations (Maximo, AiM, eMaint, MaintainX, Limble)
Snowflake and Databricks bi-directional sync
Integration categories.
Standard connectors across the systems most facility teams already run. Don't see your system? The integration framework is pattern-based — if your tool has an API or a database, we can likely connect to it during your pilot.
CMMS & Work Management
Priority buildImport your existing work order history, PM schedules, and asset registries. Push enriched risk context back into the CMMS your technicians already use.
Building Management & BAS
In scopingContinuous condition signals from your existing BMS/BAS feed directly into the risk engine — not a separate dashboard your team has to check.
ERP & Financial Systems
In scopingCapital plans, asset registers, and cost data flow bi-directionally — so risk recommendations land in the same system finance already trusts for approval.
Data Warehouse & Analytics
Pattern definedSync Rivolq risk scores, capital recommendations, and audit trails directly into your enterprise data layer for reporting, BI, and downstream systems.
Identity & Access
Shipping at GASSO, SCIM provisioning, and role-based access that fits into whatever identity stack your organization already runs.
Collaboration & Alerts
Pattern definedHigh-severity risk alerts and capital-decision notifications routed to the tools your team works in every day — not a new inbox to check.
How we integrate
Principles, not just a connector list.
Read-first. Write on request.
By default, Rivolq reads from your source systems without modifying them. Writing back into your CMMS or ERP is opt-in per integration — so your source-of-truth systems stay under your control.
No middleware resellers.
Direct connections where possible. When a third party is required (iPaaS for a legacy ERP, for example), we name it, document it, and the customer owns the credentials.
Your data stays your data.
Data processed through integrations remains yours. We never sell it, never use it to train cross-customer models, and never share it without written authorization.
Built for your auditors.
Every integration event is logged, timestamped, and attributable. When an auditor asks what data Rivolq pulled, when, and what changed — the answer is a query, not a conversation.
Don't see your system?
Pilots are where we prove the integration pattern works for your stack.
Most of our catalog integrations started as pilot-customer integrations. If your CMMS, ERP, or BMS is not on the list above, tell us what you run — we'll scope the work during pilot conversations and ship the connector with your deployment.
Tell us what you runWant a scoped integration plan for your stack?
We'll walk through your CMMS, BMS, ERP, and data layer on a 30-minute call and map what a Rivolq integration looks like for your environment — including read patterns, write-back options, and timeline.