Your team stops asking you for verification codes.
Shared accounts send their verification email to one address. HeyPass reads that address and delivers each code to the person who requested it, in seconds, without giving them access to the mailbox it arrived in.
Free for small teams when we open. No card. One email to tell you we are live, and nothing after that.
One inbox, several people, one bottleneck.
Whoever owns the shared address becomes part of every login their colleagues attempt. It is a small task that arrives without warning and cannot be batched.
You reply at 4:34. The code expired at 4:31, so the request comes back.
A colleague in another timezone starts at nine. You are asleep, and their morning is spent waiting.
Two people sign in at once. Two codes land seconds apart, and neither knows which is theirs.
Someone left in March. You cannot say what they can still reach.
The usual fix is handing out the mailbox password, which gives away the invoices sitting next to the codes.
Your own numbers.
Two sliders. The figure underneath is hours a year, and it moves as you drag.
This is an estimate at five minutes a request, which covers finding the email and returning to what you were doing. Move the sliders to match your team.
What the person requesting sees.
Some services send six digits. Others send a link that works once, or ask whether a browser attempting to sign in belongs to you. All three arrive the same way.
They receive the code. The rest of the inbox stays yours.
Below is a shared mailbox on an ordinary morning. Your colleague sees one line of it.
Nobody on your team is given a mailbox login, so there is no need to weigh trusting a colleague against what else is in there.
What HeyPass stores, and for how long.
Three things persist. Everything else is removed on a timer.
The code, link or approval
Deleted once it expires. Links are kept exactly as sent and are never opened by us, since one visit would spend them.
The request record
Who asked, when, which account, which sender answered, and whether it was used. No message body is kept with it.
Every other message that arrives
Invoices, client threads, bank alerts. No person at HeyPass opens them, they are never indexed, and they are removed automatically.
Once the window closes the message is gone from our side and cannot be retrieved by anyone, including us.
HeyPass never holds your mailbox password.
The connection is a forwarding rule you set at your end. There is no login step and no token of yours on our servers, and you can switch the rule off in ten seconds without telling us.
Forward everything
Three minutes to set up. You can search recent mail inside HeyPass and build a login straight from a real verification email, so no rule is written by hand. Anything unmatched is removed within 48 hours.
Forward a filtered set
A filter, so only senders you name ever reach us. Your invoices and client threads never leave your mailbox. You add each sender yourself, which takes about ten seconds per account.
Auto-forwarding, any provider
Gmail and Google Workspace, connected directly
Microsoft 365 and Outlook, connected directly
Zoho Mail, connected directly
Forwarding already covers every provider on that list, so nothing is blocked while the direct connections are built. Manual forwarding will not work, because it strips the headers that separate one of your accounts from another.
Every request is on the record.
The log answers questions that shared logins normally leave open.
Which subscriptions nobody has opened since February, ahead of the renewal date.
Who reached the developer account on Tuesday, and which email answered them.
A verification email arriving that nobody requested, which means the login is being tried from outside your team.
What someone leaving on Friday can still reach.
Free for small teams.
Not a trial with a clock on it. A small team can stay on the free plan for as long as they like.
Free
$0No card, no expiry.
- Verification codes, sign-in links and browser approvals
- Forwarding from any mail provider
- Access granted per member, removed the same minute
- Full request log
- Automatic deletion of everything unmatched
Team
Later this yearFor larger teams. Priced before we switch it on.
- Everything in Free
- Higher member and account limits
- Longer log retention
- Approval required before a code is released
When HeyPass is the wrong tool.
You already use single sign-on
The problem is solved. HeyPass would sit on top of something that already works.
You can afford a seat for each person
Buy the seats. It is a cleaner arrangement and we would say so if you asked.
Sharing would breach your agreement with the provider
HeyPass makes an organisation's own shared accounts tidier and auditable. It does not make an arrangement permitted that your provider prohibits.
The account is personal, financial, medical or governmental
These are outside what HeyPass is built for and are excluded under the terms.
Join the waitlist.
We open to the first teams shortly. Waitlist members get access first and see pricing before it is published.
One email when we open. Privacy policy
Questions
Is HeyPass a password manager?
No. Your team signs in with the password from wherever they keep it now. HeyPass handles the verification code or link that arrives afterwards, which is the part that currently goes through a person.
Do you need my mailbox password?
No. There is no login step and no token of yours on our servers. You set a forwarding rule at your end and can remove it whenever you like.
Do I have to forward my whole inbox?
No. A filter can restrict it to senders you name, and everything else stays in your mailbox. If you do forward everything, anything that is not a verification email is deleted automatically within 24 to 48 hours, and no person at HeyPass opens it.
Which mailboxes work?
All of them, because the connection is forwarding rather than a login. Gmail, Google Workspace, Microsoft 365, Outlook and Zoho all forward. Direct connections arrive later as an option. Manual forwarding is not supported, because it removes the headers that identify which of your accounts the message was for.
What happens when two people need the same account at once?
One person holds it and the others queue. The hold releases on its own, and the next person receives the code without messaging anybody.
Someone leaves. Are they locked out?
They stop receiving codes for that account the same minute you remove their access. The shared password will still be in their password manager, so rotate it as you would normally. What you gain is a second factor they can no longer pass, immediately.
What will it cost?
Nothing for a small team. The free plan is not a trial. A paid plan for larger teams arrives later and its price will be published before it is switched on.
When do you open?
Within weeks rather than months. Everyone on the waitlist hears on the same day.