[{"data":1,"prerenderedAt":34},["ShallowReactive",2],{"arch-deep-/architecture/integrations/realpage":3},{"id":4,"title":5,"body":6,"category":23,"deepPage":24,"description":25,"extension":26,"layer":27,"meta":28,"navigation":29,"path":24,"relatedFlows":30,"replaces":30,"seo":31,"stem":32,"__hash__":33},"architecture/architecture/integrations/realpage.md","RealPage integration",{"type":7,"value":8,"toc":19},"minimark",[9,13,16],[10,11,12],"p",{},"RealPage is the second of the two dominant property management systems in the residential operator market. The integration covers the OneSite product line for traditional multifamily and the Investment Management Services platform for institutional asset operators, behind the same operating-layer contract used for Yardi.",[10,14,15],{},"The integration consumes RealPage as the system of record for lease, ledger, and unit-state data. The orchestration is one-directional from RealPage on lease and tenancy facts, and bi-directional on operational events that need to land in RealPage's ledger — amenity charges, late fees, deposit holds, refunds. The wrapper normalizes the shape of these events so the building's books reflect the resident's actual experience, not a vendor-specific schema.",[10,17,18],{},"Failure modes are explicit. If RealPage is unreachable, the operating layer continues to serve resident workflows from cache and queues outbound events for reconciliation when the link returns. The behavioral standard scores the resident-facing experience, not the integration's uptime — a Yardi-backed building and a RealPage-backed building produce the same resident behavior or they do not meet the standard.",{"title":20,"searchDepth":21,"depth":21,"links":22},"",2,[],"integration","/architecture/integrations/realpage","RealPage OneSite and IMS wrapped through the property management integration layer.","md","4",{},true,null,{"title":5,"description":25},"architecture/integrations/realpage","BKGAjC_ZoRD0sfElKMBhbGBux8cr4UbJo9g3r6crPJk",1779718756836]