Disclaimer
This project is for learning and communication purposes only. We are not responsible for any data loss; regular vault backups are strongly recommended.
This project is not affiliated with Bitwarden. Please do not report issues to the official Bitwarden team.

Feature Comparison Table (vs Official Bitwarden Server)

Capability	Bitwarden	NodeWarden	Notes
Web Vault (logins/notes/cards/identities)	✅	✅	Web-based vault management UI
Folders / Favorites	✅	✅	Common vault organization supported
Full sync `/api/sync`	✅	✅	Compatibility and performance optimized
Attachment upload/download	✅	✅	Choose either Cloudflare R2 or KV
Import / export	✅	✅	Fully implemented, including Bitwarden vault + attachments ZIP import
Website icon proxy	✅	✅	Via `/icons/{hostname}/icon.png`
passkey / TOTP fields	✅	✅	Fully supported, no premium required
Send	✅	✅	Choose either Cloudflare R2 or KV
Multi-user	✅	✅	Full user management with invitation mechanism
Organizations / Collections / Member roles	✅	❌	Not necessary to implement
Login 2FA (TOTP/WebAuthn/Duo/Email)	✅	⚠️ Partial	User-level TOTP only
SSO / SCIM / Enterprise directory	✅	❌	Not necessary to implement
Emergency access	✅	❌	Not necessary to implement
Admin console / Billing & subscription	✅	❌	Free only
Full push notification pipeline	✅	❌	Not necessary to implement

Tested clients / platforms

✅ Windows desktop client (v2026.1.0)
✅ Mobile app (v2026.1.0)
✅ Browser extension (v2026.1.0)
✅ Linux desktop client (v2026.1.0)
⬜ macOS desktop client (not tested)

Quick start

One-click deploy

Deploy steps:

If you only want a quick trial, simply click the one-click deploy button in step 2. The remaining steps are mainly for long-term maintenance.

Fork this repository and name it NodeWarden.
Click the button below. On the page that opens, rename the project to NodeWarden2 and set JWT_SECRET to a random 32-character string.
After deployment, open the Worker settings on the same page and disconnect the Git repository.
Reconnect the Git repository to the fork from step 1, then change the Name field at the bottom to NodeWarden.
The temporary NodeWarden2 repository can be deleted.

📦 If you do not have a payment method attached and cannot enable R2 object storage, you can use KV mode instead

R2: requires a payment method; single attachment / Send file limit is 100 MB (project-level limit, editable in code); 10 GB free storage

KV: no card required; single attachment / Send file limit is 25 MiB (Cloudflare limit, not editable); 1 GB free storage

Fork this repository and name it NodeWarden.

Open your GitHub repository, go to the Actions page, and run Switch to KV mode (this automatically switches wrangler.toml to the KV configuration).

In your own repository, click the button below. On the page that opens, rename the project to NodeWarden2 and set JWT_SECRET to a random 32-character string.

After deployment, open the Worker settings on the same page and disconnect the Git repository.

Reconnect the Git repository to the fork from step 1, then change the Name field at the bottom to NodeWarden.

The GitHub repository NodeWarden2 can be deleted.

Tip

Sync upstream (keep your fork updated):

Manual: open your fork on GitHub and click Sync fork when prompted.

Automatic: in your fork, go to Actions, click I understand my workflows, go ahead and enable them. Once enabled, Sync upstream will automatically sync the upstream main branch every day at 3 AM and keep your current wrangler.toml configuration unchanged.

CLI deploy

# Clone repository
git clone https://github.com/shuaiplus/NodeWarden.git
cd NodeWarden

# Install dependencies
npm install

# Cloudflare CLI login
npx wrangler login

# Create cloud resources (D1 + R2)
npx wrangler d1 create nodewarden-db
npx wrangler r2 bucket create nodewarden-attachments

# Deploy
npm run deploy 

# (Optional) KV mode (no R2 / no credit card)
npx wrangler kv namespace create ATTACHMENTS_KV
# Replace placeholder inside `id = "placeholder"` in wrangler.kv.toml with the returned namespace id (keep the quotes)
npm run deploy:kv

# To update later: re-clone and re-deploy — no need to recreate cloud resources
git clone https://github.com/shuaiplus/NodeWarden.git
cd NodeWarden
npm run deploy

Local development

This repo is a Cloudflare Workers TypeScript project (Wrangler).

npm install
npm run dev

FAQ

Q: How do I back up my data?
A: Use Export vault in your client and save the JSON file.

Q: Which import/export formats are supported?
A: NodeWarden supports Bitwarden json/csv/vault + attachments zip and NodeWarden vault + attachments json in both plain and encrypted modes, and every format visible in the import selector is directly importable.
A: It also supports direct import of Bitwarden vault + attachments zip, which is not directly supported by official Bitwarden Web import.

Q: What if I forget the master password?
A: It can’t be recovered (end-to-end encryption). Keep it safe.

Q: Can multiple people use it?
A: Yes. The first registered user becomes the admin. The admin can generate invite codes from the admin panel, and other users register with those codes.