Clockode is an offline Linux TOTP authenticator in Rust that replaces Authy with local KeePass encryption and standard Aegis backup compatibility.
Spanish software developer Alex Marín created Clockode to provide a native Linux desktop authenticator that generates two-factor authentication codes without cloud dependencies. Built in Rust with the Iced framework, the tool stores credentials in a local KeePass vault instead of locking secrets behind proprietary accounts. That architecture keeps token generation offline, private, and under direct developer control.
Authy pairs two-factor authentication with Twilio cloud servers, requiring phone-number verification and routing token sync through closed APIs. Following Twilio deprecation of its desktop client, Linux workstation users lost native support entirely. Authy also isolates credentials inside a proprietary format, preventing developers from exporting tokens into local scripts or standard backup archives.
Clockode focuses on open platform integrations. It encrypts secrets inside standard KeePass KDBX4 databases using keepass-rs, allowing DevOps engineers to inspect or back up credentials with KeePassXC and existing infrastructure tools. Desktop integration extends to camera access: Clockode connects through ashpd and PipeWire to scan QR codes without direct /dev/video access. It lacks Authy managed multi-device cloud server, but an internal filesystem watcher automatically reloads entries whenever utilities like Syncthing update the database file.
arboard library targets wlroots data protocols that GNOME Mutter omits for security, breaking clipboard copying in pure Wayland Flatpak sessions (GitHub issue #22).Why choose Clockode instead of Authy for developer workstations? Clockode runs offline on Linux using open KeePass storage, whereas Authy abandoned desktop support and tethers credentials to Twilio cloud servers.
Can Clockode synchronize two-factor authentication tokens across devices? Clockode contains no built-in sync server, but its KDBX4 database syncs across machines with Syncthing and imports standard Aegis mobile backups.
Does Clockode require network access to generate codes? No. Clockode computes time-based one-time passwords using local system clocks, and its Flatpak package requests no network permissions.
Clockode is an effective choice for Linux developers who want an offline desktop authenticator integrated with KeePass and Syncthing workflows, but it is not intended for teams requiring hosted multi-device push approvals. Active updates through August 2026 and a copyleft GPL-3.0 codebase ensure that sensitive authentication tokens remain verifiable, portable, and free from vendor lock-in.
Commands from the official package registries. Each package is matched to Clockode through the registry's own link to its source code or website.
flatpak install flathub dev.mariinkys.ClockodeFree IDE for Java, Kotlin, Go, TypeScript and Python. Built on IntelliJ Community, fully open source, 300+ plugins.
Show that Clockode is listed as an open-source alternative. Paste into your README: