A3S Box
  • English

      • A3S Box guides

      A3S Box is a local OCI workload runtime, not a hosted Sandbox service or a remote control plane. The CLI, native SDKs, and Agent Skill ultimately operate the same runtime installed on the current machine.

      The default execution path uses a MicroVM with a dedicated Linux guest kernel. On a certified Linux host, a shared-kernel Sandbox is an explicit choice; Box never falls back between the two isolation classes.

      Start here

      GuideUse it to
      InstallationInstall a verified release on Linux, macOS, or Windows.
      Quick startInspect the host, run a MicroVM, and manage a first service.
      ArchitectureUnderstand the isolation resolver and local runtime boundary.
      Images and buildsPull, build, tag, save, load, and prune OCI images.
      Storage and snapshotsUse bind mounts, volumes, tmpfs, commits, and snapshots.
      Networking and ComposeConfigure TSI, named networks, published ports, and Compose.
      Windows WHPXEnable WHPX and work within the Windows capability boundary.
      Agent SkillLet a coding agent use Box with the right lifecycle rules.

      This order gets a minimal workload running before explaining the runtime boundary, then moves into durable image, data, and network resources. For one command, go directly to the CLI reference. If the language is already decided, start from the SDK overview.

      Choose the execution boundary

      ContractDefault MicroVMExplicit Sandbox
      Kernel boundaryDedicated guest Linux kernelShared host Linux kernel
      Isolation classhardware-vmshared-kernel
      Intended workloadUntrusted workloads and stronger tenant boundariesTrusted automation and controlled tools
      HostLinux/KVM, Apple Silicon/HVF, Windows/WHPXCertified Linux host
      Automatic fallbackNeverNever
      IMPORTANT

      A shared-kernel Sandbox does not protect against a host-kernel exploit, a hostile host administrator, hardware side channels, or data deliberately exposed through a bind mount. Use the default MicroVM when those risks matter.

      Choose how to use Box

      EntryBest forStart with
      CLIInteractive runs, diagnosis, and opsQuick start
      Native SDKsApplications, agent workers, and CI/CDRust, Go, Python, or TypeScript
      Agent SkillCoding agents that orchestrate local BoxInstall the Skill and reload the agent

      All three entries share one execution manager, image store, volumes, networks, snapshots, logs, and generation fences. None creates a second local state model.