Skip to main content
reg121.cloud is the managed backend platform that powers every REG121 site. When you create a site, the platform automatically provisions a dedicated Postgres schema, a REST API layer, and a full authentication infrastructure — scoped to that site. There is no separate backend tier to configure or unlock; these capabilities are part of every plan.

Postgres Storage

Each site is backed by its own isolated Postgres schema. Data is stored relationally and tenant isolation is enforced at the database level, not just in application logic.

REST API

A per-site REST API layer is provisioned automatically. You interact with your site’s data and logic through this API without configuring or deploying an API server yourself.

Authentication

Each site gets its own auth infrastructure supporting end-user account creation and login. Auth state is tied to the site’s isolated schema and does not cross tenant boundaries.

Tenant Isolation

Isolation is enforced at the database level. One tenant’s schema cannot be accessed by another tenant’s application layer, structurally — this is not enforced only by application code.

​
What’s Included in Every Plan

Every site created on REG121 is automatically provisioned with the following infrastructure. No additional steps or plan upgrades are required.
  • Isolated Postgres schema — a dedicated schema within the shared Postgres cluster, scoped exclusively to the site
  • REST API layer — a per-site API endpoint layer that exposes your site’s data and operations
  • Authentication infrastructure — end-user account creation, login, and session management, backed by the site’s own schema
  • Tenant isolation — database-level schema isolation ensuring one site’s data cannot be reached from another site’s application layer
Schema provisioning is automatic at site creation. You do not provision or configure the database.

​
Design Philosophy

REG121 is built for developers and agencies who want to use REG121 as infrastructure rather than as a closed platform. The intent is straightforward: you bring the tools and workflows you already know, and REG121 manages the infrastructure underneath. That means you work with a real REST API, real Postgres-backed storage, and a defined authentication layer — the same primitives you would reach for in any standard web project. REG121 handles provisioning, isolation, and maintenance of those layers so you do not have to. There are no proprietary abstractions you need to adopt. If you can make an HTTP request or connect to a Postgres-compatible client, you can build on REG121.
For details on how tenant isolation is implemented at the schema level — including how row-level and schema-level isolation interact — see the Architecture page.