Every property manager running AppFolio has handed a vendor a login at some point. A leasing bot, a maintenance coordinator, a compliance tool: something that needed to reach into your PM software and touch real data. Most of the time, nobody thinks twice about it.

Beagle built an entire company on that assumption. For the better part of a year now, AppFolio has been trying to prove the assumption was wrong, and the fight has turned into one of the more revealing lawsuits in proptech.

I've covered this story as it's developed. Since my last update, a lot more of the actual mechanics have surfaced, including exactly how Beagle operated inside AppFolio's platform, step by step. It's worth walking through the whole thing, because however this case ends, it's going to set the tone for every add-on vendor sitting on top of a property management system of record. Not just this one.

The Short Version, If You're Just Catching Up

Beagle sells insurance compliance services to property managers: chasing down proof of renters insurance, auto-enrolling non-compliant tenants in liability waivers, that kind of thing. More than 80% of its customers run on AppFolio, and until recently, Beagle got into those accounts the way a lot of point solutions do when there's no real integration. Property managers created a login for Beagle and let it work inside their AppFolio account directly.

In December, AppFolio decided that had to stop. It sued Beagle, told property managers by mass email that Beagle's setup created "serious security risks," and moved to cut off access within five business days. Beagle sued back, alleging AppFolio was running "a systematic campaign to destroy Beagle's business," and asked for an emergency order forcing AppFolio to restore access. That request was denied, and so was Beagle's motion to reconsider, and a second motion to reconsider. Beagle appealed to the Ninth Circuit on April 7. (The Daily Journal covered that first stretch of the case in more detail.)

As of this writing, the appeal is fully briefed, though notably, Beagle isn't even asking the appellate court to rule on the merits. It's asking for a hearing where the engineers on both sides can be cross-examined about what AppFolio's alternatives can actually do. That alone tells you how technical this case has become, and it's what's new since my last check-in: a much clearer picture of what Beagle was actually doing inside AppFolio's platform, and why "just use the alternatives" isn't the clean answer AppFolio wants it to be.

Here's a video I put together covering the early days of the lawsuit, if you want the backstory in full:

What Beagle Was Actually Doing In There

For a long time, the honest answer to "what was Beagle doing inside AppFolio" was murky, even to the lawyers arguing about it. That changed when a property manager forwarded AppFolio his full correspondence with Beagle, including an AI notetaker's summary of an onboarding call. (If you're using a meeting bot on vendor calls, that transcript doesn't just evaporate. File that away.)

Once that surfaced, the process turned out to be pretty methodical:

  • Provisioning. A Beagle rep walks the property manager through creating a new user on a live call: first name "Compliance," last name "Reports," role set to Accounting/Accountant. The invite gets routed to a custom domain, essentially a reports inbox.
  • The audit. Beagle pulls the tenant roster, checks it against policy data, and produces a list of who's out of compliance on renters insurance.
  • Notice and enrollment. Beagle emails the non-compliant tenants from its own domain, verifies any policy they upload, and auto-enrolls the rest in a monthly liability waiver.
  • The write. This is the part that matters legally. Beagle doesn't just read data, it writes it. It posts recurring charges against non-compliant tenants directly, and where the property manager has a competing product like AppFolio's own FolioGuard, it disables that subscription.
  • Money routing. Beagle has the customer open a support ticket with AppFolio asking to suppress those line items from owner statements, so the waiver income shows up as the property manager's revenue rather than getting passed through to the owner.
  • Exit. About five days later, Beagle's account manager follows up and suggests deleting the user account they just created, since Beagle can run off scheduled reports going forward.

That last step is the one AppFolio has leaned on hardest. A "temporary" login that gets deleted after a handful of days, on a pattern repeated across more than 800 accounts by AppFolio's count (57 of them renamed mid-dispute, across eight domains, according to the court's own findings), is a hard thing to wave off as routine vendor access.

Why "Alternatives" Isn't a Clean Answer

AppFolio's defense, in large part, is that Beagle had legitimate options and chose the risky one instead. There are technically three paths:

  • Scheduled Reports. Any customer can configure these in a few minutes, delivered to any inbox. The catch: read-only. A CSV report can't write a charge back to the ledger, which is the entire second half of what Beagle's service does.
  • Database API. The customer's own programmatic access to their data. Read access requires AppFolio's Plus tier; write access requires Max. Even on the top tier, this still runs through the customer, which, if you squint, looks a lot like the exact account-sharing arrangement AppFolio is suing over in the first place.
  • Stack API. The actual partner marketplace, and the only path with real write access to things like recurring charges. It requires AppFolio's approval, at AppFolio's discretion.

It's worth knowing AppFolio isn't neutral on Beagle's category to begin with. It sells its own competing product, FolioGuard, and holds a minority stake in Second Nature, one of Beagle's direct rivals in the renters-insurance-compliance space (background on that investment here). None of that makes AppFolio wrong on the legal merits. But it's useful context for why "just apply to our marketplace" hasn't exactly been a warm welcome here.

Beagle argues none of the three paths were viable at the time it needed them. AppFolio argues Beagle didn't try hard enough, and points to Beagle's own CEO undercutting the emergency-order request by telling a customer the fix was "simple." That contradiction, the "simple fix" email versus the "no viable alternative" court filing, is a big part of why the January restraining order got denied.

Where the Law Actually Sits

On the antitrust piece, Beagle has a real headwind. AppFolio says it has roughly 9 million units on its platform, out of about 52 million residential rental units nationally, which is under 17% of the market, and behind both RealPage and Yardi. That's well short of the roughly 30% threshold courts generally treat as a floor for a monopolization claim, and AppFolio isn't even the market leader in its own category.

On the computer-misuse side, AppFolio is showing up with real evidence: internal emails, and a sample of just three accounts tied to 633 recurring resident charges worth roughly $9,575 a month. That's not a smoking gun on its own, but it's the kind of specific number that's hard to argue around.

Beagle's best argument is simpler than any of that: the data belongs to the property manager, and the property manager chose to let Beagle in. A terms-of-service violation isn't automatically the same thing as unauthorized access under federal computer fraud law. Beagle is leaning on the hiQ v. LinkedIn line of reasoning here, the same argument that's protected scrapers and other vendors in prior cases. Whether it holds up when the access method looks this deliberate is the actual question in front of the Ninth Circuit.

No Cures Act for Property Management

Here's the part I find most interesting, and credit belongs to Brendan Keeler, whose deep dive on this case is genuinely worth your full attention if the topic interests you at all. Keeler covers healthcare software for a living, and he pointed out that this exact fight, a point solution locked out of a system of record, plays out constantly in healthcare too. The difference is that healthcare has the 21st Century Cures Act, which spells out when a system of record has to let a vendor in, on what terms, and for what fee.

Property management has none of that. AppFolio said as much, more or less, in its own court filing. He unearthed this notable quote:

…There is no statutory scheme here that governs data sharing among property managers. There is no body of law that regulates the exchange of data among property managers. There is no public policy reason that a privately-held company should be required to share its property management data with third-parties. AppFolio, like virtually all companies in the United States, is free to determine with whom it wants to do business.

As Keeler frames it, healthcare got its rules because Congress legislated them. Property management, and honestly most industries outside healthcare, is running the same fight with no rulebook at all.

That's not a knock on AppFolio specifically. Any system of record in our industry, whether that's AppFolio, Buildium, Rentvine, or anyone else, operates under the same legal obligation to let outside vendors in, which is to say: none.

What This Means If You're Not AppFolio

You don't need to be running AppFolio or using Beagle for this to be relevant. Every PM company has some version of this stack: a core system of record, plus a handful of point solutions bolted on through logins, screen-scraping, or half-supported integrations because a "real" partnership never got approved.

Ask yourself two questions about every vendor in that category. What data are they actually touching, and would you be comfortable if your PM software's legal team read the honest answer? And second: if that vendor got cut off tomorrow, what would actually break in your operation?

I don't think most operators have a clean answer to either question right now. This case is a pretty expensive way to find out yours.

Where This Goes From Here

The judge has already ordered both sides into private mediation, due by November 2. Given that neither side has won a single emergency motion and a trial this complex is genuinely expensive to run, I'd bet on some negotiated outcome before this ever reaches a jury: a sanctioned form of access, a fee arrangement, or the two companies just walking away from each other. If it doesn't settle, jury trial is scheduled for September 28, 2027, which tells you everything about how slow this kind of case actually moves.

Either way, Beagle stays cut off from AppFolio's data in the meantime. That part isn't up for negotiation until one side blinks.

-Peter

Further reading: Brendan Keeler's full case breakdown, "The Dogs of (Platform) War," covers the legal timeline in more technical detail than I have room for here.