Skip to main content

Roadmap

What is planned for Linkdean, in rough order. Everything already shipped is on the features page, and each release is in the changelog.

Plans move as the beta teaches us what matters. Want something sooner, or something that is not here? Say so in GitHub Discussions.

Now: running the public beta well​

  • Browser extension in both stores. Live on the Chrome Web Store; the Firefox add-on is in review. Edge installs from the Chrome listing.

Next: once the beta settles​

Archiving and AI assistance come first. They are the biggest gaps on the comparison page.

  • Archive and downloads. Keep a copy of every page you bookmark, so a link that dies is not lost.
    • A single-file HTML copy and a PDF of each page, taken when you save it. Opt-in, and counted against your storage.
    • Search inside the pages themselves, not only titles, notes and tags.
    • Download any copy as HTML, PDF or reader-mode Markdown, or include all of them in your export.
    • When a link breaks, open its saved copy instead.
    • Copies of vault bookmarks are encrypted with the vault and kept out of search.
  • AI assistance, on your terms. Off by default, and you choose who runs it: your own API key, or a local model on your own server. The hosted service will include a small free allowance.
    • Tag and folder suggestions as you save and file.
    • A short summary of each bookmark.
    • Search by meaning ("that article about…"), not only by the words in it.
    • Hints for related and near-duplicate bookmarks.
    • Later, dashboard sections suggested from what you save and open.
    • Suggestions wait for your click. Vault contents are never sent to a model.
  • More for AI agents. Folders and tags already work as Agent Skills (experimental, off by default). Next: a read-only MCP server, and archived page text inside skills.
  • Legal review. A lawyer reviews the Terms and Privacy Policy before anything costs money.
  • Plans and pricing for the managed service. Deciding what stays free, what a paid plan would add, and the limits of each. Self-hosting stays free for non-commercial use.
  • Privacy-respecting usage statistics. Aggregate counts only (active users, bookmarks saved, features used), nothing per person and no page content or addresses. Off by default when you self-host.

Later​

  • Organizations and teams. Shared team spaces with roles, restricted folders, invites and an audit log, while personal libraries stay private. Then invite links, verified domains, SAML and SCIM single sign-on, and team vaults.
  • Other languages. The interface translated, starting with making every string translatable.

Far out​

Ideas we want to get to, without a date.

  • End-to-end encrypted vaults, where the server never sees the key.
  • Native mobile apps for iOS and Android, beyond the installable web app.
  • A desktop app for macOS, Windows and Linux.
  • Previews for sites behind bot protection, which block the screenshot today.
  • Moving off the home server to a VPS, then to multi-server cloud hosting, as the service grows.
  • A welcome email, badges for likes and ratings, a FAQ on this site, and a few easter eggs.