No server. No telemetry. Open source.

Sync your browser to storage you own.

Konode keeps bookmarks, open tabs, history and your extension list in step across every Chromium browser, stored in your Google Drive, GitHub, or WebDAV. Nothing ever touches a Konode server, because there isn't one.

Add to Chrome — it's free How to set it up

MacBook · this device Synced 42s ago · 3 streams active E2EE

Bookmarks312 items

Open tabs18 tabs · 2 windows

Historyde-duplicated

AES-256-GCM PBKDF2 · 600k rounds MV3 extension MPL-2.0 licensed Chromium + Firefox SHA-256 integrity

What syncs

Four data streams, in step across every browser.

Bookmarks

Two-way sync that preserves your folder structure. Deletions propagate too, so no old bookmarks quietly come back.

Open tabs

Save the current tab set and restore another device's session whenever you want.

History

A synced, de-duplicated history list, with the original visit time preserved where the browser allows it. Chromium does not, Firefox does.

Extensions

Sync the list and see at a glance which extensions are missing on the device you're on. Read-only: Konode never installs anything.

When two devices disagree, you choose how it's resolved: newest wins, always prefer this device, always prefer the other, or resolve it yourself from the popup.

Your storage

Bring the backend. Konode does the rest.

One-time sign-in

Google Drive

Scoped to drive.file, so Konode only ever touches the files it creates.

Fine-grained token

GitHub

Point it at a single private repository. Every sync leaves a version history you can read.

Username + password

WebDAV

Nextcloud, ownCloud, Synology, pCloud, kDrive, or any other WebDAV server.

Planned · Mega. Not available yet.

Privacy & security

The threat model, out in the open.

No Konode servers exist.

Your data goes only to the backend you configure. Nothing is ever sent to us or to any third party, because there is nothing in the middle.

Optional end-to-end encryption.

AES-256-GCM with a 600,000-round PBKDF2-SHA256 derivation. An explicit choice during setup. Off by default, and never silently enabled.

Credentials stay local.

OAuth tokens, GitHub tokens, WebDAV passwords and your passphrase live only in chrome.storage.local on your device.

Least privilege.

History, tabs and management permissions are requested only when you turn those data types on. Extension-list access is read-only.

Full detail in the privacy policy.

How it works

One JSON file per device, per data type.

/Konode/macbook-bookmarks.json

{
  "device":   "macbook",
  "type":     "bookmarks",
  "updated":  "2026-07-27T09:41:00Z",
  "checksum": "sha256:a3f9…c2b7",
  "e2ee":     true,
  "payload":  "<AES-256-GCM ciphertext>"
}

Illustrative shape; the repository has the exact schema. Every sync pulls each peer's file, merges non-destructively, then pushes back. Bookmarks use tombstones so deletions travel between devices without resurrecting old entries.

Alternatives

How it compares.

Konode compared with Floccus, Raindrop.io, xBrowserSync, and built-in browser sync
	Konode	Floccus	Raindrop.io	xBrowserSync	Built-in sync
What syncs	Bookmarks, tabs, history, extension list	Bookmarks	Bookmarks	Bookmarks	Bookmarks, tabs, history, passwords
Where it writes	Your Drive, GitHub, or WebDAV	Your Drive, Nextcloud, WebDAV, Dropbox, Git	Raindrop's servers	Their server, or self-hosted	Google's or Mozilla's servers
Account needed	No	No	Yes	No, anonymous ID	Yes
End-to-end encryption	Optional, on every backend	Optional, WebDAV and Drive	No	Yes, client-side	Firefox yes, Chrome optional
Open source	Yes, MPL-2.0	Yes	Apps only	Yes	Partially

Compared in July 2026 from each project's own documentation. Check the source projects for current details.

Your browser, everywhere. On storage you own.

Free, open source, no account. Install once, connect your storage, you're done.

Add to Chrome Source on GitHub