Frequently asked questions.

Envoy is the operational coordination and verification layer above the property operator’s existing operational stack. It verifies Envoy-supplied monitoring from the day it’s deployed, and it verifies customer-supplied devices, systems, and integrations wherever it can reach them. It coordinates the response. It shows portfolio operational state across the properties and signals it can surface, and it produces the operational record from what it observed. Envoy reaches operators through a partner or directly from ObjectSpectrum.

Envoy does four jobs.

Infrastructure trust verifies Envoy-supplied monitoring at properties, and it verifies customer-supplied monitoring wherever Envoy can reach it.

Operational coordination gives every alert a structured path: ownership, acknowledgment, response, escalation, resolution, and closure.

Portfolio visibility gives each role a view across the properties and signals Envoy can surface.

Operational accountability produces the operational record from the state and the work Envoy observed.

Envoy is software, but platform isn’t the right word for its category. Envoy is the operational coordination and verification layer for property portfolios. Prism is the platform ObjectSpectrum builds and operates underneath Envoy.

No. Envoy works with connected devices, monitors, and operational systems, but it is not an IoT product or an IoT dashboard. Those systems generate readings and alerts. Envoy verifies the monitoring state it can reach, connects alerts to response ownership and portfolio context, and documents the state and work it observed.

Envoy is the operational coordination and verification layer for property portfolios. “Operational Awareness Infrastructure” is the broader category language for that layer. Envoy itself is described mainly by the operational jobs it performs.

Property operations depend on more specialized systems than they used to: monitoring, administration, control, inspection, and field service. As the number of systems grows, verification, coordination, portfolio visibility, and accountability each become a job of their own. A system can look fine and no longer be reporting. That’s silent monitoring failure, and it creates risk. Catching that condition, assigning the response, and documenting what happened is a job that runs across systems rather than inside any one of them.

The partner is ObjectSpectrum’s customer. The partner pays ObjectSpectrum on a recurring basis and owns the operator relationship. It deploys Envoy across the properties or customer relationships it manages. An owner or operator reached through a partner experiences Envoy through that partner. Where ObjectSpectrum sells directly, it holds the customer relationship itself.

Yes. The primary path is through a partner, but ObjectSpectrum also sells and supports deployments directly, depending on what the deployment involves. Start at Get Envoy either way, and someone will come back to you with the right path. On a direct deployment, ObjectSpectrum supplies and operates the monitoring, handles implementation and technical support, and alerts go to you or to a contact you name.

A firm qualifies as a partner through its operating and economic role, not through its label alone. The partner pays ObjectSpectrum on a recurring basis, owns deployment and the customer relationship, and deploys Envoy across the properties or customer relationships it manages. Common partner types include facilities management firms, property management companies, and mechanical and HVAC providers with maintenance agreements. They also include security and low-voltage integrators with recurring monitoring billing, restoration and remediation firms working under program contracts, insurance carriers funding monitoring across an insured book, and rental fleet operators that deploy Envoy across the assets they rent. Firms that only introduce business are referral partners, or referrers, not Envoy partners.

Envoy currently has industry pages for multifamily (including independent living communities), hospitality, commercial and retail, student housing, rental and vacation homes, industrial, utilities, telecom, and self-storage. The coordination and verification job is the same across all nine, while operating conditions and the partner model vary. The need is easiest to recognize at vacant and periodically occupied properties, where no one is there continuously to catch a silent failure early.

Envoy does not replace resident automation. SmartRent, PointCentral, DOOR (formerly Latch), and similar systems operate devices inside the property, including smart locks, thermostats, and unit-level monitoring. Envoy operates above the broader operational stack, and it can include resident automation state it can reach as part of the coordination and verification job. Where that monitoring is already present, Envoy absorbs it, verifies it, and expands it. Where it is absent, Envoy provides it. The systems coexist.

No. Envoy does not replace property management systems such as RealPage, AppFolio, Yardi, or Entrata. Those systems handle the administrative work: leasing, accounting, resident management, and work orders. Envoy carries the cross-system coordination and verification job above the existing stack.

No. Building management systems control and automate building infrastructure. Honeywell, Siemens, Johnson Controls, and Schneider are among the providers. Envoy operates above the control layer. It uses the monitoring and alert state it can reach as part of the coordination, response, portfolio-visibility, and documentation job. The building management system keeps performing its own function.

It can do that job, though it isn’t its primary role. IoT dashboards collect and display readings from connected devices and systems. Envoy provides a single view of monitoring, alerts, response, and records, so a dashboard whose job is to display readings is doing what Envoy already does. Envoy can replace it.

A dashboard shows readings when someone opens it, and Envoy watches them continuously and sends the alert when a reading crosses the line set for that property. A dashboard doing something else for you can stay in place, and Envoy can read from it where it is compatible.

Envoy does not replace leak detection vendors. Leak detection systems sense and alert for a specific failure mode. If leak detection is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it. Either way, Envoy connects the leak-detection state to response ownership and documentation, and puts it in broader portfolio context.

Envoy monitors property conditions and reports what it finds. It is not a burglar, fire, smoke, carbon-monoxide, or life-safety alarm, and it should not be used in place of one. Those need their own certified equipment that alarms locally at the property.

Where you already have them, Envoy can watch them. It monitors that the alarm fired, alerts the contact you assign, and records the event, without replacing the alarm itself.

Envoy does not replace inspection software. HappyCo and similar tools produce point-in-time condition records through scheduled inspections. Envoy produces a continuing operational record from the monitoring state and work it observes between inspections. The two systems serve different points in the operational timeline.

ObjectSpectrum builds and operates Envoy on Prism. A partner pays ObjectSpectrum on a recurring basis. It deploys Envoy across the properties or customer relationships it manages, and it owns the operator relationship. The partner may attach Envoy as a recurring service, bundle it into an existing service, or absorb the recurring cost against its own operational savings.

A partner brings Envoy into customer relationships it already owns. Depending on the partner’s model, it may attach Envoy as a recurring operational service, include it in a broader managed-service offering, or fund it across its managed book. The operator experiences Envoy through the partner’s customer-facing service.

Partners build recurring economic value by deploying Envoy across the properties or customer relationships they manage. A partner may charge for Envoy as part of a recurring service, bundle it into an existing agreement, or absorb the cost where the operational savings justify doing so. Pricing, rates, tiers, margins, and commercial terms are not published on this website.

ObjectSpectrum builds and operates Envoy on Prism. It provides the product, operates the platform underneath it, and supplies partner enablement, technical support, and continuing product investment. A capability running on Prism is not automatically a current capability in Envoy.

The partner pays ObjectSpectrum on a recurring basis. It owns the deployment and the customer relationship, and it carries the customer-facing operational service. The partner deploys Envoy across the properties or customer relationships it manages, rather than treating Envoy as a one-off introduction.

Deployment is partner-led. It starts by defining the properties, the monitoring scope, the coverage area, response ownership, and which existing systems are in scope. Envoy-supplied monitoring is covered from the moment of deployment. Customer-supplied devices, systems, and integrations are verified wherever Envoy can reach them. The partner coordinates the operator relationship and the operational work around deployment.

Deployment timing depends on portfolio size, property access, the monitoring already in place, integration requirements, and the partner’s operating plan. The scope and sequence get set with the partner before rollout. There’s no single deployment timeline that fits every case.

It depends on what’s already there. Where an operator already has monitoring, Envoy works with the devices, systems, and integrations it can reach. Some integrations may need connectivity hardware. Where monitoring doesn’t exist for a required failure mode, Envoy provides monitors as part of the deployment. The current set includes water leak detection, temperature, humidity, mold condition detection, power, internet connectivity with router reboot, occupancy and motion, and geo-locating and geofencing for on-site movable assets. If the monitoring is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it.

Existing monitoring stays in place and keeps performing its own function. Envoy verifies customer-supplied monitoring wherever it can reach it, connects alerts to response ownership and portfolio context, and documents the state and work it observed. Envoy does not represent unreachable devices, systems, properties, or historical events as verified.

ObjectSpectrum is the company that created Equipment Intelligence and builds and operates Prism. Envoy is one of several productized solutions built on Prism. ObjectSpectrum builds and operates Envoy.

Prism is the platform ObjectSpectrum builds and operates beneath Envoy, its other productized solutions, and its custom client work. Envoy runs on Prism, but Prism’s capabilities and Envoy’s capabilities stay separate. A capability can run on Prism without sitting inside what Envoy currently offers, and features ship in Envoy, never on Prism.

Prism has been in production across client deployments for over ten years. Machine learning has been operating in live environments, not in demo decks. Not every Prism capability is currently included in Envoy.