Does it work with texted verification codes?

Yes, and it is live today. A dedicated number receives the text, LetMeInNow reads the one-time code out of it, and it lands in front of whoever is signing in before it expires.

Does it work with authenticator apps?

Yes, and it is live today. A shared vault holds the account's authenticator secret and generates the rotating six-digit code for the team, the same code an authenticator app would show, so it isn't locked to one phone.

Can it catch magic links?

Not yet. Texted codes and authenticator codes reach the right person today, and routing an emailed sign-in link to them is the next thing we are building, not something we claim now. Magic links are fragile because they open on whatever device grabbed the email.

What if a service can only text the code to one phone?

That is exactly what the dedicated number is for. The service texts its code to that number instead of a personal phone, and LetMeInNow puts it in front of whoever is signing in. A client number is $6 a month, and it is free during the private beta.

Where does the authenticator code actually come from?

From a shared vault that holds the account's authenticator secret and generates the code on demand. It is the same rotating six-digit code an authenticator app would show, just available to the whole team instead of one device.

Private beta / what it catches

Every kind of login code, to the right person.

A sign-in throws a code at you: a text, an authenticator, sometimes a link. LetMeInNow catches it and puts it in front of whoever is signing in, so it never rides a chain of forwarded texts to get there.

01 Request beta access Free during beta

A texted codeSMS one-time code Built An authenticator codeTOTP, rotating six digits Built A magic linkEmailed sign-in link Next

01 / 03

Built · live now

A texted code.

The classic one: a service texts a six-digit code to a phone. A dedicated number catches that text, LetMeInNow lifts the code out of it, and it lands in front of the person actually signing in, first try, before it expires.

01 CATCH

The verification text lands on a dedicated number.

02 READ

LetMeInNow reads the one-time code out of it.

03 IN

In front of whoever is signing in. First try, before it expires.

02 / 03

Built · live now

An authenticator code.

Most accounts don't text at all. They want a rotating six-digit code from an authenticator app, normally locked to one person's phone. LetMeInNow keeps a shared vault: it holds the account's authenticator secret and generates that code for the whole team, so it isn't stuck on anyone's device.

// SHARED VAULT ROTATES · 00:30

One secret, held for the team. The code refreshes on its own timer, the same as any authenticator app, and everyone who needs it can read the current one.

01 VAULT

The shared vault holds the account's authenticator secret.

02 GENERATE

It makes the rotating six-digit code, on demand.

03 IN

Not tied to one phone. Nobody is the single point of failure.

03 / 03

Coming next · not shipped yet

A magic link.

Magic links are the fragile one. The email opens the link on whatever device grabbed the message, which is usually not the device signing in. That is the magic-link loop, and it is the exact coordination pain LetMeInNow exists to end.

The account emails a one-tap sign-in link.Sent

It opens on whatever device holds the inbox, not the one at the sign-in screen.Wrong device

So it gets forwarded around until it reaches the right person, or it expires first.The loop

Codes and the authenticator already reach the right person. Routing an emailed link to them too is the next thing we're building, not something we claim today.

THE PATH

However it arrives, the path is the same.

Caught, walled to the client it belongs to, and delivered to whoever is signing in. Nothing crosses between clients.

A / CATCH

Caught the moment it arrives

A text on a dedicated number, or a fresh code from the vault. No forwarding, no relayed screenshots.

B / WALLED

Walled to one client

Tagged to the workspace it belongs to. Each client sees only its own codes. Nothing leaks between them. Ever.

C / DELIVERED

In front of the right person

Waiting for whoever is signing in to copy. First try, before it expires. No waiting on a text that never came.

01 Request beta access Back to the overview

FAQ

What it catches, and what's next.

Texted codes and authenticator codes today. Where magic links stand, straight.

Does it work with texted verification codes?: Yes, and it is live today. A dedicated number receives the text, LetMeInNow reads the one-time code out of it, and it lands in front of whoever is signing in before it expires.
Does it work with authenticator apps?: Yes, and it is live today. A shared vault holds the account's authenticator secret and generates the rotating six-digit code for the team, the same code an authenticator app would show, so it isn't locked to one phone.
Can it catch magic links?: Not yet. Texted codes and authenticator codes reach the right person today, and routing an emailed sign-in link to them is the next thing we are building, not something we claim now. Magic links are fragile because they open on whatever device grabbed the email.
What if a service can only text the code to one phone?: That is exactly what the dedicated number is for. The service texts its code to that number instead of a personal phone, and LetMeInNow puts it in front of whoever is signing in. A client number is $6 a month, and it is free during the private beta.
Where does the authenticator code actually come from?: From a shared vault that holds the account's authenticator secret and generates the code on demand. It is the same rotating six-digit code an authenticator app would show, just available to the whole team instead of one device.