Campus Compute

Campus Compute runs durable, globally reachable software on selected hardware while preserving the same installation and Gateway boundaries across deployment modes.

Configure hardware, not trust

An account can use its own Node or Campus-hosted capacity. Placement changes where a workload runs; it does not change the application’s identity or authority.

CampusOS → Campus Mux → Campus Node Runtime → isolated workload
                                      └────→ per-installation Gateway

The Runtime owns isolation, volumes, lifecycle, and machine-local network attachment. Each installation gets its own Gateway for private data traffic, public ingress checks, service forwarding, and sealed outbound requests.

Lifecycle

Workloads use foreground, automatic, or always-on lifecycle modes selected by the user. Authorized MCP calls, schedules, public routes, visible interfaces, and bounded work leases provide explicit liveness signals. See background execution.

Reachability

Workloads are private by default. HTTP and WebSocket publication requires a declared route and a matching installation grant. Native UDP publication is separate and Runtime-assigned. See public endpoints and sockets.