selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

CookieCloud logo

Self-host CookieCloud

release-v1.0.3

Sync browser cookies and LocalStorage with E2E encryption

ReleaseOpen SourceGPL-3.0
docker run -p=8088:8088 easychen/cookiecloud:latest
Updated2 months ago
LanguageJavaScript
Setup difficultyEasy
Stars
3 200
Port
8088 (CookieCloud sync API server (upload/download of encrypted cookie data))
Docker
easychen/cookiecloud

What is CookieCloud?

CookieCloud is a small client-server tool for moving logged-in browser sessions between machines. An extension in Chrome or Edge uploads cookies — and, in newer releases, the LocalStorage of the same domain — to a server you run yourself, while another browser configured with the same UUID and password pulls them down. Encryption happens in the browser with an AES key derived from the UUID plus password, so the server stores only ciphertext, and the sync interval is configurable. The server itself is a minimal Node HTTP API with a POST /update endpoint and a GET /get/:uuid endpoint; it is published as the multi-architecture easychen/cookiecloud image (linux/amd64, linux/arm64) with state kept in a mounted ./data volume, or started straight from the repo with yarn and node on port 8088. An official test server and several community servers are listed, but the README recommends running your own instance for data security. Notable limits: synchronization is one-way (one browser pushes, others pull), Firefox builds are a compile-it-yourself affair because its cookie format differs from Chromium's, and configuration now lives locally after a breaking format change. The repository also ships decryption reference code for Node, Python, Go and Deno, example Playwright tests, and an agent-skill file that lets coding assistants fetch, decrypt and inject a session.

Should you self-host CookieCloud?

CookieCloud scores 57/100 on selfhost.directory (how scoring works) and ranks #5 of 11 in Browser Automation. It has 3 200 GitHub stars.

It shipped 2 stable releases in the past year. The latest, release-v1.0.3, came out on 3 May 2026.

Setup is easy: most people get it running in one sitting. An official Docker image is available. It is GPL-3.0-licensed and written mostly in JavaScript.

Its closest alternative on selfhost.directory is Lightpanda (79/100, 37 085 stars). It scores higher overall, so compare the two before you pick. See CookieCloud vs Lightpanda side by side.

Features

  • AI agent skill
  • Browser Extension
  • Configurable sync interval
  • Cookie syncSynchronization is one-way: one browser uploads, another downloads.
  • Decryption examples in several languages
  • End-to-end encryption
  • Fixed-IV encryption format
  • LocalStorage sync
  • REST API
  • Sub-path deployment

CookieCloud README

How to install CookieCloud

Install CookieCloud with Docker

Environment variables
API_ROOT
docker run -p=8088:8088 easychen/cookiecloud:latest

Optional: docker run -e API_ROOT=/cookie -p=8088:8088 easychen/cookiecloud:latest to serve under a subdirectory.

How to configure CookieCloud

  • API_ROOTServe the API under a URL subdirectory; the value must start with a slash

    Serve the API under a URL subdirectory; the value must start with a slash

    values: any path starting with /, e.g. /cookie

  • COOKIE_CLOUD_HOSTURL of the CookieCloud server used by client/example scripts (environment variable on the consuming side)

    URL of the CookieCloud server used by client/example scripts (environment variable on the consuming side)

    values: e.g. http://127.0.0.1:8088

  • COOKIE_CLOUD_PASSWORDPassword combined with the UUID to derive the local AES decryption key

    Password combined with the UUID to derive the local AES decryption key

  • COOKIE_CLOUD_UUIDUUID generated by the browser extension, identifies the stored cookie bundle

    UUID generated by the browser extension, identifies the stored cookie bundle

CookieCloud releases & version history

FAQ

Which browsers does the extension support?

Chrome and Edge are officially supported, other Chromium-based browsers may work but are untested, and Firefox has to be compiled from source with an incompatible cookie format.

Is the synchronization bidirectional?

No, it is one-way at the moment: one browser acts as the uploader and another as the downloader.

More in Browser Automation

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…