Project architecture

Static frontend and backend in one project

Console & MCP

app.plurabase.com

console session · per-project tokens

Customer frontend (Sites)

s-<site>.plurabase.app

publishable key only · opaque origin

Project API

<project_ref>.api.plurabase.com

PostgREST · Auth · Realtime · Storage · Functions

Each project's backend (Supabase open-source services)

PostgreSQL 17.6

PostgREST

GoTrue Auth

Realtime

Storage

Edge Functions

Planned public domains; none of them serves traffic yet. During the pilot everything is served on a private Tailscale hostname.

A project with its own backend

In the pilot, an admitted account creates its project from the private console. Each project gets its own PostgreSQL 17.6, Auth, PostgREST, Realtime, Storage and Edge Functions. Sign-up and creation without operator help are installed on the pilot, which is not open to the public.

Code or an agent connected

The application uses @supabase/supabase-js v2. An agent connects over MCP with a token for one project and an operation_id on every write.

Migrations and Row Level Security

RLS policies with USING and WITH CHECK keep each user to their own rows, including when the browser calls the API directly.

Frontend published on Sites

A person uploads the static build as a ZIP; the app reads ./__simplybase/config.json and an earlier release comes back without touching the database. Git deploys are in development.

Agent quickstart