Linkwarden Hosting
Collect, organize, preserve, and collaboratively manage bookmarks and archived webpages.
- One click deploy
- 2 GB RAM Memory needed
- 25 GB Disk Space Needed
- From 5 € Price
Official links
Linkwarden’s official links and original website
Linkwarden Website
More
Tech
- Docker image
- ghcr.io/linkwarden/linkwarden:latest
- Default port
- 3000
- Database
- postgres
How Linkwarden works
Linkwarden stores a URL together with a title, description, tags, collection membership, and an archived representation of the page. Users can add links through the browser interface, organise them into personal or shared collections, and return through search rather than relying on a flat browser bookmark list.
Preservation is central to the workflow. The server captures a durable copy so a reference can remain useful after the source changes or disappears. Annotations and descriptions add personal context, while collection permissions determine which team members can view or maintain a shared research set.
Key Linkwarden features
Collections and tags provide two complementary ways to structure saved material. Search indexes bookmark metadata and archived content, helping users find a source from remembered words rather than its original address. Import tools provide a route from browser bookmarks or other supported formats.
Collaborative collections allow several people to build a reference library together. Each link can carry notes or annotations, and preserved copies reduce dependence on the continued availability of the original page. The catalogue stack includes Meilisearch to support fast retrieval across the archive.
Linkwarden vs Raindrop.io
Linkwarden is a self-hosted bookmark manager and webpage-preservation service built around collections, tags, search, annotations, and shared libraries. Raindrop.io is a provider-hosted bookmark platform with managed synchronisation, browser extensions, official applications, collections, tags, highlights, and cloud backup.
Raindrop.io may suit users who want a mature hosted account, native applications, and infrastructure operated by the vendor. Linkwarden is more attractive when controlling the server, keeping preserved pages within the chosen hosting environment, and managing a team archive directly are higher priorities.
Who uses Linkwarden
Researchers collect source material and preserve citations in Linkwarden, while product and engineering teams build shared references for tools, competitors, standards, and documentation. Individuals use it to replace browser folders with a searchable long-term reading and research archive.
The application is not a crawler for unrestricted bulk archiving. Page capture can fail on sites that require authentication, block automation, or depend heavily on unsupported browser behaviour, so important preserved material should be checked after it is saved.
Self-hosting Linkwarden: requirements and cost
Resource use grows with saved-link volume, page-preservation jobs, archived content, search indexing, imports, and active collaborators. PostgreSQL stores accounts, links, collections, permissions, and metadata, while Meilisearch handles indexing. PostgreSQL is included in the AvaHost stack but remains unmanaged. Application email delivery is disabled, so invitation or notification mail is not part of the hosted service.
Linkwarden has no separate software charge for the hosted application, and the database-adjusted recommendation is Plan 3 at €10. Linkwarden hosting provides one-click setup, an archive domain, automated HTTPS, automatic application updates, and scheduled backups. Because preserved pages consume storage over time, archive growth should be reviewed even though this app is not flagged for the catalogue storage step-up.
F.A.Q
Linkwarden starts at €10 on Plan 3 after allowing for PostgreSQL and the search service in its catalogue stack. The Linkwarden package includes one-click setup, a custom domain, automated HTTPS, application updates, and scheduled backups. Saved-page volume, preservation jobs, imports, search indexing, and team activity influence future resource needs.
The deployment provisions PostgreSQL for accounts, links, collections, permissions, and metadata, plus Meilisearch for indexing. Linkwarden is connected to both services automatically. PostgreSQL is included but unmanaged, so database records, search state, and persistent archived files should be considered together when planning maintenance, exports, or recovery.
A custom domain can be connected to Linkwarden, with automated HTTPS applied after DNS points to the hosted installation. Choose the final address before distributing shared collection links or configuring browser integrations. After the switch, verify sign-in, page capture, search, imported bookmarks, and any saved references to the earlier hostname.
Page preservation depends on what the source website permits and how it renders content. Sites behind authentication, anti-automation controls, paywalls, or unusual client-side behaviour may not produce a complete archive. Check important captures after saving them, retain original files when available, and avoid treating one archived representation as the only legal or evidentiary copy.