Opportunities › Secure credential input for password managers › Proposed app
Hushdoor
Unlock KeePass-style vaults from the CLI without shell history or env vars.
- Score
- 47
- confidence 34
- Evidence
- 1
- items on the page
- Rivals
- 1
- named in sources
- First version
- 35 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 2025
- New market · AI estimate
ScreensConcept
Desktop and mobile: Developers use the CLI tool at desks for secure credential access, but must approve unlocks on phones to keep the workflow seamless. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
Unlock request
Waiting for youApprove?
About this appAI proposal
Hushdoor lets you unlock a password manager from the command line without typing the master password into the shell or exporting it as an environment variable. You approve the unlock on your phone or in a browser tab, and a small local helper passes the secret straight to the tool that needs it.
It is built for developers and sysadmins who use KeePass-style vaults in terminals and scripts. One Hacker News user found fnox's FNOX_KEEPASS_PASSWORD environment variable uncomfortable because of shell history exposure. Hushdoor removes that step.
Each unlock is a short-lived, single-use grant. Nothing is written to history, env or disk, and every grant is logged so you can see what asked for your vault and when.
- Tagline
- Unlock your vault without leaving a trace in your shell.
- Voice
- CalmPrecisePlainspoken
- Why this name
- A door you open quietly: the master password goes in without a sound in history, env or logs. Two plain words joined, easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
No history, no env
The master password never appears on a command line or in an environment variable. The helper hands it to the target process over a private pipe.
No member yet
Approve on your phone
Type or confirm the password in the Hushdoor PWA. Your terminal only learns that the unlock was approved.
No member yet
Single-use grants
Each grant works for one process and expires in seconds. A leaked grant ID is useless afterwards.
No member yet
Short-lived memory use
The local helper holds the secret in locked memory only as long as needed, then zeroes it.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F5C4DPine · primary#F4F1EAPaper · surface#1C2420Ink · text#D9822BAmber · accent#3B6EA8Slate Blue · data
Typography
Aa
Hushdoor
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Unlock your vault without leaving a trace in your shell.
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, not based on any market figure.
Solo
Free
- One vault
- Single-use grants
- Local history of the last 20 unlocks
Pro
$6 a month
- Unlimited vaults and hosts
- Phone approval
- Full audit log export
Team
$5 a month
- Per user, 5 seat minimum
- Shared policies
- Approver rules
- 90-day central audit log
Would you pay Team · $5 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Users invite others. Team admins invite colleagues to approve unlocks and share policies. Teams set up the helper on each host, so use spreads across a team's machines and people.
- Do they become customers?
- Invited teammates are real developers who can become paying seats. Test whether a solo user's first team invite happens within two weeks of install.
- First customers
- Small DevOps and platform teams of 3 to 15 engineers who already keep secrets in KeePass-style vaults and use CLI tools such as fnox.
- Where to reach them
- Hacker News: Post a technical write-up on the shell history problem with an open-source helper and a sign-up for the PWA.
- Developer forums: Answer questions on secrets handling in sysadmin and DevOps communities, linking a short demo.
- Tool issue trackers: Offer a Hushdoor integration guide to maintainers of CLI tools that read master passwords from env vars.
- First milestone
- Ten teams install the helper, and five pay for Pro or Team within 60 days.
Why people already pay for this
- Public claimUser found environment variable approach for storing master passwords uncomfortable due to shell history exposure
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Local helperSmall signed native CLI agentA PWA cannot hand a secret to a terminal process or lock memory; a local binary must do this.
- This app · Secure channelEnd-to-end encrypted relay (WebSocket)Carries the approval and secret between phone and helper without the server reading it.
RisksAI inference
- TechnicalPassing a secret to another process without exposure depends on each password-manager tool's input options. Some may only accept env vars or prompts, which limits integration.
- CommercialEvidence is one public comment. Many developers may accept the risk or use keyfiles and OS keyrings, so demand is unproven.
- TechnicalTyping the password on a phone moves the risk to the phone and the relay. The end-to-end design must be sound and reviewable.
- PlatformA PWA on iOS has limits on background work, so notification-based approval may be unreliable.
- RegulatoryHandling master passwords invites close security review. Buyers may expect an independent audit before trusting it.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.