Ingress and routing
Nginx terminates TLS at your edge ingress, separates install host and app host routes, and proxies public/community/API surfaces.
The platform combines gateway APIs, canvas/admin UIs, policy controls, and release evidence lanes so features are backed by operational proof.
Nginx terminates TLS at your edge ingress, separates install host and app host routes, and proxies public/community/API surfaces.
Central runtime contract for orchestration, policies, telemetry, public proofs, and feature/status checks.
Admin controls operations and policy. Canvas powers user-facing runtime and community experiences.
Switch runtime planes to inspect boundary ownership and where each service responsibility sits in live deployment.
Single trusted entrypoint for install host and app host domains.
Routes install surfaces, community, admin, and APIs without overlap.
Edge headers and route restrictions enforce clean external exposure.
Owns workflow execution, telemetry, policy checks, and status contracts.
Capability-proof, feed, and readiness are externally verifiable.
Wave and checklist gates prevent drift between claims and runtime behavior.
Primary operator and end-user interaction surface.
Policy and operational controls for governance and diagnostics.
Identity-gated contributor channel for education and reproducibility.
| Surface | Purpose | Primary route | Status |
|---|---|---|---|
| Install + Landing | Bootstrap and public entry | sven.systems | active |
| Canvas Runtime | Main interactive experience | app.sven.systems/ | active |
| Admin47 | Operator controls | app.sven.systems/login?redirect=%2Fadmin47 | active |
| Community Hub | Verified ecosystem and feeds | app.sven.systems/community | loading |