The cloud machine for your agents, guarded on every path out

The Software Factory is what you run: agents, crews and workflows. The Pix Sandbox is the machine it runs on, a dedicated container running Belai, the open source coding harness, on Cloudflare Sandbox, built from a reproducible Nix image and wrapped in AI, package and egress firewalls, with System One decisions on every call included. Pick its size, repositories and languages in the Resolve Platform.

Pix Sandbox docs

Start a sandbox See pricing

From $85 a month per sandbox

Every way out of the machine passes a gate

Model calls, package installs and every other request leave the sandbox through a control you set in the Resolve Platform, and a System One model reads what comes back before the model does.

From checkout to a running host in one launch

Everything is set up from the Resolve Platform. The sandbox is ready when your first repository is, and the Software Factory runs on it from there.

  1. Start a sandbox. Name it in the Resolve Platform. The machine is created as soon as checkout completes.
  2. Choose repositories. Public GitHub repositories, or private ones through the Vulnesis GitHub App, by branch.
  3. Pick languages. Toolchains and language servers, plus any nixpkgs package, from the signed cache.
  4. Launch. The image is verified, the firewalls go up, your repositories are cloned and Belai comes online.
  5. Run the Software Factory. Agents, crews, workflows and board cards run on the machine from the Software Factory pages, and each run keeps its trace and its evidence.

Clef and Jev decide every call, both included

Clef from Cloudflare and Jev from TypeSafe are security models built for one job: judging whether the text an agent is about to act on is safe. On a Pix Sandbox one of them is Belai's classifier from the first session. Clef is the default and runs on Cloudflare Workers AI, so no Cloudflare key exists on the machine. Switch a sandbox to Jev from its launch settings. Either one reads prompts, file contents, web pages and tool output before the model sees them, and catches prompt injection, jailbreaks and instructions hidden in repository text. The API key is added at the network edge, for TypeSafe's endpoint alone, so the machine holds only a placeholder.

A dedicated container that stays on

Every Pix Sandbox is its own Cloudflare container with a 20 GB disk, running around the clock, in one of three sizes. Small has 1 vCPU and 4 GiB and runs 1 web session and up to 7 agents. Medium has 2 vCPU and 6 GiB and runs 2 web sessions and up to 14 agents. Large has 4 vCPU and 12 GiB and runs 4 web sessions and up to 28 agents. Change size from billing: a running sandbox waits for its agents to finish, then restarts on the new size. It starts with the internet off, opens only the hosts your policy allows, and is reached through the Resolve Platform alone, with no SSH and no open port. Software Factory workflows with a schedule trigger fire on time, and a web session starts the moment you open one.

A reproducible image, built with Nix

The sandbox image is defined by a pinned Nix flake, so the same inputs give the same image, byte for byte. Language packs install as signed closures from the binary cache: Python, Node.js, Go, Rust, Java, Ruby, C and C++, .NET, Zig, Dart and cloud CLIs, plus any nixpkgs package.

Every model call through the AI Firewall

The Vulnesis AI Firewall is switched on at launch. Model calls pass through it, provider keys sync into its vault and stay off the machine, and your policy's blocked patterns, PII redaction, model allowlists and spend limits apply. Belai's permission rules, OS sandbox and classifier stay on for every session.

Malware and exploitable versions stop at the registry

With the Package Firewall add-on, each language you add is pointed at the Vulnesis Package Firewall during launch; without it, package managers use their upstream registries. Known malicious packages, typosquats and compromised maintainer releases are refused, and versions with known exploited, weaponised or high EPSS vulnerabilities are blocked by your thresholds, before a single file reaches the disk.

See every host your agents reach, and decide

Each request out of the sandbox is decided by hostname. The Resolve Platform lists every host it tried, how often, and how often it was refused, with Allow and Deny one click away. Log mode records everything; deny mode refuses every host except the ones you allow. The System One models and both Vulnesis firewalls stay reachable in either mode.

Verify every layer yourself

Run the Software Factory on a machine you can verify

A guarded machine, a verified image and System One decisions on every call, ready when your first repository is. Community includes one self-hosted Belai host. Run belai rc on your machine and the factory runs there.

Run it free on your machine Start a sandbox, from $85 a month Request a demo See pricing

See the Software Factory · Read the launch article

Questions

What is a Pix Sandbox?

The isolated cloud machine the Software Factory runs agents on: a dedicated Belai container on Cloudflare Sandbox that runs around the clock. You choose the GitHub repositories it clones and the languages it installs. The Software Factory is what you run on it, with agents, crews, workflows and board cards from the Software Factory pages in the Resolve Platform.

What sizes are there?

Three, each billed monthly per sandbox. Small, from $85, has 1 vCPU and 4 GiB and runs 1 web session and up to 7 agents. Medium, $180, has 2 vCPU and 6 GiB and runs 2 web sessions and up to 14 agents. Large, $350, has 4 vCPU and 12 GiB and runs 4 web sessions and up to 28 agents. Every size has a 20 GB disk. You pick a size when you buy and can change it from billing.

Which decision models are included?

The System One decision models are included at no charge. One of them is Belai's classifier on every Pix Sandbox from the first session and runs on Cloudflare Workers AI, so no Cloudflare key exists on the machine. A sandbox can switch to another System One model from its launch settings, and that model's API key is added at the network edge for its endpoint alone, so the machine holds only a placeholder.

What protects the machine?

Two firewalls are up before the first session and a third comes with the add-on: the Vulnesis AI Firewall for model calls, with provider keys in its vault; an egress firewall that decides each request by hostname, in a log mode or a deny mode; and, with the Package Firewall add-on, the Vulnesis Package Firewall for every installed language, which refuses known malware and exploitable versions.

How is the image verified?

The image comes from a pinned Nix flake. Belai and the Vulnesis CLI are fetched by the SHA-256 their releases publish, every package comes from one pinned nixpkgs revision, each image is built twice and ships only when both builds match, and CycloneDX and SPDX SBOMs are published. On every boot the sandbox hashes its binaries against the pins before Belai starts.