Self-host 2FAuth for private TOTP tokens.
2FAuth is a self-hosted web authenticator for TOTP/2FA tokens. VibeNest launches a prepared adapter with generated secrets, persistent storage and free SSL on your own subdomain.
Private token vault
Keep 2FA seeds in an isolated instance instead of a shared demo or browser-only scratch setup.
VibeNest-ready adapter
The adapter uses the official 2FAuth image, port 8000, generated APP_KEY, SQLite defaults and persistent storage.
Security-sensitive
Treat this as recovery-critical infrastructure. Keep backups and protect the admin account before storing important tokens.
Deploy 2FAuth in one click
- 1. Launch the adapter VibeNest opens the deploy flow with the 2FAuth adapter repo and branch pre-filled.
- 2. Confirm hardware Use a free or paid server slot so the token manager has RAM, CPU and persistent storage.
- 3. Finish setup Open the public URL, create the first account and configure backups before adding recovery-critical tokens.
A private web authenticator for TOTP accounts
2FAuth stores time-based one-time password entries in a browser-accessible vault. It can centralise tokens that would otherwise be spread across phones and authenticator apps, while keeping the service on an instance you administer.
This convenience also raises the cost of a mistake: possession of the vault may unlock second factors for many other accounts. The VibeNest recipe generates the Laravel application key, keeps SQLite data on a persistent volume and terminates HTTPS at the platform route.
Recovery comes before convenience
Create the owner account immediately, close unused registration paths and keep independent recovery codes for every critical service. Back up and test restoration of the persistent volume before moving tokens out of another authenticator. A running container alone is not a recovery plan.
Source, VibeNest recipe and live proof
Original open-source project
Review the upstream source, release notes and AGPL-3.0 license before you deploy or update the app.
Original GitHubVibeNest-ready recipe
Adapter uses the official 2FAuth image on port 8000, generated APP_KEY, SQLite defaults and persistent /2fauth storage. A stale smoke project build-pack was corrected from nixpacks to docker-compose before validation.
Deploy repositoryPublic deployment proof
Public URL returned HTTP 200 with 2fauth_session cookie, nginx/PHP headers and no VibeNest fallback.
Open live deploymentFrequently asked questions
Is 2FAuth open source? +
Yes. 2FAuth is open-source software. VibeNest launches it through a small adapter that keeps upstream intact and adds deploy-safe defaults.
Why should I run my own 2FAuth instance? +
2FA seeds are sensitive personal state. Your own instance isolates the account, storage and generated app key under your VibeNest project.
Does 2FAuth fit the free tier? +
The adapter passed a VibeNest free-tier smoke deploy with 256 MB RAM and 0.5 vCPU. Heavy usage may need a paid hardware slot.
Does it need persistent storage? +
Yes. The adapter stores 2FAuth data on a persistent volume so accounts and tokens survive redeploys.
What should I do after deploy? +
Create the first account, confirm the public URL works, then set up backups before storing recovery-critical tokens.
Deploy your private 2FA manager
Start with a tested 2FAuth adapter, then keep secrets, storage and SSL under your own VibeNest project.
Deploy 2FAuth