Build app platforms

GlobalStacks is designed to be the substrate for higher-level app platforms. A team can use it directly for sandboxes and networks, or build product workflows on top of it.

Examples:

• internal developer platforms
• preview environment systems
• customer-hosted app platforms
• hosted app platforms on owned hardware
• continuous integration (CI) runner fleets
• secure remote development workspaces

What GlobalStacks provides

GlobalStacks provides the parts that are hard to re-create safely:

• runtime placement
• sandbox and micro virtual machine (microVM) lifecycle
• private networking
• firewall policy
• port forwarding
• volume attachment
• agent-managed host capacity
• provider-backed machine provisioning
• audit records
• runtime and isolation reporting

That lets platform builders focus on the product layer instead of writing their own host agent, scheduler, firewall controller, and sandbox runtime from scratch.

What you build on top

A Vercel-like product usually adds:

• project and service models
• Git integrations
• build jobs and build cache
• deployment revisions
• release promotion and rollback
• custom domains
• Transport Layer Security (TLS) certificates
• Hypertext Transfer Protocol (HTTP) routing
• preview Uniform Resource Locators (URLs)
• environment variables and secrets
• usage-based billing

GlobalStacks does not force one app model. It provides the lower-level runtime and network control plane those app models need.

Reference shape

Your platform user interface (UI) and application programming interface (API)
  |
  | projects, services, deployments, previews
  v
GlobalStacks control plane
  |
  | placement, policy, network topology, audit
  v
GlobalStacks agents
  |
  | sandboxes, micro virtual machines (microVMs), port forwarding, firewalling, volumes
  v
Your infrastructure or GlobalStacks-managed capacity

Use GlobalStacks when you want the control plane and isolation layer, but still want freedom to define the app platform experience above it.