Foundry Cloud
Foundry workspace / Cloud Sandboxes & Runtime Preview

Stash your localhost.

Build and test in the cloud, open a working preview in your browser, and review the changes directly in GitHub without local runtime friction.

Architecture — 01
  • Start builds in isolated cloud environments.
  • Open the working app directly in your browser.
foundry-runner: build-session-9912
Example run
01 ✓ Cloning acme/dashboard @ b4e12a8
120ms
02 ✓ Installing project dependencies
380ms
03 ✓ Synthesizing "team invite flow with role selection"
820ms
04 ✓ Spinning isolated ephemeral container at port 3000
210ms
Cloud build finished. Preview ready in the browser.
View route ↗
Systems Spec · Architecture 02

Isolated sandbox execution.

Builds and tests run in isolated cloud environments, keeping project commands separate from your laptop and its credentials.

Layer
Mechanism & Implementation
Execution Boundary
01. Workstation Host
Use the workspace and preview from your browser.
No local server to start
02. Build Sandbox
Project commands run as an unprivileged user with a sanitized environment.
Builds run separately
03. Network Egress
Cloud tasks use private networking with controlled HTTPS egress.
Controlled outbound access
04. Repo Permissions
GitHub App installation tokens are short-lived and scoped to the repository.
Scoped repository access
Isolated environments
Dependency scanning
Secret scanning
Structured audit logs
Design Spec · Architecture 03

Better designs.

Foundry refines the details, carries your design system across screens, and explores new layouts within it.

foundry-design: principles
Illustrated examples

Attention to detail

Fine adjustments in spacing, alignment, and typography make every element feel placed with care.

Optical alignment
  • Optical spacing
  • Aligned baselines
  • Fine borders

Design consistency

Foundry agents reuse existing UI components so new screens look and feel like part of the same product.

One system, multiple screens
  • Shared typography
  • Consistent spacing
  • Reusable components

Controlled creativity

Explore different compositions while keeping the visual language of your product.

Composition studies
  • Layout exploration
  • Flexible components
  • Brand constraints
Automation Spec · Architecture 04

From ticket to product.

Connect your work tracking tool and Git repo, and Foundry will pick up your tickets. Manage the product, not the code.

  1. Pick up a ticket

    Foundry starts with the requirements in your ticket.

    ENG-384 Add team invitations Assigned to Foundry
    Work tracking tool
  2. Build and test

    Foundry implements the change and runs checks in an isolated cloud environment.

    Cloud sandbox
  3. Review the changes

    Foundry opens a pull request and deploys a preview so your team can try the changes.

    Pull request

Turn tickets into working software today.

Build in the cloud, share a working preview, and review the changes in GitHub.

Open your Foundry workspace to get started.