Open-Source DevOps · karakeep-app

karakeep

Karakeep is a self-hosted bookmark manager that saves links, notes, and images with AI-powered automatic tagging and full-text search. It includes browser extensions, mobile apps, RSS feed integration, and supports collaborative sharing and content archival.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/karakeep-app/karakeep

27.2k

GitHub stars

1.3k

Forks

TypeScript

Primary language

AGPL-3.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	karakeep-app/karakeep
Owner	karakeep-app
Primary language	TypeScript
License	AGPL-3.0 — OSI-approved
Stars	27.2k
Forks	1.3k
Open issues	659
Latest release	v0.32.0 (2026-05-08)
Last updated	2026-07-06
Source	https://github.com/karakeep-app/karakeep

What karakeep is

Built on Next.js (TypeScript) with Drizzle ORM, NextAuth for auth, tRPC for client-server communication, Meilisearch for full-text search, and Puppeteer for web crawling. Integrates LLM providers (OpenAI, Ollama) for tagging and summarization; supports OCR, video archiving via yt-dlp, and full-page archival via monolith.

Quickstart

Get the karakeep source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/karakeep-app/karakeep.git2cd karakeep3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Self-Hosted Read-It-Later for Organizations

Teams wanting centralized bookmark/content storage without external SaaS dependencies can deploy Karakeep on-premise with collaborative lists, SSO support, and rule-based management for compliance.

Personal Knowledge Management with AI Enrichment

Individual users accumulating links and notes from multiple sources benefit from automatic link preview fetching, AI-driven tagging, and semantic search across archived content.

Content Archival and Link-Rot Protection

Users prioritizing content preservation can leverage built-in full-page archival (monolith), video archiving (yt-dlp), and OCR capabilities to protect against link rot and lost context.

Implementation considerations

Docker deployment recommended; requires database (Drizzle supports PostgreSQL/MySQL), Meilisearch instance, and optional LLM service (OpenAI or local Ollama). See official docs for detailed setup.
LLM integration is optional but core feature; OpenAI calls incur costs; local Ollama models provide alternative but require additional hardware/compute.
Full-page archival (monolith) and video archiving (yt-dlp) add dependencies; evaluate storage requirements for large bookmark collections.
Browser extensions and mobile apps (iOS/Android) depend on backend API stability; test sync behavior before production rollout.
Authentication via NextAuth; supports SSO. Plan identity provider integration (OAuth, SAML) early for enterprise deployments.

When to avoid it — and what to weigh

Closed-Source or Proprietary Requirements — AGPL-3.0 license requires source code sharing if deployed as a service. Organizations unable to comply with copyleft obligations should avoid this project.
Minimal DevOps Capacity — Self-hosting requires infrastructure setup, database management, LLM endpoint configuration, and ongoing maintenance. Not suitable for teams with no DevOps resources.
Multi-Tenancy SaaS Model — AGPL-3.0 license complicates commercial multi-tenant deployment. Requires legal review and potentially custom licensing arrangements (see Karakeep Cloud model).
Production Stability as Hard Requirement — README explicitly states the app is 'under heavy development' with 659 open issues. Not recommended for mission-critical workflows without capacity to manage instability.

License & commercial use

Licensed under AGPL-3.0 (GNU Affero General Public License v3.0), a strong copyleft license. Any modified version deployed as a network service must offer source code to users. Self-hosting is permitted; commercial use or SaaS deployment requires compliance review.

AGPL-3.0 is not a permissive license for commercial use without legal review. Internal deployment by a single organization is typically acceptable; offering Karakeep as a managed service (e.g., SaaS) triggers source-code disclosure obligations. The maintainers operate a commercial managed offering (Karakeep Cloud) under separate terms. Any commercial deployment should undergo legal review to confirm compliance. Requires review before proceeding.

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	High
DEV.co fit	Good
Assessment confidence	High

Security considerations

Self-hosted deployment means security posture depends on operator. NextAuth handles authentication; SSO support available. Project documentation includes a 'Security Considerations' page (link provided in README but content not in supplied data). AGPL-3.0 source availability aids code review. LLM API calls (OpenAI) transmit bookmark data to external services; assess data residency requirements. No mention of encryption at rest or in transit; requires verification. Operators must manage secrets (LLM keys, database credentials, session keys). No third-party security audit data supplied.

Alternatives to consider

Linkwarden

Open-source, self-hostable bookmark manager focused on links with collaborative collections. More mature and lower maintenance overhead, but lacks AI tagging and comprehensive content archival.

Pocket/Mozilla Read-It-Later

Proprietary SaaS; highly polished and zero DevOps burden. No self-hosting, no AI enrichment, but proven stability for read-it-later use case.

Memos

Software development agency

Build on karakeep with DEV.co software developers

Review the AGPL-3.0 license with legal counsel, assess self-hosting and DevOps capacity, test the demo at try.karakeep.app, and plan for ongoing maintenance given the 'heavy development' status.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

linkwarden linkding LinkAce

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source DevOps Web App Development API Development AI Development Talk to DEV.co

karakeep FAQ

Can I use Karakeep commercially or offer it as a service?

Not without legal review. AGPL-3.0 requires you to offer source code to users if deployed as a network service. Internal use is typically fine; SaaS offerings require compliance or custom licensing. Maintainers offer a commercial managed version (Karakeep Cloud).

Do I have to use OpenAI for AI tagging?

No. Karakeep supports local LLM models via Ollama, so you can avoid external API calls. OpenAI integration is optional.

What database does Karakeep support?

Drizzle ORM is used; typically PostgreSQL or MySQL. Exact supported versions and configuration options require review of the docs or code.

Is Karakeep production-ready?

README explicitly states 'under heavy development' with 659 open issues. Suitable for self-hosted personal or team use, but expect API changes, bugs, and feature volatility. Not recommended for mission-critical workflows without active maintenance capacity.

Work with a software development agency

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 karakeep is part of your open-source devops roadmap, our team can implement, customize, migrate, and maintain it.

Ready to evaluate Karakeep for your team?

Review the AGPL-3.0 license with legal counsel, assess self-hosting and DevOps capacity, test the demo at try.karakeep.app, and plan for ongoing maintenance given the 'heavy development' status.

Talk to DEV.co Schedule a Consultation