Developer implementation track
Set up the project, run Supabase safely, configure OAuth, validate APIs, install the node agent, and deploy to production.
OpenStep-by-step launch enablement for developers, operators, and customers.
Use this center as the practical operating manual for moving UmamiEdge from local setup to controlled global pilot execution.
Tracks
Four practical tracks for launch execution.
User and operator track
Sign in, create an organization, add sites, register nodes, monitor health, manage customers, and complete acceptance gates.
OpenLaunch execution track
Coordinate pilots, legal readiness, contracts, training, implementation, support, and executive approval.
OpenOperational readiness track
Validate status, observability, migrations, deployment runs, SLA, failover, and compliance evidence before customer traffic.
OpenDeveloper path
Implementation sequence.
These are the engineering steps that must pass before a pilot can depend on the platform.
Prepare the local workspace
A clean Next.js project running locally without legacy route leftovers.
Evidence: Homepage loads, /docs opens, and /api/health returns a JSON response.
Configure environment variables
The app can connect to Supabase from browser, server routes, and admin-only workflows.
Evidence: Login page renders without missing configuration warnings.
Run database compatibility fixes
Older Supabase databases are upgraded before the main schema and seed scripts run.
Evidence: No missing column, duplicate enum, function parameter, or not-null seed errors appear.
Configure Supabase Auth
Google, GitHub, and magic-link sign-in work locally and in production.
Evidence: Login with Google or GitHub returns to / by default and /login?next=/operator returns to /operator.
User path
Operator sequence.
These are the steps a non-developer follows to activate a tenant, register sites and nodes, and prepare go-live.
Sign in
You enter the platform with a valid Supabase session.
Evidence: Header shows your email and Sign out.
Create the organization
A tenant is created for your team, customer, or pilot network.
Evidence: Organization appears in the switcher and onboarding proceeds to site setup.
Add the first site
A physical or commercial host location is registered.
Evidence: Site is available for node registration.
Register the first node
A GPU or inference node exists in the registry with a secure telemetry key.
Evidence: Node appears under /nodes and the key prefix appears under /nodes/keys.