OpenViSTAI · Agents · Blockchain · Crypto
Menu
Security & Custody

NodeAuth

NodeAuth is an open-source web-based application for storing and generating 2FA/TOTP credentials, with encrypted storage, Cloudflare Workers or Docker deployment, PWA installation, offline code generation, configuration checks, and automated backups to Email, WebDAV, Amazon S3, or Telegram.

Independent OpenViST project profile, based on linked sources.

NodeAuth — OpenViST project profile in Security & Custody.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use NodeAuth when you want to manage TOTP credentials through a deployable web application and need a choice between serverless hosting and self-hosted Docker operation. Its PWA and backup features are relevant when offline code generation or recovery copies are part of the workflow.

Who it is for

  • People managing multiple 2FA/TOTP credentials.
  • Digital-asset users seeking a dedicated authentication-code manager.
  • Operators who want Cloudflare Workers or Docker deployment choices.
  • Users who need an offline-capable PWA and configurable backup destinations.

Documented uses

  • Store 2FA/TOTP credentials in a dedicated application.
  • Generate authentication codes from saved credentials.
  • Run the service through Cloudflare Workers or on self-managed Docker infrastructure.
  • Access code generation through an installed desktop or mobile PWA while offline.
  • Create automated backups through Email, WebDAV, S3 storage, or a Telegram bot.
Before you choose

Requirements & limits

The public repository identifies NodeAuth as open-source software under the AGPL-3.0 license. The supplied material documents Cloudflare Workers, Docker, web, PWA, desktop, mobile, and self-hosted deployment contexts, but does not establish account requirements, pricing, or service availability.

  • Choose between Cloudflare Workers and Docker based on whether you want serverless deployment or infrastructure under your control.
  • Consider PWA installation if offline TOTP generation is important to your workflow.
  • Review the required security-key configuration because the application can block access when key settings are missing or unsafe.
  • Select backup destinations that fit your recovery model: Email, WebDAV, S3, or Telegram.
  • AGPL-3.0 licensing matters if you modify and publicly provide the software as a service.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Deploy NodeAuth with Docker

Set up NodeAuth as a self-hosted 2FA/TOTP management service.

Before you start

  • Docker-capable infrastructure.
  • The NodeAuth repository and its deployment documentation.

Steps

  1. Review the deployment documentation at the NodeAuth wiki.

  2. Use the repository’s documented Docker deployment method.

  3. Configure the service’s required security keys and settings.

  4. Apply the documented health checks before using the service to manage credentials.

Expected outcome

A Docker-based NodeAuth installation for storing and generating 2FA/TOTP codes.

Guide limitations

  • The supplied material does not provide the exact Docker command, environment variables, storage configuration, or verification procedure.
  • This recipe describes documented setup stages and is not a deployment test or security audit.
Source-based practical guide

Install NodeAuth as an offline-capable PWA

Use NodeAuth through an app-like desktop or mobile interface with offline TOTP generation.

Before you start

  • A deployed NodeAuth instance.
  • A supported desktop or mobile browser capable of PWA installation.

Steps

  1. Open the deployed NodeAuth web application.

  2. Install it to the desktop or mobile home screen using the browser’s PWA installation flow.

  3. Use the installed application to access stored credentials and generate TOTP codes while offline, as described by the project.

Expected outcome

An app-like NodeAuth interface that the project describes as capable of offline code generation.

Guide limitations

  • The supplied material does not specify browser versions, synchronization behavior, or recovery steps after device loss.
  • Offline availability depends on the application having been installed and its relevant data being cached.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
3 October 2026
Original website title
nodeauth/nodeauth-byos · Official homepage title · retained in its source language