Skip to content

One sign-in for every REM app

Every REM app now signs people in through REM Auth. One account, one password, one set of second factors - and apps that never see your password. Here is how it works and why we built it this way.

RREM Team3 min read

REM makes several apps: REM Payments, REM Blogs, REM CloudHub, REM Vibe Coder and more. Until recently each one had its own sign-in, its own password rules and its own idea of who you were. Today every REM app signs people in through one place, REM Auth, at auth.remplatforms.com.

What changes for you

  • One account. You create it once, confirm your e-mail once, and use it in every REM app.

  • One password. Change it in one place and every other device is signed out at once, everywhere.

  • One set of second factors. Add an authenticator app, a security key or a passkey on your account page, and it protects every REM app.

  • One profile. Your picture, name and language follow you into each app.

When you choose Sign in in any REM app, it sends you to REM Auth. The screens show the name of the app you came from, and when you are done you are sent straight back. If you are already signed in to REM Auth in that browser, the next app lets you in without asking again.

Apps never see your password

This is the main reason we did it. An app that keeps passwords has to store them safely, rate-limit guesses, handle resets and second factors, and get every one of those right. Now only REM Auth does that. The apps receive a signed token that says who you are, what your verified e-mail is, which teams you are in and what your role in that app is. Nothing more.

Rules that keep accounts real

We were strict about three things:

  1. An address must be proven. A new account works only after you open the confirmation link we mail you. Apps trust your e-mail and give you roles only while it is verified; change your address and it is unverified until you confirm the new one.

  2. One account per mailbox. name+shop@gmail.com and n.a.m.e@gmail.com are the same Gmail mailbox, so they are one account. Throwaway mail domains are refused.

  3. No hints to strangers. Signing up with an address that already has an account gives the same "check your e-mail" answer, and the real owner gets a mail saying so. The forgot-password page answers the same way whether or not the address exists. Nobody can find out who has an account by trying addresses.

Wrong passwords count against both the address and the username, so guessing from many places does not help; after about five failures in a row sign-in waits. Every new password must be at least 10 characters with mixed case, a digit and a symbol, and must not be easy to guess.

For teams and administrators

Access is decided in one place too. An organisation has teams; a product lists which teams may use it and with which role (for example admin, editor or viewer). Put someone in a team and they get the right apps with the right roles at their next sign-in. Take them out, or switch the account off, and every app hears about it at once through a signed event.

For developers

REM Auth is a standard OpenID Connect provider. An app connects itself at deploy with two values, REM Auth's address and a connect token, and gets its client id and secret back. It can send people to REM Auth's pages, or draw the same screens inside the app with our @rem/auth-react SDK, where the browser never leaves its domain. The REM Auth developer docs have the endpoints, the claims and the webhooks.

Start at auth.remplatforms.com, and read the user guide for every screen. Questions: support@remplatforms.com.

AIProduct

REM Credits: one ledger for every REM app

AI actions in REM apps are paid for in REM Credits. All of them are kept in one ledger, in REM Payments, with every movement and its reason. Here is how credits are granted, spent and taken back.

RREM Team18 Nov 2026 · 3 min read
One sign-in for every REM app · REM Platforms Blog