In November 2025, someone posted to r/Anki with a simple question: does Polar Bookshelf still exist?
They had discovered the app secondhand — told it could turn PDFs into Anki flashcards — and had gone looking for it. The Reddit thread they were reading linked to a betting site. A YouTube tutorial gave them enough context to type the right terms into Google; those led to the same betting site. They asked ChatGPT about Polar Bookshelf. ChatGPT gave them a friendly explanation, the app's old tagline, and the URL. The URL was the gambling site.
"Is this website still working???" they asked. "Does anyone know???"
Two days later, one reply: "Yeah it's gone. It was run by just one guy. He worked really hard at it but it never took off. I assume he cut his losses."
That is as close to an obituary as Polar has received.
Polar Bookshelf was, for a few years, one of the most-discussed reading tools on Hacker News. Its Show HN launch in October 2018 pulled 382 upvotes. At its peak the GitHub repo had around 4,500 stars. The developer claimed about 5,000 monthly active users. The app appeared in PKM-focused roundups and "second brain" tool lists throughout 2019 and 2020.
Today, the domain it lived at — getpolarized.io — has been taken over by squatters who cycle users through gambling-affiliate traffic. The main GitHub repository has been deleted. The founder has never publicly explained the shutdown. And people like the Anki poster above keep discovering Polar through old tutorials and AI chatbots, keep clicking the old URL, and keep landing somewhere they did not intend.
This is a short history of how that happened.
2018: local-first, open source, and a lot of hype
Polar launched in October 2018 as a local-first reading and annotation tool for PDFs, EPUBs, and captured web pages. It was built by Kevin Burton, a solo developer. The stack was Electron and TypeScript on top of Firebase auth; files were stored locally by default; the code was Apache-2.0 licensed on GitHub under burtonator/polar-bookshelf.
The pitch worked. The Show HN post drew hundreds of upvotes and a long comment thread. Early adopters liked the local-first story — PDFs stayed on your disk, highlights stayed yours, sync was optional. The personal-knowledge-management and incremental-reading communities, especially, latched on to Polar as the thing their workflow had been missing: an Anki-compatible spaced-repetition layer on top of PDFs they already read. The subreddit r/PolarBookshelf appeared. The project gained stars. For a few months after launch it looked like the right project at the right time.
It also looked, from the founder's own posts, like a project he was already struggling to fund.
2019: the frustration arc
Three months after launch, in January 2019, the founder posted on Hacker News: "I've literally LOST money open sourcing this... I'm -$1250 or so at this point."
In March, he asked for donations: "If you like Polar please consider donating... we've received essentially zero Open Source contributions from the community and very little funding."
In April, he put it more bluntly: "we've only raised about $500... I've probably made about $0.15 per hour... Consumers hate paying for software."
The same month, he launched a crowdfunding plea titled "Help me reboot the Internet", which earned 428 upvotes on Hacker News but did not materially change the economics. He framed users who had said they would donate around $27 on average as the community "failing to follow through."
There is nothing unusual about a solo developer running out of money. The noticeable thing, reading those posts now, is what the developer pointed at.
The Hacker News upvotes, the GitHub stars, the r/PolarBookshelf subreddit — the hype that had put Polar in front of developers in the first place — were reframed as a community that owed him. Users were "Consumers" who "hate paying for software." Stars and forks were "essentially zero Open Source contributions." A project that had leveraged open-source visibility to gain traction was publicly blaming open-source users for not also funding it.
This is a pattern worth watching in any early-stage tool. A developer whose public voice frames users as counterparties who owe them, rather than as customers to earn, is making a prediction. The tool will be worth what users are willing to donate to it — which, the developer will remind them, is never enough. When the funding gap can no longer be papered over with Stripe buttons and blog posts, something has to give. It rarely gives in the users' favor.
By October 2019, the founder described Polar as having about 5,000 monthly active users in a post looking for a co-founder.
A year later, Polar pivoted.
October 2020: the cloud-only pivot
On October 27, 2020, Show HN: Polar 2.0 appeared on the front page.
The new version was a different product. Local-first was gone. Polar 2.0 was cloud-only, required an account, and stored all your data in Firebase. Existing v1 users were migrated automatically; there was no path to stay on the local-first version other than pinning an old binary and blocking updates.
The pricing attached to it was ambitious. The free tier offered 1 GB of storage per account. A co-founder confirmed that existing v1 users were grandfathered to 2 GB. Premium went up to 500 GB of storage per paying user, with a 20% launch discount advertised in the Show HN post.
The comment section of the launch thread was largely hostile. A representative reaction from user ajvs: "the v2 update changes this from local or cloud storage to cloud only." tannerbrockwell described using Time Machine to restore the 1.x binary and blocking Polar from auto-upgrading. focus2020 wrote: "I am glad that forced me to look at other options and found Emacs pdf-tools mode."
Two problems were visible in that launch.
The first was the promise that had been broken. Polar's original appeal had been local-first — users who had chosen it over cloud-native alternatives had done so partly because it kept their files local. A forced cloud migration is not a feature release; it is a reversal of the contract. A tool that pivots out of the category it was chosen for will lose the users who chose it for that category.
The second problem was the economics. Every 1 GB free tier on Firebase Cloud Storage costs real money to the operator — the published on-demand rate at the time was on the order of $0.026 per gigabyte per month, before egress, Firestore metadata, and CDN. Every signup was now a recurring infrastructure bill for a two-person team with no venture funding. Every 500 GB premium account was a much larger one. The more successful the marketing, the faster the cash would burn.
Freemium math only works when your free tier's marginal cost is near zero, or when your paying users heavily subsidize the free ones. Polar's math was the opposite: generous free storage on per-gigabyte infrastructure, with premium tiers generous enough to swamp the subsidy ratio. That kind of freemium is sustainable for venture-funded companies that can lose money until one side of the flywheel catches up. It is not sustainable for a solo developer who was already $1,250 in the hole.
The Show HN launch surfaced both problems out loud, from the product's own power users. It is rare for the signal to be this explicit. The founder pressed on.
2021 to 2024: from open to opaque
On May 26, 2021 — seven months after the v2 launch — the polar-bookshelf GitHub repo was archived. A banner at the top informed visitors that there would be no further commits.
This was not the product's shutdown. It was the final step of the open-source-to-closed-core transition that had started with Polar 2.0 in October 2020. The OSS codebase had already stopped being the real product; archival closed its chapter officially. For paying subscribers already on the cloud-only 2.0, nothing changed on May 26, 2021. For everyone else, something important did. With archival complete, external visibility into Polar's development went to zero. New bugs, new features, retention trends, infrastructure decisions — all of it moved behind the Firebase account boundary. The only people who could tell whether the product was healthy were the ones operating it.
Before the public tracker froze, it had already told users something. A Wayback snapshot from June 2022 preserved 964 open issues against 584 closed — the state of the tracker at the moment it went read-only. More than 60% of reported problems sat unresolved, concentrated on Firebase and Firestore authentication failures, sync errors that dropped highlights, and cross-platform regressions on every major operating system. These were not cosmetic bugs. They were core-workflow failures on the primary promise — your annotations staying where you put them. The team that was now invisible had visibly been behind on maintenance before they went invisible.
From the outside, during the period that followed, the external signals were largely positive. getpolarized.io kept running, collecting email addresses and advertising a GPT-3-powered flashcards feature. The co-founder continued publishing Polar-branded product-update videos on his YouTube channel through January 2022. In March 2022, the AnKing — one of the largest Anki-focused YouTube channels — published a 16,000-view tutorial recommending Polar as a paid partnership, telling viewers "they were kind of a side project and now they've hired multiple people and are really taking off and improving things on a daily basis." The video included a 25% affiliate discount code.
All three signals may have been accurate when they were published. Scaffolding repos like polar-shared, polar-site, and polar-app-public did get sporadic updates through 2024, suggesting the commercial team was doing something in that window. The issue with these signals is not whether they were true in early 2022. It is that they were the only signals users had, and they did not expire. A user who found The AnKing's tutorial in March 2022 had different information than a user who found it in March 2024 — but the tutorial itself said the same thing. The last officially published build, version 2.0.103, appeared on a SourceForge mirror on May 3, 2022. Whatever happened between that build and the domain's lapse in late 2024, we do not know.
That is the underappreciated cost of the open-to-closed transition. Once the public repo was archived, there was no way for users to see when the commercial team slowed down, when the co-founder stepped back, when the founder moved on to other projects. The only signals available were marketing artifacts that continued to exist after the product did not.
The founder did not stop using Hacker News during this period; he just stopped mentioning Polar. His posting activity continued on other topics — language models, politics, geology — at the same cadence as before. A developer who has wound down a project but stays active elsewhere, without ever acknowledging the thing users trusted them with, is a different signal from a developer who goes dark across the board. Users cannot reach him about the product he built. But the account is still posting.
April 2023: the deletion
In April 2023, the GitHub repo moved from archived to gone. A URL that had returned a read-only page for almost two years now returned a 404.
Archival had been commercial logic. Deletion was not. The public OSS users who had been exiled in the October 2020 pivot were no longer customers; there was no business reason to touch their code, and no operational cost to leaving the archived repo in place. Deleting it was a discretionary act against an audience the product had already walked away from once.
A deleted repo is not the same as an archived one. Archival leaves the history available; community forks can still pull from their original upstream, rebase, and keep a fork alive. Deletion severs that history. Any clone or fork that had been created as a downstream of the main repo lost its upstream; GitHub stops linking the forks back to a parent that no longer exists. Even users who had stepped away from Polar could not easily maintain the 1.x local-first code they still relied on.
MobileRead, the long-running ebook community, has a precedent for community takeover of abandoned reading tools — there are threads documenting users carrying projects forward after their original developers had vanished. That takeover pattern requires the source code to remain available. The April 2023 deletion foreclosed it for Polar. There was no longer a canonical repository to fork, no history to rebase against, no authoritative tag for the last stable build. Community forks that survived — half a dozen scattered mirrors with zero or one star each — were effectively orphaned in place, their commits no longer connected to any larger project.
Archiving tells the world: this is frozen, but you can still study it and build on it. Deletion tells the world: the thing no longer exists, and neither does its lineage. For a tool that thousands of people had used to annotate their personal libraries, the choice to delete rather than archive was not a neutral cleanup step. It was a second shutdown, two years after the first.
Late 2024 to early 2025: the domain squat
By late 2024, getpolarized.io was no longer serving the old landing page. The domain had lapsed. Sometime between then and the first quarter of 2025, it was picked up by a squatter. An ArchiveBox issue from March 23, 2025 documented it serving a Thai gambling site at that point. Squatter funnels rotate their destinations, and the redirect chain has rotated since — as of early 2026 the chain routes European traffic into a sports-stats domain that blocks EU visitors with an HTTP 403, a well-known architecture for sportsbook-affiliate monetization targeting permissive jurisdictions. The specific endpoint is less interesting than the pattern: users from old tutorials keep arriving, and someone is converting the traffic.
A lapsed domain that gets picked up by an unrelated business is a routine operational event. What made this particular takeover consequential is that every reference to Polar across the internet — years of Hacker News threads, YouTube tutorials, blog roundups, subreddit posts, AI chatbot training data — pointed at that same URL. Six years of accumulated recommendation inventory began delivering users into the squatter chain.
The Reddit poster from r/Anki in November 2025 was one of the casualties: three independent discovery channels, all routing into whatever the squatter chain was serving that week.
This is a problem that barely existed in the early web and is especially pronounced now. A product built in 2018 accumulates links — organic links, tutorial links, review links, mentions on Hacker News, explanations in Stack Overflow answers, recommendations baked into AI model weights. Those links have no expiration date. When the product dies, the recommendation inventory keeps delivering traffic for years, now to whatever takes over the URL. For a PDF reading tool with loyal early adopters and a multi-year presence on HN, the residue is a substantial long tail. For an AI chatbot whose training data included the original hype, the residue lasts until the model is retrained — and often beyond, because product launches leave a louder footprint in training data than silent shutdowns do.
The audience that never arrived
A final thread is worth pulling. Polar's hype lived on Hacker News, Product Hunt, and Reddit — specifically the personal-knowledge-management and "second brain" subreddits and r/PolarBookshelf. Those audiences are real and active. They are not, on the whole, the audiences that pay premium subscriptions to reading software.
The audience that does — serious ebook readers with libraries of thousands of books, the people most likely to convert into $60-a-year paying users for a great reading tool — mostly lives on MobileRead. MobileRead discussed Polar exactly once, in February 2019. A user posted about discovering it. Another user pointed out Polar only handled PDFs (EPUB support would not arrive until the cloud-only 2.0 pivot a year and a half later). The original poster self-corrected ten days later, noting that Polar's own recommendation was to convert EPUBs to PDFs in Calibre as a workaround. The thread died. No MobileRead user ever started a follow-up thread about Polar. No migration thread appeared after the shutdown. No "what's replacing Polar" post. The serious-ebook audience looked once, saw the format gap, and moved on.
This is a kind of signal that is hard to see at the time. A tool being loved by the hype audience tells you about the hype audience. It does not tell you whether the paying audience exists. If the paying audience is silent in the places you would expect it to show up, the economics are harder than they look. Polar was popular in communities full of people who enjoy trying new software. It was never popular in a community full of people who buy reading software.
What was visible all along
The closing pattern is not one thing. It is several smaller things that, read together in 2019 and 2020, would have suggested caution.
The founder's voice, starting in early 2019, framed users as counterparties who owed money rather than as customers who had been promised anything. The pricing math attached to Polar 2.0 relied on Firebase storage economics that do not survive generous free tiers and a two-person team. The product's own power users revolted on the October 2020 Show HN thread and said out loud that the broken local-first promise was disqualifying. The issue tracker accumulated unresolved sync and auth bugs on the product's core workflow. The paying audience never really arrived; the hype audience never really paid.
None of these was hidden. The blame-users arc is on Hacker News with a date attached to every post. The 500 GB-per-premium-user pricing is quoted in a Show HN comment. The frozen issue tracker is still accessible through the Wayback Machine. The MobileRead non-engagement was a thread anyone could read. Taken together, a careful buyer in October 2020 had most of the information they needed to decide against putting a personal library of PDFs behind a Polar account.
The signal that mattered most was the pivot itself. Polar's transition from open-source local-first to closed-source cloud-only in October 2020 was the moment the early-warning system stopped working. Before the pivot, users could read the code, watch the issue tracker, and fork the project if the team lost interest. After the pivot, all of that became invisible. The subsequent archival in 2021 was just the formal end of a window that had already been closing for months. Any tool that goes through a similar transition — open source to closed, local to cloud, community-maintained to commercially operated — is asking its users for a new kind of trust. Users should count that ask as a material change in the deal, not a feature release.
Most people did not read these signals together. Most people saw the Show HN, the positive comments, and a product that looked good. That is the pattern worth leaving with: sustainability signals tend to be public, individually small, and only load-bearing in aggregate. None of the individual data points predicts a shutdown. All of them together predict the likelihood of one.
The category Polar served best — incremental reading of PDFs with spaced-repetition integration — is still under-served seven years after its launch, and will probably be served next by a tool built on someone else's mistakes. When that tool arrives, the questions that would have warned a reader away from Polar are the questions worth asking of it too.