Skip to main content
Every REG121 site includes a full authentication system for end users. This system is provisioned automatically when the site is created and is isolated to that site — there is no shared auth layer across sites. The underlying storage is the same per-site Postgres schema that backs all other site data.

​
What Is Supported

End-user account creation and login is live in production. Users of a generated site can register for an account and authenticate with that account. Each site’s authentication is independent: a user account created on one site has no relationship to, and cannot be used on, another site. Auth isolation is enforced at the same database level as all other data isolation — each site’s user records exist within that site’s dedicated schema.

​
Implementation Details

Auth flow specifics, token formats, session handling, and SDK integration details are not yet documented here. This section will be updated once engineering confirms the public interface. Contact REG121 support for current guidance.
The specifics of how authentication is implemented — including token formats, session lifetimes, endpoint paths, credential exchange flows, and any SDK or client library integration — are not yet publicly documented. Do not build integrations against inferred or undocumented auth endpoints. Once the public interface is confirmed, this section will be updated with precise implementation details.

​
Isolation

Auth data — including user account records and session data — is stored within the same per-site Postgres schema as all other site data. This means the isolation guarantees that apply to custom tables and form submissions apply equally to authentication data. No auth data crosses site boundaries at the database level. The structural isolation model is described in full on the Security & Isolation page.