AppFolio vs. Beagle: is anyone actually winning?!

AppFolio and Beagle are locked in three lawsuits over platform access and security. AppFolio says Beagle illegally accessed accounts; Beagle claims AppFolio blocked them to protect a $75 million rival investment in Second Nature. Neither side is winning yet, but the case exposes a bigger fight over who controls API access in property management.
Chapters
It's time for an update on the Beagle versus AppFolio lawsuit. Juicy, I know. So I've been kind of quietly keeping an eye on this in the background. If you're not familiar, Beagle is a company that provides renters insurance or renters insurance compliance, and they partner with property managers to help them do this. So there's a couple other companies that do this too. And Beagle got into trouble with AppFolio because AppFolio claims they were trying to circumvent some of their security protections and violating their license terms. and doing a bunch of other stuff. So AppFolio sued Beagle and blocked Beagle's access to AppFolio's platform. This is back in late 2025. And ever since then, they've been locked in this legal battle where they're going back and forth. There's actually multiple lawsuits happening at the same time right now across 3 different cases. And it's gotten really messy and complicated. Beagle is saying AppFolio is not allowing us to compete. They're being anti-competitive because they have a competing product Which is, you know, Second Nature. And AppFolio made a $75 million investment in Second Nature about a year ago as well. And they're saying, hey, this is really hurting us. If we're not allowed to integrate with AppFolio or use their platform to help our customers use our product, we're not going to be able to be successful and we're not going to be able to compete. And AppFolio is saying, that's not really our problem, first of all. And second of all, you illegally accessed accounts. You went in and set up user accounts in an attempt to hide from us. You know, they're calling them ghost accounts and they're basically saying, Beagle, you've been behaving very badly on our platform. They're claiming security risks and other things like that. So we don't know where this is gonna go. It is still pending and working its way through the courts, but I wanted to get an update on the situation. So I went and dug through all the court filings and figured out what the latest and greatest was. There's really no like smoking gun here yet. Neither of these parties to the cases has a clear upper hand right now. But it's always fun to sort of dig in and see what is going on with these 2 companies because Beagle is sort of infamous in our circles for being really aggressive with their cold calling. They call property managers pretending to be a potential customer to get the owner on the phone, and then they try and pitch them on their service, or at least that's what they were doing. I published an article about this earlier this year. Toto got involved in it as well, and it seems like we were actually able to kind of stop or alter the sales approach that Beagle had been taking, and that seems to have quieted down quite a bit. So that's great to see. But nevertheless, that made a lot of people annoyed at Beagle for doing that. So they're not exactly the perfect victim here. AppFolio, on the other hand, you know, all these claims of they're being anti-competitive, they're blocking access to their platform. There's a lot of questions around what is the obligation or how should it work with a system of record like AppFolio? Should they be required to give property managers access to their platform? Should they be required to do that for free? So there's a much bigger context that this all fits into, which I find very interesting. I was actually able to find another article covering the story from a different angle. There's a guy who's writing about it from the healthcare side of things. He's called the API Guy. His name is Brandon Keeler. He's a really nice dude. And his coverage of these questions about systems of record and who has access and what about a free API, paid API is really good. So I highly encourage you to check out his article if you haven't. He's been doing a great job covering this. So that's the latest. Unfortunately, there's not like a clear winner emerging yet. Yet, and the case doesn't seem like it's anywhere near being wrapped up, but I'm going to keep you up to date, so stay tuned.










