What is the RealPage EliseAI integration pause? The RealPage EliseAI integration pause is RealPage's October 8, 2026 decision to suspend all new EliseAI site activations under its RealPage Exchange agreement while leaving existing integrations running. For multifamily operators, it is the first time a dominant property management system has cut off a major AI vendor mid-deployment, exposing a risk almost no AI diligence tests: the AI you bought runs on a pipe a third party controls. For the wider vendor landscape, start with our buyer's guide to AI property management platforms.
Key Takeaways
- RealPage paused new EliseAI site activations on October 8, 2026, citing EliseAI's failure to submit its Apollo agent for review under their integration agreement.
- Existing integrations keep running, but operators mid-rollout cannot turn EliseAI on at properties that were not already live.
- EliseAI powers roughly one in six U.S. apartments by its own count and raised $350 million at a $4 billion valuation on September 29, 2026.
- RealPage announced a competing front-office integration with Funnel on October 13, 2026, five days after the pause.
- Integration continuity, not model quality, is the diligence question that decides whether your AI stack survives a vendor dispute.
What RealPage Actually Did
RealPage suspended new EliseAI activations, not existing ones. Properties already running the integration keep working. Properties scheduled to go live, including acquisitions and lease-ups being added to an existing EliseAI contract, cannot be activated while the review runs. RealPage President and CEO Dirk Wakeham framed it as a governance review, not a termination.
Wakeham's stated reasons were specific. "EliseAI never submitted Apollo for review, and we can't assess what we haven't seen," he told Multifamily Dive in reporting published October 12, 2026, adding that RealPage had "reports of them actively trying to work around our controls and outside our agreement." EliseAI says RealPage's claim that it used the API in prohibited ways is false. The two had operated under an integration agreement for three to four years, revised in 2024, limiting EliseAI to specific, agreed-upon use cases.
Wakeham said the pause lifts once EliseAI shows the integration is, in his words, "safe and secure and governed and has the right performance monitoring." That is solvable, and the point is not whether they reconcile. It is that a contract between two vendors, which no operator signed and most have never read, decided whether software they pay for works at their next property.
Why Apollo Triggered the Dispute
The trigger was a product, not a billing fight. EliseAI launched Apollo on September 3, 2026 as a single agentic AI teammate that can perform any task inside the Elise platform and inherits each user's permissions. We flagged permission inheritance as the part operators should scrutinize in our analysis of EliseAI's Apollo agent.
That architecture is what RealPage objected to. An integration scoped to specific use cases assumes the connecting software does a bounded set of things. An agent that can perform any task in its platform, reaching through an API into the system of record, is not bounded that way. The agreement was written for a chatbot answering leasing inquiries. Apollo is a different category of software riding the same connection.
This is a structural problem agentic AI creates across the CRE tech stack, not a RealPage quirk. Integration agreements signed in 2022 and 2023 describe what data a partner may read and write. They rarely describe what an agent may decide.
The Real Risk Is Integration Dependency
The risk that matters is integration dependency: your AI vendor's usefulness rests on a connection another company can suspend without your consent. Buyers benchmark accuracy, speed, and price, but rarely ask what happens when the pipe closes.
This is not a one-off. Funnel gave EliseAI a revised agreement in late 2025 tying continued CRM access to a promise not to replicate certain functionality, and EliseAI declined to sign, leaving operators running both tools exposed. Two platforms have now used integration access as leverage against the same AI vendor inside twelve months.
The exposure is wide because multifamily stacks are fragmented. NMHC and RealFoundations research on customer experience technology found most operators run 10 to 20 solution providers across the resident journey. Every connection between two of them is a contract you never signed.
Price the downside before it happens. Say your staffing model assumed an AI leasing agent would let you run a region one leasing associate lighter. If the integration stalls and you re-add that role at $55,000 fully loaded, NOI falls $55,000 per year, since salaries are an operating expense. At a 5.5% cap rate, that recurring expense costs roughly $1.0 million of value at disposition. A lease-up delay is different: lost rent during a slow month is a one-time cash flow hit that damages IRR but does not capitalize into value. Knowing which one you face decides whether this is an annoyance or a valuation event. CRE operators who want help stress-testing an AI stack can reach out to Avi Hacker, J.D. at The AI Consulting Network.
What the Funnel Deal Signals
Five days after pausing EliseAI, RealPage announced an integration partnership with Funnel on October 13, 2026, putting RealPage screening, payments, pricing, and availability tools inside Funnel's renter workflow. Funnel CEO Tyler Christiansen said "the future of multifamily will be built by best-in-class platforms working together." Wakeham noted several of RealPage's top 10 customers are Funnel customers and that the deal had been in development for months.
Read the two events together and the signal is clear: the system of record now picks which partners reach its data. That is a different market than the open-integration era operators bought into, and it sharpens the procurement question we raised when Yardi shipped its own AI layer in Yardi Virtuoso Enterprise. A platform that sells AI and gatekeeps rival AI has an obvious incentive problem. Price it in rather than assume neutrality.
None of this means specialist tools are a bad bet. EliseAI passed $200 million in annual recurring revenue in June 2026 and raised $350 million led by Andreessen Horowitz and Bessemer Venture Partners. Specialists still ship faster than suites on narrow workflows. That bet simply carries a dependency the suite bet does not, and it belongs in your contract.
Five Contract Terms to Add Before Your Next AI Renewal
- 1. Integration continuity: Require the vendor to disclose every third-party integration your deployment depends on and to notify you within five business days of any suspension or material change in access.
- 2. Activation rights: Tie fees to your ability to activate new sites. If the vendor cannot onboard a property you paid to cover, that property should not be billable.
- 3. Data export on demand: Require structured export of conversation logs, maintenance records, and resident interactions at any time, not only at termination. If an integration dies, the record of what your AI told residents is evidence you will need.
- 4. Scope-change disclosure: Require written notice before the vendor materially expands what its agent can do through an existing integration. Apollo is the cautionary tale.
- 5. Termination for integration failure: Add a no-penalty exit if a required integration stays down past a defined window, such as 30 or 60 days.
Run the same questions at your system of record. Ask who approves partner integrations and whether the platform sells a product competing with the partner you are about to buy. The AI Consulting Network specializes in exactly this kind of vendor and contract diligence.
What Operators Should Do This Quarter
Start with an inventory, because most firms cannot name their dependencies. List every AI tool in production, the system of record it reads from, and which properties are live versus pending. Pending is where a pause bites.
Then define a manual fallback for each AI workflow. If your leasing agent stops onboarding properties next month, who answers inquiries, and what does that cost per property per month? Write the number down. Operators who demand hard performance data up front tend to be the ones with a credible fallback, a point we made in our analysis of AI work order completion rates. Watch NMHC's technology trends coverage too: standardized terms would help operators more than any single vendor win.
Frequently Asked Questions
Q: Does the RealPage pause break EliseAI at properties already using it?
A: No. RealPage suspended new site activations only, and existing integrations continue to run. The operators affected are those adding properties to an existing EliseAI contract, including acquisitions and lease-ups scheduled to go live after October 8, 2026.
Q: Why did RealPage object to EliseAI's Apollo agent specifically?
A: RealPage says Apollo was never submitted for review. The agreement limited EliseAI to specific, agreed-upon use cases, and Apollo can perform any task inside the EliseAI platform, which RealPage argues exceeds that scope. EliseAI disputes that it misused the API.
Q: Should operators stop buying specialist AI tools and buy from their system of record instead?
A: Not automatically. Specialists usually ship better narrow workflows, and EliseAI's $200 million in annual recurring revenue reflects real adoption. Price the dependency rather than avoid it: require integration continuity terms, activation-based billing, and a no-penalty exit if a required connection stays down.
Q: What does an integration cutoff actually cost a multifamily portfolio?
A: It depends on whether the cost is recurring or one-time. Re-adding a leasing role at $55,000 fully loaded is a permanent operating expense that lowers NOI by that amount annually and cuts value by roughly $1.0 million at a 5.5% cap rate. A lease-up delay is a one-time cash flow loss that hurts IRR without capitalizing into value.