Security and privacy decision
Enpass
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Enpass, store an encrypted vault locally and optionally sync it through the user's own cloud folder. The hard boundary is mature apps, browser extensions, platform biometrics, and ongoing security maintenance, plus security assurance, infrastructure, and trust.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Store an encrypted vault locally, optionally sync it through the user's own cloud folder, and document the threat model explicitly with no claim of replacing an audited service.
What it still won’t have
- mature apps, browser extensions, platform biometrics, and ongoing security maintenance
- independent security audits
- global relay infrastructure
- breach monitoring data
- account recovery and support
What remains hard
- Brand trust
- Execution quality
First-year cost
The build hours below are a category default, not an estimate for this product. Change them to your own numbers and the comparison follows.
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a personal replacement for Enpass in an empty repository. Use Rust, Tauri 2, React, SQLite, Argon2id, and audited cryptographic libraries; do not offer alternative stacks. The core loop is: store an encrypted vault locally, optionally sync it through the user's own cloud folder, and document the threat model explicitly with no claim of replacing an audited service. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Write a plain-language threat model before implementing any sensitive feature. Keep all vault data encrypted with a master key derived through Argon2id and a unique salt. Use authenticated encryption from a maintained library and never invent cryptographic primitives. Implement lock timeout, clipboard clearing, password generation, import, export, and encrypted backups. Make recovery-key creation explicit and test restore from a fresh installation. Display a persistent warning that the build has not received an independent security audit. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a production VPN or anonymity network. Deliberately leave out identity-protection monitoring and data-broker removal. Deliberately leave out enterprise security guarantees, audits, and emergency support. Finish by running the tests and listing the exact commands used.
