pi pod: Self-Hosted Sandboxing for pi Coding Agents

pi pod is a self-hosted infrastructure layer designed to run pi coding agents within isolated sandboxes on a user's own server. The project aims to provide a minimal, curated tooling environment that enables software engineers to maintain ownership of their data and avoid lock-in from AI providers while gaining the necessary engineering controls for agentic workflows.

Core Capabilities of pi pod

pi pod provides a consolidated environment for the "agentic engineering" workflow. While the base pi harness is designed for simplicity and customization, pi pod adds the structural components required for organizational or professional software engineering, including:

  • Isolated Sandboxing: Running agents in a restricted environment to prevent them from impacting the host system.
  • Native Clients: Integration with local tools and interfaces.
  • RBAC Session Sharing: Role-Based Access Control for managing how sessions are shared across users or teams.
  • Surface Automation: Capabilities for automating browser and native applications.

Deployment and Ownership Models

pi pod is currently available as a self-hosted edition, allowing businesses and individuals to deploy the environment within their own data centers. This model ensures that the entire agentic environment remains under the user's control, providing higher levels of privacy and ownership. A hosted service option is planned for future release.

Technical Discussion and Community Feedback

The introduction of pi pod has sparked a technical debate regarding the security boundaries of sandboxing and the specific implementation of isolation.

Security Boundaries: Containers vs. MicroVMs

A significant point of contention among users is the definition of "isolated sandbox." Several contributors argue that standard containerization is insufficient for running untrusted code:

"Daily reminder that containers are not considered a safe security boundary, and never were. If you really need to run untrusted code, use a MicroVM."

Other users questioned whether the project differs significantly from running a harness in an LXC container or a Virtual Machine (VM) via Proxmox, suggesting that existing kernel-level tools like systemd-nspawn could provide similar functionality without the need for a new abstraction layer.

Integration and Team Standardization

Developers are interested in how pi pod can be used to standardize agent configurations across a team. For example, the creator of Epho noted the need for a standardized pi configuration on a team or project level so that multiple organization members can utilize the same private infrastructure without having to spin up individual instances on their local machines.

Alternative Approaches

Community members highlighted several alternative paths for running agents in isolated environments:

  • Custom Harnesses: Some developers are building personal alternatives to tools like Claude Code, incorporating their own MicroVM support.
  • Integrated Systems: Projects like BakedPi integrate pi with Forgejo to create a software team simulation.
  • Abstraction Layers: Tools such as Omnigent and OpenShell are being used by users who prefer sandbox abstractions over managing their own infrastructure.

Sources

Related

  • Dispatch
  • Dispatch
  • Project
  • Dispatch
  • Dispatch