ClipCascade — Self-Hosted, Open-Source

Features

• 🚀 Instant Clipboard Sync – Clipboard content updates in real time across all connected devices. Just copy, and it’s there!
• 🔒 Secure Authentication – Ensures only authorized users can sync clipboard data.
• 🛡️ End-to-End Encryption – Protects clipboard content with advanced cryptographic security and hashing techniques.
• 🔄 Dual Sync Modes:
• ☁️ Server-Based Sync – Reliable cloud-based synchronization via a centralized server.
• 🔗 Peer-to-Peer Sync – Direct device-to-device connection for ultra-low latency and minimal server dependency.
• 💻 Cross-Platform Compatibility – Works seamlessly on Windows, macOS, Linux, and Android.
• 📄📷📁 Universal Clipboard – Syncs text, images, and files effortlessly across devices.
• 📦 Self-Hosting Option – Deploy your own secure instance using a Docker image or standalone JAR file.
• 👥 Multi-User Support – Isolates clipboard data per user while enabling seamless syncing between personal devices.

Installation

4. **Access the Server** Once the server is running, you can access it via: ``` http://localhost:8080 ``` - **Default Credentials:** - **Username:** `admin` - **Password:** `admin123` > **Important:** It is strongly recommended to change the default credentials immediately after the initial login. For guidance on setting up a **reverse proxy**, refer to the [Reverse Proxy Setup](https://github.com/Sathvik-Rao/ClipCascade?tab=readme-ov-file#-reverse-proxy-setup) section. [➡️ Explore Advanced Details](https://github.com/Sathvik-Rao/ClipCascade?tab=readme-ov-file#%EF%B8%8F-advanced-details) * * * * * * * ### 🐳 Self-Hosting ClipCascade Using Docker: #### Quick Installation (Single Command) For users who prefer a one-liner, you can deploy ClipCascade instantly using: ```yaml docker run -d --name clipcascade -p 8080:8080 -e CC_MAX_MESSAGE_SIZE_IN_MiB=1 -v ./cc_users:/database sathvikrao/clipcascade ``` #### Detailed Installation Steps To host ClipCascade on your server using Docker, follow these steps: 1. Create a `docker-compose.yml` File Create a `docker-compose.yml` file with the following content, or download it from the [release page](https://github.com/Sathvik-Rao/ClipCascade/releases): ```yaml services: clipcascade: image: sathvikrao/clipcascade:latest ports: - "8080:8080" # Expose the ClipCascade server on port 8080 restart: always # Automatically restart the container if it stops volumes: - ./cc_users:/database # Persistent storage for user data environment: - CC_MAX_MESSAGE_SIZE_IN_MiB=1 # Maximum message size in MiB (ignored if P2P mode is enabled) - CC_P2P_ENABLED=false # Enables or disables peer-to-peer(P2P) mode # - CC_ALLOWED_ORIGINS=https://clipcascade.example.com # Defines allowed CORS origins for security # - CC_SIGNUP_ENABLED=false # Enables or disables user self-registration

Why self-host ClipCascade

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

What hardware do you need

Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through ClipCascade. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.

Where to go from here

• Browse the full self-hosted app directory
• Compare self-hosted alternatives side-by-side
• DevOps roadmap — learn the skills to run your own server