Coexistence
How Envoy works with your existing stack.
Envoy is the operational coordination and verification layer above the property operator’s existing operational stack. It does not replace your property management system. It does not replace your building management system. It does not replace your resident automation, your inspection software, or your point-solution monitoring. It sits above the systems already in place, verifies that they are working, coordinates response when they fire, and produces the operational record those systems do not produce on their own.
See the layer mapWhy this page exists
The operational stack is fragmented by design.
Modern property operations rely on specialized systems that solve different operational problems. The operational stack has fragmented because the problems themselves are different. Verifying that those systems are working and coordinating response across them is a different operational job from any of them. As the stack becomes more specialized, that job naturally separates from the systems being coordinated.
Coexistence is not an integration burden; it is the structural reality of running property operations at scale.
Coexistence is not an integration burden; it is the structural reality of running property operations at scale.
Above the PMS
Property management systems.
Envoy does not replace RealPage, AppFolio, Yardi, or Entrata. Property management systems are the administrative layer of the operational stack. They handle leasing, accounting, resident management, and the work order process. They are the system of record for the business of running the property.
Envoy operates at a different layer. The operational coordination and verification layer sits above the administrative layer and resolves a different problem. The PMS knows what work orders have been assigned and completed; it does not know whether the monitoring infrastructure feeding those work orders is actually working. The PMS records that an alert produced a maintenance ticket; it does not verify that the alert system itself is healthy.
The two systems coexist by design. The PMS continues to handle leasing, accounting, and resident management. Envoy verifies that the operational infrastructure underneath the property is working, coordinates response when alerts fire, and produces the operational record the PMS does not. Work orders generated by Envoy alerts can land in the PMS work order system. Operational documentation produced by Envoy can be exported to PMS-attached records. The platforms operate on different layers and the workflow between them strengthens both.
Envoy operates at a different layer. The operational coordination and verification layer sits above the administrative layer and resolves a different problem. The PMS knows what work orders have been assigned and completed; it does not know whether the monitoring infrastructure feeding those work orders is actually working. The PMS records that an alert produced a maintenance ticket; it does not verify that the alert system itself is healthy.
The two systems coexist by design. The PMS continues to handle leasing, accounting, and resident management. Envoy verifies that the operational infrastructure underneath the property is working, coordinates response when alerts fire, and produces the operational record the PMS does not. Work orders generated by Envoy alerts can land in the PMS work order system. Operational documentation produced by Envoy can be exported to PMS-attached records. The platforms operate on different layers and the workflow between them strengthens both.
Above resident automation
Resident automation.
Envoy does not replace SmartRent or Latch. Resident automation operates primarily inside the unit. It owns smart locks, smart thermostats, leak sensors paired with shutoff, hub infrastructure, and the resident-facing app. The unit is the center of the operational model. The operational outcome is resident experience, ancillary revenue, and unit-level risk reduction.
Envoy operates above the unit. The coordination and verification layer sits across the broader operational stack, including resident automation. Resident automation generates monitoring signals. Envoy verifies that those signals are arriving, coordinates response when they fire, and integrates them with the rest of the operational layer. The distinction matters because resident automation’s monitoring is unit-scoped by design; verifying that the monitoring itself is healthy is not the platform’s job.
An operator who has deployed SmartRent does not remove it to add Envoy. They add Envoy to coordinate operational awareness across SmartRent, the BMS, the leak detection vendor, the inspection platform, and the rest of the stack. SmartRent owns a customer-facing relationship Envoy does not touch. Envoy owns a layer of operational coordination SmartRent does not provide.
Envoy operates above the unit. The coordination and verification layer sits across the broader operational stack, including resident automation. Resident automation generates monitoring signals. Envoy verifies that those signals are arriving, coordinates response when they fire, and integrates them with the rest of the operational layer. The distinction matters because resident automation’s monitoring is unit-scoped by design; verifying that the monitoring itself is healthy is not the platform’s job.
An operator who has deployed SmartRent does not remove it to add Envoy. They add Envoy to coordinate operational awareness across SmartRent, the BMS, the leak detection vendor, the inspection platform, and the rest of the stack. SmartRent owns a customer-facing relationship Envoy does not touch. Envoy owns a layer of operational coordination SmartRent does not provide.
Above inspections
Inspection software.
Envoy does not replace HappyCo or Inspectorio. Inspection software digitizes periodic property inspections, manages condition documentation, and produces compliance-ready records. It is operationally focused on cadence-based assessment: scheduled inspections, due diligence walkthroughs, turn inspections, routine condition reviews.
Inspections are periodic snapshots. They capture what is true at the moment of inspection. Envoy is continuous. It captures operational state in the gaps between inspections, which is where most operational incidents actually happen. The two operational models are structurally distinct: cadence-based assessment captures conditions at intervals; continuous coordination tracks operational state in real time.
Inspections remain valuable for the work they are designed to do. The condition documentation, the compliance records, the turn inspections, the due diligence walkthroughs are not replaced by continuous operational coordination. They are complemented by it. The operational question is not inspections or Envoy; it is what the operator knows between inspections and what evidence they can produce that operations were functioning in those gaps.
Inspections are periodic snapshots. They capture what is true at the moment of inspection. Envoy is continuous. It captures operational state in the gaps between inspections, which is where most operational incidents actually happen. The two operational models are structurally distinct: cadence-based assessment captures conditions at intervals; continuous coordination tracks operational state in real time.
Inspections remain valuable for the work they are designed to do. The condition documentation, the compliance records, the turn inspections, the due diligence walkthroughs are not replaced by continuous operational coordination. They are complemented by it. The operational question is not inspections or Envoy; it is what the operator knows between inspections and what evidence they can produce that operations were functioning in those gaps.
Above the BMS
Building management systems.
Envoy does not replace Honeywell, Siemens, Johnson Controls, or Schneider. Building management systems control building infrastructure: HVAC, lighting, access, and the operational equipment that runs the building itself. The BMS operates the equipment through setpoints, schedules, control logic, and direct device commands.
Envoy operates above control. The coordination and verification layer provides operational awareness across the systems the BMS controls and across the broader operational stack the BMS does not touch. The BMS knows whether a chiller is running; it does not know whether the sensors monitoring the chiller are still reporting accurately. The BMS controls the equipment it owns; it does not coordinate operational response across the leak detection vendor, the resident automation layer, or the inspection cadence.
Control and awareness are different operational problems. The BMS does control well. Envoy does coordination and verification well. The integration between them is the workflow boundary: BMS-attached sensors produce signals; Envoy verifies the signals are arriving and coordinates response when they require attention beyond what the BMS alone can resolve.
Envoy operates above control. The coordination and verification layer provides operational awareness across the systems the BMS controls and across the broader operational stack the BMS does not touch. The BMS knows whether a chiller is running; it does not know whether the sensors monitoring the chiller are still reporting accurately. The BMS controls the equipment it owns; it does not coordinate operational response across the leak detection vendor, the resident automation layer, or the inspection cadence.
Control and awareness are different operational problems. The BMS does control well. Envoy does coordination and verification well. The integration between them is the workflow boundary: BMS-attached sensors produce signals; Envoy verifies the signals are arriving and coordinates response when they require attention beyond what the BMS alone can resolve.
Above point solutions
Point-solution monitoring.
Envoy does not replace leak detection vendors or specialty environmental monitors. Point solutions are designed for a single failure mode. A leak detection vendor detects leaks. An environmental sensor vendor detects temperature, humidity, or air quality excursions. The operational value is in the depth of coverage on the specific failure mode the platform was built to catch.
Envoy operates above point solutions. The coordination and verification layer verifies that the point solutions are actually working, coordinates response when they fire, and integrates their signals with the broader operational stack. A leak detection vendor cannot, by architecture, verify itself. The point solution detects leaks; the layer that confirms the leak detector is online and reporting is a different operational problem.
Point solutions retain their value within scope. The narrow specialization is the strength of the category. What changes when Envoy is in place is that the operator can trust the point solution is working, can coordinate response when it produces signals, and can integrate its operational evidence with the rest of the portfolio’s operational record. The same holds where a property has no point solution for a given failure mode: Envoy provides that monitoring as part of the deployment, then verifies and coordinates it like any other source. If the monitoring is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it.
Envoy operates above point solutions. The coordination and verification layer verifies that the point solutions are actually working, coordinates response when they fire, and integrates their signals with the broader operational stack. A leak detection vendor cannot, by architecture, verify itself. The point solution detects leaks; the layer that confirms the leak detector is online and reporting is a different operational problem.
Point solutions retain their value within scope. The narrow specialization is the strength of the category. What changes when Envoy is in place is that the operator can trust the point solution is working, can coordinate response when it produces signals, and can integrate its operational evidence with the rest of the portfolio’s operational record. The same holds where a property has no point solution for a given failure mode: Envoy provides that monitoring as part of the deployment, then verifies and coordinates it like any other source. If the monitoring is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it.
Above IoT dashboards
IoT dashboards.
Envoy is not an IoT dashboard. IoT dashboards aggregate readings from underlying systems into displayable views. They operate on those readings, not on the operational state of each property. The dashboard shows what is happening; it does not coordinate response, verify that the underlying systems are working, or produce the operational record that downstream stakeholders increasingly require.
Envoy is the operational layer above those readings. Aggregated readings are the input. Operational coordination, verified infrastructure, and documented response are the outputs. The dashboard surfaces what is true; the coordination layer is what the operator and their team work in to act on what is true.
The distinction is structural. A dashboard that shows sensor readings cannot, by design, verify that the sensors producing those readings are healthy. A visualization layer that aggregates alerts cannot, by design, coordinate the lifecycle of those alerts across teams and systems. Visualization is part of the operational stack. Coordination and verification is the layer above it.
Envoy is the operational layer above those readings. Aggregated readings are the input. Operational coordination, verified infrastructure, and documented response are the outputs. The dashboard surfaces what is true; the coordination layer is what the operator and their team work in to act on what is true.
The distinction is structural. A dashboard that shows sensor readings cannot, by design, verify that the sensors producing those readings are healthy. A visualization layer that aggregates alerts cannot, by design, coordinate the lifecycle of those alerts across teams and systems. Visualization is part of the operational stack. Coordination and verification is the layer above it.
The layer map
How to read the layer map.
Every operational system in property tech sits on a specific layer. The administrative layer handles the business of the property. The resident automation layer operates inside the unit. The inspection layer runs on cadence. The control layer operates equipment. The point-solution layer detects specific failure modes. The visualization layer shows aggregated readings.
Envoy operates on the coordination and verification layer above all of them. The layer is not a feature competition with any of the systems below it. It is a different operational job. The systems below continue to do what they do well. Envoy verifies they are working, coordinates response across them, and produces the operational record that no single layer below can produce on its own.
Without a coordination and verification layer above them, the systems below produce signals that may or may not be working, fire alerts that may or may not be coordinated, and leave the operator with an incomplete operational record.
Envoy operates on the coordination and verification layer above all of them. The layer is not a feature competition with any of the systems below it. It is a different operational job. The systems below continue to do what they do well. Envoy verifies they are working, coordinates response across them, and produces the operational record that no single layer below can produce on its own.
Without a coordination and verification layer above them, the systems below produce signals that may or may not be working, fire alerts that may or may not be coordinated, and leave the operator with an incomplete operational record.
Become a partner
Envoy is sold through partners.
If you serve property operators and want to add an Envoy partnership to your service line, the Become a Partner form is the right next step.