Self-hosted clusters
Connect Linux, macOS, Windows, Proxmox, and bare-metal capacity as self-hosted clusters that can schedule sandbox workloads on owned hosts.
Infrastructure
Use the infrastructure you already operate.
GlobalStacks gives teams one control plane for sandbox placement, host readiness, runtime networking, and deployment activity across owned machines and cloud capacity.
ARM64 hosts
Install gstacks and gstacks-agent on Linux ARM64 and macOS ARM64 hosts, including Apple Silicon machines.
Distributed file system
Attach shared sandbox volumes backed by JuiceFS so files can follow workloads through the agent-managed volume path.
Cross-agent mesh
Host agents join a Tailscale-compatible mesh for cluster reachability, health, and data-plane coordination without exposing infra endpoints to sandboxes.
Sandbox mesh and DNS
Attach sandboxes to managed networks with stable DNS aliases and virtual addresses while agents enforce policy and proxy traffic.
Terminal access
Open browser or CLI terminal sessions for connected hosts and sandboxes through the agent-backed terminal path.
SSH and port forwarding
Use managed OpenSSH config for sandbox aliases, join a sandbox network from the CLI, and forward service aliases to localhost.
Deployment model
Owned capacity first, cloud when it makes sense.
The control plane treats connected hosts as schedulable infrastructure. Hosts can be eligible for sandbox placement, host access, or both, and routing labels make placement explicit instead of relying on fragile naming conventions.
The self-hosted runtime is free to run on your own hardware. You bring the machines, storage backend, and network path; GlobalStacks keeps the agent, clustering, sandbox, mesh, and volume workflows consistent.
Release artifacts include Linux ARM64 and macOS ARM64 builds for both the CLI and host agent, so ARM Linux boards, servers, and Apple Silicon Macs can participate in the same self-hosted cluster model.
Host agents join Tailscale-compatible mesh networks for cross-agent reachability. Sandbox workloads stay behind the agent boundary and reach services through GlobalStacks DNS names, virtual loopback addresses, and policy-checked proxies.
Operators can open host and sandbox terminals in the browser or from the CLI. Developers can also use OpenSSH gateway aliases for sandboxes and `gstacks mesh forward` to expose a network alias on localhost during development.
Proxmox deployments use API-backed OCI container import and rolling target selection. Product operations stay on typed APIs and agent RPCs instead of SSHing into control-plane machines.