The Master V1 backend
Portable application code on managed PostgreSQL infrastructure.
The application boundary
V1 uses Next.js → MasterController → MasterRecord → PostgreSQL. Supabase is the initial database infrastructure provider. Auth is isolated behind an adapter. Storage needs its own adapter and access tests; it is not included in the initial runtime starter.
The browser calls application APIs. Controllers validate identity, input, authorization and business rules. MasterRecord provides the data-access layer with a separate database context and transaction for each request. Generated application code should not spread Supabase table APIs throughout the frontend.
Development and production
Development runs in Daytona. A production publication builds and tests an artifact in Daytona, then deploys a separate Node container through Coolify. Production credentials do not belong in the development sandbox or browser.
Development and production use separate Supabase projects. A first production baseline transfers supported schema objects, not development users or customer data. Source export is available; moving providers still requires migrating data and configuring any provider adapters.
Availability
The implementation is merged for rollout and live testing. Read managed hosting before planning a launch, and schema lifecycle before changing a database.