42
Reviewed scope
scoped operator namespaces
ERP and business systems · October 2026 research
Review 42 operator namespaces with published Yardi workflow declarations or observations of their corporate websites. Of these, 33 support only the RentCafe public website platform. Keep those website observations separate from Voyager and property-management ERP research.
Research dated 2026-10-25. Original source dates and website scope stay with the records.
42 scoped operator namespaces
Research dated
Contact-free research examples · CSV
Review 42 operator namespaces with published Yardi workflow declarations or observations of their corporate websites. Of these, 33 support only the RentCafe public website platform. Keep those website observations separate from Voyager and property-management ERP research.
Download the 3-row CSV preview42
scoped operator namespaces
33
scoped operator namespaces
Sources were checked on 24–25 October 2026. A source check dates the declaration or website observation, not adoption or current runtime.
Research summary and contact-free examples only. Full-file commercial delivery and source reproduction rights remain unresolved.
CSV columns: name · domain · sourceClass · checkedOn · scope
These approved examples illustrate the 2026-10-25 research. They are not a representative sample of all customers.
fidumpm.com
Company property-management service declaration · 2026-10-25
The company service page describes maintaining financial and lease records in Yardi Voyager. Specific property coverage, current runtime and paid status were not verified.
rentarnel.com
Company-bound public website configuration · 2026-10-25
The company-branded website supports a RentCafe public website observation only. Voyager, ERP, resident operations, portfolio coverage and paid status were not established.
bridgepm.com
Company-bound public website configuration · 2026-10-25
The company-branded website supports a RentCafe public website observation only. Voyager, ERP, resident operations, portfolio coverage and paid status were not established.
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
33 of 42
33 of the 42 reviewed operator namespaces support only the RentCafe public website platform. Website-platform observations cannot establish Voyager or property-management ERP use.
The count covers grouped operator namespaces. Legal-company customers, paid deployments, portfolio coverage and whole-organization use remain unverified.
Research 2026-10-25 · scoped operator namespaces · WhosBuilt saved-record analysis
Company workflow declarations retain their stated modules and limits. Property, client, resident and portal-user counts add no operator namespaces.
The count covers grouped operator namespaces. Legal-company customers, paid deployments, portfolio coverage and whole-organization use remain unverified.
Research 2026-10-25 · scope and grouping rule · WhosBuilt saved-record analysis
Source checks span 2026-10-24–2026-10-25. Retained observations and examples keep their original dates.
Review 42 operator namespaces with published Yardi workflow declarations or observations of their corporate websites. Of these, 33 support only the RentCafe public website platform. Keep those website observations separate from Voyager and property-management ERP research.
| Source class | Count | Scope |
|---|---|---|
| Company property-management service declaration | Not separately counted | scoped operator namespaces |
| Company-bound public website configuration | Not separately counted | scoped operator namespaces |
RentCafe website scope: scoped operator namespaces Sources were checked on 24–25 October 2026. A source check dates the declaration or website observation, not adoption or current runtime.
Operator grouping: scoped operator namespaces Sources were checked on 24–25 October 2026. A source check dates the declaration or website observation, not adoption or current runtime.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.