Platform overview

GlobalStacks is organized around three product areas: Studio, Products, and Infra.

Studio is where software is created and changed: workspaces, tasks, source control, reviews, blueprints, builds, artifacts, and agent-assisted workflows.

Products is where software is shipped and operated: product surfaces, environments, applications, services, deployments, data services, domains, releases, support, and observability.

Infra is the secure execution substrate underneath both areas: hosts, connected agents, clusters, managed capacity, sandboxes, networks, volumes, Access, secrets, registries, recovery, and infrastructure activity.

The core product is not a single hosting workflow. Studio and Products consume shared Infra primitives so teams can run secure workspaces, agent tasks, preview flows, hosted app platforms, continuous integration (CI) fleets, remote development environments, customer-hosted app platforms, and GlobalStacks-managed clusters on the same control plane.

Network stack level

GlobalStacks spans multiple layers:

• Layer 2 (L2) and host networking implementation: tap devices, bridges, network namespaces, and host firewall primitives
• Layer 3 (L3): private addressing, routing, mesh membership, subnet and network boundaries
• Layer 4 (L4): port and protocol policy, Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) reachability, port forwarding
• Layer 7 (L7): Hypertext Transfer Protocol (HTTP) routing, domains, Transport Layer Security (TLS), and preview Uniform Resource Locators (URLs) when higher-level ingress is enabled

Most users should experience this through Studio and Products workflows. Operators still need Infra reports so they can audit runtime and isolation boundaries.

What GlobalStacks owns

GlobalStacks owns placement, runtime approval, network policy, control-plane identity, audit records, and typed agent communication. Sandboxes and managed-capacity agents do not self-select tenants, clusters, providers, or runtime authority.

Provider extensions and host agents report what capacity exists. The control plane decides what can run there. Sandboxes are Infra runtime instances; Studio workspaces and tasks can use them, but sandboxes are not the product or workspace root.

Where to go next

• Use the runtime layer page to understand Infra sandboxes, micro virtual machines (microVMs), and placement.
• Use the network layer page to understand mesh networking, firewall policy, and port forwarding.
• Use the app-platform building blocks page to see how Products can run Vercel-like platforms on your own infrastructure.