Same-origin trust boundary
The browser talks only to zentro.run. API keys and private Railway URLs stay on the server.
Platform
System architecture
One intelligent platform — from operators in the browser to private services on Railway. Every layer is a capability, not a separate product silo.
Architecture diagram
Users
Operators, developers, approvers, auditors
Frontend
Next.js at zentro.run — marketing, console, same-origin API routes
Platform
Incidents, automations, approvals, audit, Copilot modules
AI Gateway
Copilot route, reasoning proxy, optional OpenAI
Providers
OpenAI, SH backend, Robot backend (private Railway network)
Storage
Supabase Postgres, auth, RLS-scoped workspace data
Infrastructure
Railway services, private *.railway.internal networking
Platform as hub
Incidents, automations, Copilot, and billing modules share Supabase identity and audit context.
Optional backends
Reasoning, robot, and Own API services connect via env-configured proxies — not hard-coded secrets in this repo.