Same-origin trust boundary
The browser talks only to smohix.run. API keys and private Railway URLs stay on the server.
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 smohix.run — marketing, console, same-origin API routes
Smohix Own API
Documented gateway surface — product UIs call Own API / same-origin routes; private backends stay server-side
Platform
Incidents, automations, approvals, audit, Copilot modules
AI Gateway
Copilot route, reasoning proxy, optional OpenAI
Providers
Configured AI and automation backends (server-side only)
Storage
Supabase Postgres, auth, RLS-scoped workspace data
Infrastructure
Deployed services with private networking — topology not published
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.