Libby Isn't Your Library. It's a Private Equity Asset.

Ask a patron where they get their library ebooks and a lot of them will say "Libby." Not "OverDrive," not "my library's vendor." Libby. The cheerful app with the card-stock colors that feels like a branch you carry in your pocket. That feeling is the product working exactly as designed, and it is worth taking a minute to look at who actually owns the thing.

Libby is the reading app made by OverDrive¹, the dominant digital-lending platform for U.S. public libraries. OverDrive was founded in Cleveland in 1986 by Steve Potash. In 2015 the Japanese conglomerate Rakuten bought it for about $410 million. And in 2020, Rakuten sold it to KKR² — one of the largest private-equity firms in the world.

The price was never officially disclosed, which is itself worth noting; you can infer roughly $775 million from Rakuten's own reported profit on the sale. But the number matters less than the category. The app your patrons treat as a civic institution is a portfolio asset of a global buyout firm, bought and sold like any other.

Your library is not the owner of Libby. Your library is a customer of it. The distinction is the whole thing.

Now follow it one step further

Here is the fact that reframes the rest. In October 2023, KKR completed a $1.62 billion acquisition of Simon & Schuster³, one of the Big Five trade publishers, from Paramount.

So as of now, a single private-equity firm owns both the platform that libraries license ebooks through and one of the publishers that libraries license ebooks from. KKR sits on both sides of the table at which your library negotiates digital content. It owns the rails, and it owns some of the cargo.

I want to be careful and precise about what that does and doesn't mean. I am not telling you KKR coordinates Simon & Schuster's library licensing terms with OverDrive's platform pricing to squeeze libraries. I have no evidence of that, and large funds run portfolio companies at arm's length as a matter of routine. What I am telling you is the documented structural fact: the concentration is real, it is in one set of hands, and it is the kind of arrangement libraries should be able to see clearly and ask about — not discover by accident.

What ownership buys you the right to do

Ownership isn't abstract. It decides what the platform is for. A library-owned cooperative builds the platform to serve circulation. A buyout firm builds it to produce returns on a fund's timeline. Those two goals overlap a lot of the time, and then at the margins they don't, and the margins are where patrons live.

You don't have to theorize about this. Look at what OverDrive shipped this spring: Amplify, a service that turns "hundreds of millions of monthly reading sessions across Libby and Sora" into analytics it sells to publishers. The reading behavior your patrons generate, aggregated into a product. That is not a library-cooperative instinct. That is an owner looking at an asset and asking what else it can be made to yield. Same pattern, same owner, one rotation further along.

What this isn't, and what it is

This is not a claim that KKR is uniquely villainous, or that OverDrive is a bad product. Libby is, genuinely, a good app; the people who build it are good at their jobs. Private-equity ownership of library infrastructure is not a scandal, it's a condition — and a widespread one. OverDrive (KKR), Ex Libris (Clarivate), SirsiDynix (Constellation), Follett (Francisco Partners): the rails libraries run on are, overwhelmingly, owned by firms whose customers are their investors, not their patrons.

The point isn't to make you cancel Libby. It's to make you stop mistaking it for your library. Your library is the institution, the staff, the card, the right to read without being sold. Libby is a vendor relationship that currently runs through a KKR balance sheet. Naming that correctly is the precondition for everything else.

What libraries can actually do

• Say it plainly to your board and your patrons. Not "Libby is evil." Just: the app is a vendor product owned by a private-equity firm, the library is a customer, and the library's job is to negotiate from that footing rather than treat the vendor as a partner with shared goals.
• Read the data terms. Now that the owner is monetizing reading behavior, your contract's usage-data and analytics clauses are the thing that decides whether your patrons are in the dataset. Ask, in writing, whether your library's activity feeds Amplify and whether you can opt out.
• Know your library-owned alternatives. The Palace Project and Library Simplified, run by the nonprofit LYRASIS, are open-source digital-lending layers libraries help govern. Cooperative and author-paying models exist. None are turnkey drop-in replacements for OverDrive's catalog reach, and pretending otherwise helps no one — but knowing they exist is how you negotiate, and building them is how the next generation of rails ends up owned by the institutions that depend on them. That's the entire reason I build the co-op versions.

The app feels like the library because it was built to. The ownership record says otherwise, and the ownership record is the part that decides what gets built next.

Filed June 2026. No corrections to date.