Stop being your team's OTP machine.
Shared accounts send their verification codes to one inbox. Yours. HeyPass hands each code to whoever asked for it, in seconds.
Free for small teams when we open. No card.
Your own numbers.
An estimate at five minutes a request, covering the time to find the email and return to what you were doing.
Codes are only part of it.
Some services send six digits. Others send a link that works once, or ask whether a browser signing in belongs to you.
They receive the code. The rest stays yours.
Nobody is given a mailbox login, so there is nothing to weigh against what else is sitting in there.
You decide who can request what.
Every request is on the record.
Which subscriptions nobody has opened since February. Who reached the developer account on Tuesday. Whether a code arrived that nobody asked for, which would mean the login is being tried from outside your team.
We never hold your mailbox password.
The connection is a forwarding rule you set at your end, and remove whenever you like. Three things are stored. Everything else goes on a timer.
The code, link or approval
Deleted when it expires. Links are never opened by us, since one visit would spend them.
The request record
Who asked, when, which account, which sender answered. No message body.
Everything else that arrives
No person at HeyPass opens it, it is never indexed, and it cannot be retrieved afterwards.
Auto-forwarding, any provider
Gmail, Microsoft 365 and Zoho, connected directly
Forwarding covers every provider today, so nothing waits on the direct connections. A filter can restrict it to senders you name.
Free for small teams.
Free
$0No card, and no expiry.
- Codes, sign-in links and browser approvals
- Forwarding from any mail provider
- Access per member, removed the same minute
- Full request log
Team
Later this yearPriced before we switch it on.
- Higher member and account limits
- Longer log retention
- Approval before a code is released
When HeyPass is the wrong tool.
You already use single sign-on
The problem is solved.
You can afford a seat for each person
Buy the seats. It is a cleaner arrangement.
The account is personal, financial, medical or governmental
Excluded under the terms. Sharing that would breach your provider's agreement is your call to check, not ours.
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
If you are the one asking for codes rather than sending them, this page is written for you.
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. 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. Manual forwarding will not work, because it removes the headers that identify which of your accounts a 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.