Octi Keeps Your Android Devices in Sync (Without Google, Without Root)

Last updated: September 13, 2026 · 6-minute read

599 stars is absurdly low for what Octi does. The app watches battery levels, Wi-Fi SSIDs, clipboard contents and installed-app changes across every Android device you own, and pushes those states between phones in near real time — through Google Drive if you want zero setup, or through your own end-to-end encrypted server if you never want to see Google's name in the sync path. It is GPL-3.0, it ships on Play Store, GitHub and IzzyOnDroid at the same time, and almost nobody is talking about it.

This is Buried Treasure №5 — the series where I dig up open-source projects that deserve more attention than their star counts suggest. Every claim below comes from the repo itself, verified on September 6, 2026.

Who built it, and why that matters

Octi comes from the d4rken-org GitHub organization — the developer behind SD Maid, one of the longest-lived storage-cleaning apps on Android. The pedigree shows in unglamorous places: reproducible-builds badges, a public Discord, Crowdin localization, and a changelog that moves in small, honest increments. The latest release is v1.3.0-rc0, published September 4, 2026, and the repo has been pushed to within days of this writing. Five contributors keep the Kotlin codebase moving.

That track record is the main reason this project survives the thing that kills most multi-device utilities: the long, boring middle years of maintenance.

What Octi actually syncs

The module list is deliberately small and deliberately useful:

• Battery — charge level, charging speed, and time estimates from each device, visible on all the others.
• Connectivity — current Wi-Fi SSID and IP address per device. Finding the phone that drifted onto a congested band stops being a guessing game.
• Installed apps — app list and the last app installed, so you can stop re-deriving "which phone did I install that on".
• Clipboard — copy text into Octi on one device, pull it out on another.

That is the whole feature list at the core, and the restraint is the point. Octi is not trying to mirror notifications, stream your screen, or turn your phone into a keyboard for your laptop. It answers one question continuously: what is the state of my other devices right now?

The sync options are where it gets interesting

Two transports exist, and choosing between them is really a privacy decision.

Google Drive is the path of least resistance. If all your devices share one Google account, sync works with no server and no configuration. Your data transits Google's infrastructure, encrypted by Octi but resident there.

Octi Server is the self-hosted path — a separate companion project that stores sync data on hardware you control, with end-to-end encryption so the server only ever sees ciphertext. No Google account involved at all. If you already run a VPS for your own services, this slots into the same mental model.

Two companion clients connect to that self-hosted server: Octi Desktop, a Compose Multiplatform app for Linux, macOS and Windows, and Octi Web, a browser client — which means your phone states are visible from any machine that can reach your server. The protocol itself is documented in the repo's docs/protocol/ directory: linking, HTTP API, change notifications, and the encryption scheme. A third-party Home Assistant integration already exists, community-built, exposing device states as entities installable through HACS.

Self-hosting the server converts Octi from "handy utility" into "private device-state mesh that happens to fit in a Docker container".

Where it falls short

Honesty first: Octi is not a KDE Connect replacement, and comparing them misses the point. KDE Connect owns the LAN — remote input, notification mirroring, file push over local network. Octi owns ambient state — battery, connectivity, clipboard — across devices that may be in different cities, over cloud or your own server. If you want to control your phone from your PC, use KDE Connect. If you want your tablet to know your phone is at 14 percent before you leave the house, that is the job Octi does.

The caveats stack up like this. The GitHub release line currently sits at a release candidate — v1.3.0-rc0 — so expect occasional rough edges on the newest features. The clipboard module works copy-into-Octi rather than silently capturing everything, which is the privacy-correct design but a small extra step. And the project's scope is Android-first; the desktop and web clients are explicitly early-stage, so treat them as promising rather than polished. One method note: I have not run a multi-device Octi sync myself — this piece comes from reading the org's repos end to end, the wiki, and the release history.

Try it in five minutes

The fastest path needs two Android devices and nothing else:

1. Install Octi on both phones — Play Store, GitHub Releases, or the IzzyOnDroid F-Droid repo all carry it. 2. Pick the same sync method on both. For the no-Google route, point both clients at your Octi Server instance during setup. 3. Grant the modules you want on each device — battery and connectivity need nothing special; clipboard is opt-in by design. 4. Watch one phone's battery percentage appear on the other. That moment is the entire pitch, compressed.

For the self-hosted route, the server repo has Docker instructions, and the wire protocol docs are there if you would rather build your own client than trust anyone's binary. That openness — a documented protocol, GPL-3.0 code, reproducible builds — is rare in Android utilities and worth rewarding.

TL;DR

• Octi is a GPL-3.0 multi-device manager for Android from the SD Maid developer — 599 stars, actively maintained, v1.3.0-rc0 released September 4, 2026.
• It syncs battery state, Wi-Fi/IP, installed-app lists and clipboard between devices — ambient state, not remote control.
• Sync runs over Google Drive for zero setup, or a self-hosted end-to-end encrypted Octi Server with desktop and web companion clients.
• It complements rather than replaces KDE Connect; clipboard capture is deliberate opt-in, and desktop clients are early-stage.
• Fastest try: install on two phones, pick a sync transport, grant modules — done in five minutes.

If your device fleet is two phones and a tablet, the ambient-state picture Octi draws gets useful fast — and it pairs naturally with the privacy-first tooling this site keeps circling back to. Gander, next in the Buried Treasure series, applies the same self-verifying transparency idea to file viewing.

---

Not affiliated with d4rken-org, Google, or the KDE Connect project. Sources: the Octi GitHub repository, its server and desktop companion repos, and the GitHub API data pulled September 6, 2026.