linkwarden
Linkwarden is a self-hosted, open-source bookmark manager written in TypeScript that lets teams collect, organize, and annotate web content while preserving copies as screenshots and PDFs. It combines read-it-later functionality with collaboration features, offering browser extensions, mobile apps, and full-text search.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | linkwarden/linkwarden |
| Owner | linkwarden |
| Primary language | TypeScript |
| License | AGPL-3.0 — OSI-approved |
| Stars | 18.9k |
| Forks | 796 |
| Open issues | 634 |
| Latest release | v2.14.1 (2026-04-22) |
| Last updated | 2026-07-07 |
| Source | https://github.com/linkwarden/linkwarden |
What linkwarden is
Built with Next.js and React, Linkwarden provides a full-stack TypeScript application with API keys, SSO integration, and automated content preservation (screenshot/PDF/HTML capture). It supports collaborative workspaces with granular permission controls and includes optional local AI tagging.
Get the linkwarden source
Clone the repository and explore it locally.
git clone https://github.com/linkwarden/linkwarden.gitcd linkwarden# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Deployment requires TypeScript/Node.js stack and database (likely PostgreSQL based on typical Next.js setups); infrastructure costs and DevOps overhead are your responsibility.
- AGPL-3.0 license means any modifications or hosted instances must make source code available to users—validate internal security and compliance policies before deploying.
- Content preservation (PDF/screenshot capture) may require additional system dependencies (headless browser, ImageMagick) and storage allocation for large link collections.
- Optional AI tagging feature specifics (model, compute requirements, offline vs. cloud inference) are not detailed; evaluate separately against your infrastructure.
- Mobile app distribution requires separate iOS/Android app deployments and App Store/Play Store account management alongside server infrastructure.
When to avoid it — and what to weigh
- Proprietary SaaS-only Requirements — If your organization requires guaranteed commercial support, SLAs, or liability contracts—Linkwarden is AGPL-3.0, and self-hosting carries operational responsibility.
- Closed-source Compliance — AGPL-3.0 requires derived works and network services to disclose source. If you integrate it into a proprietary service without open-sourcing modifications, you may face compliance issues.
- Minimal Maintenance Tolerance — Self-hosted deployments require managing infrastructure, database updates, and security patches. Not suitable if your team cannot dedicate resources to operational upkeep.
- Enterprise SSO/Authentication at Scale — While SSO is listed for enterprise users, detailed authentication architecture and multi-tenant support are not clarified in available data; review thoroughly for large-scale deployments.
License & commercial use
Linkwarden uses AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license requiring that any derivative work or networked service must make source code available to users. Commercial use is technically possible but triggers source disclosure obligations if modifications are made or the software is deployed as a service.
AGPL-3.0 permits commercial use, but with significant obligations: if you modify the code or host it as a service, you must disclose the modified/running source code to users. Using unmodified Linkwarden for internal bookmark management is lower-risk, but integrating it into a commercial product or SaaS requires legal review. A commercial cloud offering exists (linkwarden.app), which is the safest path for businesses unwilling to navigate AGPL compliance.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
AGPL-3.0 license mandates security disclosure via email ([email protected]) rather than public issues. Self-hosted instances inherit responsibility for: database encryption, TLS/SSL configuration, authentication strength (API keys, SSO setup), and access control. Content preservation (storing user URLs as PDFs/screenshots) creates privacy considerations—validate storage security and data residency comply with regulatory requirements. No mention of penetration testing, security audit results, or vulnerability disclosure history in provided data.
Alternatives to consider
Raindrop.io
Commercial SaaS alternative with superior mobile UX, cloud backup, and zero self-hosting overhead. Lacks offline-first link preservation and open-source transparency.
Wallabag
Similar self-hosted FOSS read-it-later tool (MIT license), simpler to deploy, but lacks native collaboration and AI tagging; smaller community.
Notion / Obsidian
General-purpose knowledge management tools with better integration ecosystems and flexibility; require more manual organization and lack automated web content capture.
Build on linkwarden with DEV.co software developers
Start with the demo (demo.linkwarden.app), review the AGPL-3.0 license implications with your legal team, and try cloud hosting (linkwarden.app) or self-hosting (docs.linkwarden.app) to match your deployment model.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
linkwarden FAQ
Can I use Linkwarden commercially?
What infrastructure do I need to self-host?
Is there enterprise support or an SLA?
How does the mobile app work?
Custom software development services
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If linkwarden is part of your open-source devops roadmap, our team can implement, customize, migrate, and maintain it.
Ready to evaluate Linkwarden for your team?
Start with the demo (demo.linkwarden.app), review the AGPL-3.0 license implications with your legal team, and try cloud hosting (linkwarden.app) or self-hosting (docs.linkwarden.app) to match your deployment model.