SelfHostAuth
github.com
- Free plan
- Windows
- macOS
- Linux
- Web
- iPhone and iPad
- Android
- Browser extension
- API
- Self-hosted
8.2 Club score Visit github.com
Plans
Every plan and priceSelfHostAuth
Free
Free plan
What the maker publishes
- Audience
- The README identifies homelabbers, privacy advocates, teams needing a self-hosted OTP server, and people seeking alternatives to Google Authenticator or Authy as its intended users. source
- Availability limit
- The project says there is no hosted version and it is self-hosted only by design. source
- Clients
- The project lists a web vault, Windows/macOS/Linux Electron desktop apps, iOS and Android apps, and Chrome/Edge/Firefox browser extensions. source
- Code standards
- It supports RFC 4226 and RFC 6238, SHA-1, SHA-256, and SHA-512, 6–8 digits, and configurable periods. source
- Code type
- totp and hotp source
- Deployment
- The server uses Node.js 22+ and SQLite and can run with Docker Compose, systemd, or bare metal on a home server, NAS, Raspberry Pi, or VPS. source
- Free plan
- Yes source
- Imports
- Users can add accounts by scanning or pasting a QR code, an otpauth:// URI, or a raw base32 secret. source
- Integrations
- It accepts otpauth:// imports and provides a typed TypeScript API client for its sync server. source
- License
- The repository is licensed under MIT. source
- Multi-device sync
- Yes source
- Offline use
- Clients cache the vault locally and compute TOTP codes without connecting to the server. source
- Purpose
- SelfHostAuth is an open-source, self-hosted TOTP/HOTP authenticator and sync server. source
- Push approvals
- No source
- Security
- The server encrypts vault items at rest with AES-256-GCM, hashes passwords with scrypt and session tokens with SHA-256, and supports optional account TOTP authentication. source
- Security disclosures
- The vulnerability report last checked on 2026-09-28 lists one high and one medium finding, including a pnpm audit summary of 24 vulnerabilities. source
- Supported platforms
- web,windows,macos,linux,ios,android,chrome_extension source
- Support policy
- The security policy says maintainers aim to acknowledge vulnerability reports within three business days and ship a fix or mitigation within 30 days for high-severity issues. source
- Sync
- Revision-based push/pull sync uses last-write-wins and tombstones so deleting a code on one device deletes it across devices. source
- Transport
- The project says to use TLS through a reverse proxy; HTTPS is required for mobile apps and browser extensions when connecting outside localhost. source
Checked against the maker's pages on 9 Oct 2026.