Direct comparison
LibKey Nomad vs BrowZine vs Lean Library
Two are Third Iron products; the third left SAGE in 2025. What the library configures, and what the researcher sees when access fails.
Ask about LibKey Nomad vs BrowZine vs Lean Library
Answers are drawn from this comparison and the rest of the CASRAI corpus, with a link to every source.
Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this
How do LibKey Nomad (Third Iron), BrowZine (Third Iron), Lean Library (independent) compare side by side?
The table below compares LibKey Nomad (Third Iron), BrowZine (Third Iron), Lean Library (independent) across 12 procurement-relevant dimensions, from what it actually is through pricing.
Side-by-side comparison
| Dimension | LibKey Nomad (Third Iron) | BrowZine (Third Iron) | Lean Library (independent) |
|---|---|---|---|
| What it actually is | Browser extension that injects library holdings into third-party sites the researcher is already on (PubMed, Wikipedia and others). | Journal-first browsable shelf of the titles the library holds, with new-issue alerting and a personal bookshelf. | Browser extension that surfaces library services as well as content — LibGuides, LibChat and custom messaging in context. |
| Vendor and current ownership | Third Iron, LLC (affiliate BZ DISC, Inc. named in its privacy policy). | Third Iron, LLC — the same vendor as LibKey Nomad. Not a competitor to it. | Independent since 16 December 2025, when SAGE Publishing announced its sale to a management group. Was a SAGE product from September 2018. |
| Primary problem it solves | Friction getting to a known article, in the moment. | Current awareness — knowing what a field has published this month. | Library visibility inside the user workflow, plus access. |
| Underlying holdings data | The library knowledge base (KBART) — shared with BrowZine by design. | The same Third Iron holdings data as LibKey Nomad, which is why the two never contradict each other. | Library ILS and authentication system, per vendor documentation. |
| What the library configures to turn it on | Knowledge base accuracy, proxy prefix, optional site-wide install; Nomad++ adds branding, domain messaging and chat. | Holdings profile and title list; typically bundled with the LibKey configuration rather than set up separately. | ILS and authentication integration, Librarian Dashboard settings, custom branding and targeted messages, mass deployment. |
| Discovery-layer integration | LibKey Discovery is a separate library-side configuration for Primo, Summon, Leganto, EBSCO EDS, OCLC, SirsiDynix, TDNet and VuFind. | Not a discovery-layer component; BrowZine is its own destination interface. | Vendor site describes discovery-service integration including searchability from Google Scholar; supported platform list not published in the same enumerated form. |
| Off-campus authentication | Rides on your existing stack — EZproxy, OpenAthens, Shibboleth or SeamlessAccess. Does not replace it. | Same authentication stack as the rest of the Third Iron subscription. | Rides on your existing stack too; integrates with the institutional authentication system rather than replacing it. |
| When the article is not licensed | Surfaces open-access copies alongside subscribed content; ILLiad integration documented for the interlibrary-loan handoff. | Shows the title as not held; the article-level fallback is LibKey behaviour, not BrowZine behaviour. | States redirection to over 30M open-access articles and 75k open-access eBooks, integrating Unpaywall, OAPEN and other repositories. |
| Integrations needing no library setup | Documented self-affiliation on Consensus, SciSpace, Litmaps, Covidence, Micromedex, ResearchGate, Academia.edu, AnswerThis.io, and AI assistants including ChatGPT, Claude, Gemini and Copilot. | Not applicable — BrowZine is a library-provisioned destination. | No equivalent published self-affiliation list found in vendor documentation. |
| Scope beyond access | Nomad++ adds export to reference managers, chat and branded messaging. | Alerting and personal bookshelf; no authoring features. | Lean Library Workspace extends into writing, citing and authoring — overlapping reference-manager territory. |
| Failure the researcher actually reports | "The button says we do not have it" — usually stale knowledge base coverage dates, not the extension. | "The journal is missing" — a holdings-profile gap. | "It logged me out at the publisher" — usually a proxy stanza or federation issue upstream of the extension. |
| Pricing | Not published; institutional and negotiated. Consortial agreements exist in several countries. | Not published; typically licensed together with LibKey rather than separately. | Not published; institutional and negotiated. |
Common questions
Common questions about LibKey Nomad (Third Iron) vs BrowZine (Third Iron) vs Lean Library (independent)
Are LibKey Nomad and BrowZine competitors?
+
No. Both are Third Iron products built on the same holdings data. Nomad is the browser layer for getting to a known article; BrowZine is the journal-browsing and alerting layer. Libraries commonly run both, and they are typically licensed together rather than chosen between.
Is Lean Library still owned by SAGE?
+
No. SAGE Publishing acquired Lean Library in September 2018, but announced on 16 December 2025 that it had been sold to a management group and now operates as a standalone business. Comparisons and tender documents describing it as a publisher-owned product are out of date.
What does any of this cost?
+
Neither vendor publishes pricing. Both are institutional, negotiated, and vary by institution type, size and consortium membership, so any figure quoted in a review article is somebody else’s price. Check whether a national or regional consortial agreement already covers you before requesting an individual quote.
Do these replace our OpenURL link resolver?
+
No. They present your holdings more usefully but still depend on the KBART knowledge base and resolver underneath, and they inherit its errors. An article reported as unavailable is far more often a stale coverage date than an extension fault.
Can a researcher get most of this without a library subscription?
+
For the open-access half, largely yes — Unpaywall is free and requires no institutional licence. It is the honest baseline to measure a paid access layer against: install it first and see how much of your access gap it actually closes.
Why does access work on campus but fail at home?
+
Because on campus you are usually IP-authenticated and the extension never has to route you anywhere. Off campus it hands you to EZproxy, OpenAthens, Shibboleth or SeamlessAccess, and any gap there surfaces as an extension failure. Always trial off campus on a personal device.
