Android beta. iOS next.

The authenticator that keeps up with your accounts.

Tag every account. Filter by any combination. Sync your vault across devices with zero-knowledge encryption, so your codes are organized, portable, and ours to store but never to read.

No spam. Just a heads-up when we launch.

You're on the list. We'll be in touch.

How Fob is encrypted ›

What Fob does differently

Three things no authenticator
does well.

Every 2FA app on the market solves the basic problem: generate a 6-digit code every 30 seconds. The hard parts start after that.

01 / TAGS

Multi-tag filtering with AND logic.

Every account can carry as many tags as you want: crypto, exchange, work, high-value. Pick any two and Fob shows only accounts tagged with both. One account, many categories, no folder trap.

02 / IMPORT

One-tap Google Authenticator import.

Scan Google Authenticator's export QR code and the whole batch lands in your vault in one pass. No retyping, no re-enrolling. How the import works.

03 / BACKUP

Zero-knowledge cloud backup.

Your vault is encrypted on your device with AES-256-GCM before it ever touches our servers. The key is derived from your master password via Argon2id and never leaves the device. We hold the ciphertext, you hold the key. Restore it on a new device by signing in.

How it works

Four steps, about five minutes.

STEP 01

Add accounts.

Scan a QR code, import Google Authenticator's export, or paste a setup key. Existing accounts land in your vault without re-enrolling.

STEP 02

Tag them how you think.

Tap an account, add as many tags as you want. work, crypto, high-value. No forced hierarchy.

STEP 03

Filter by any combination.

Toggle tag chips at the top of the vault. Selecting more than one narrows to accounts that carry all of them. Search on top of that.

STEP 04

Lock it. Back it up.

Biometric or PIN lock on the app. End-to-end encrypted cloud backup when you want it. A local .fobvault export any time you want a copy on a drive.

Leaving Authy?

Authy doesn't let you export. We wrote the guide anyway.

A practical, screenshot-heavy walkthrough for moving 40-plus accounts out of Authy. Priority order, the steps that trip people up, and the ones you can safely leave for last. Useful whether or not you end up on Fob.

Read the migration guide

Under the hood

What we actually built.

Fob is a Flutter app with a local Drift vault on Android. Codes are generated on-device per RFC 6238 (TOTP), with account secrets held in Android's hardware-backed Keystore. The app window is tagged with FLAG_SECURE, so screenshots and screen-recording tools can't capture your codes.

Cloud backup is zero-knowledge. Your vault is encrypted on-device with AES-256-GCM using a key derived from your master password via Argon2id (64 MB memory cost, 3 iterations, per-vault salt). The derived key is never transmitted or stored. Our servers see an opaque ciphertext blob, a version counter, and a modification timestamp. Nothing else. You restore it on a new device by signing in with the same master password.

Fob is closed source. The trust story is built on three things instead: a third-party security audit is committed post-launch, and we plan to post the report at fob.codes/security on completion, subject to responsible-disclosure timing; the architecture is designed so the server physically cannot read your codes; and you can export your entire vault at any time in a format any other RFC 6238 authenticator can read.

Questions

Frequently asked.

Is Fob end-to-end encrypted?

Yes. Your vault is encrypted on your device with AES-256-GCM using a key derived from your master password via Argon2id. The derived key never leaves your device, so our servers only ever see opaque ciphertext. We cannot read your codes. Full architecture at /security.

Can I import from Authy?

Authy does not provide a bulk export, so there is no one-click path out. Fob ships a guided manual migration that tracks your progress account by account. The full step-by-step is at /import/authy, and it's useful whether or not you choose Fob.

What happens to my codes if Fob shuts down?

You keep them. Fob can export your vault at any time in a standard format that any other RFC 6238 authenticator can read. TOTP code generation happens entirely on your device, so your codes keep working even with no network and no Fob servers.

Is Fob free?

The core app is free: unlimited accounts, unlimited tags, local vault, biometric and PIN lock, Google Authenticator import, local .fobvault backup. Premium adds encrypted per-account notes, bulk tagging, and end-to-end encrypted cloud backup. See /pricing for the details.

Is there an iOS app?

Not yet. Fob is Android-first in year one. iOS is planned after the Android launch has stabilized. We will announce a dated iOS timeline only once the build is running in TestFlight.

How does tag-based organization work?

Every account can carry multiple tags. You can filter the vault by any combination of tags, and the filter is an AND: picking crypto + exchange shows only accounts that carry both. Folders force you to pick one category per account. Tags don't.

What is zero-knowledge cloud backup?

Your vault is encrypted on your device before it is uploaded for backup. The encryption key is derived from your master password on-device and never transmitted. Our servers store an opaque encrypted blob and nothing else. We cannot decrypt your vault. You restore it on a new device by signing in with the same master password. See /security for the full spec.

Get on the waitlist.

Android beta is running. We'll email when Fob hits Google Play and again when a TestFlight build is ready.

No spam. Just a heads-up when we launch.

You're on the list. We'll be in touch.