pi pod runs sessions of the pi coding agent in separate containers on a Linux server you operate. A CLI starts and attaches to pods; a server handles session routing and lifecycle, with Postgres and Zitadel for storage and sign-in. The source is AGPL-3.0-only. The October 5 v0.1.14 release fixes session-proxy routing and releases a matching CLI; this is an early, actively changing project, not a tested recommendation.

  • Getting started: The self-hosting guide calls for Linux, Docker Compose, Node 22.19+, and preferably 8 GB RAM. Clone the repo, run selfhost/upgrade, create a user with selfhost/add-user, then build or install @pipod/cli and use pipod login and pipod from a project directory. One standard pod is allocated 4 GiB; smaller configurations are documented for 4 GB hosts.
  • Access and cost: The self-hosted code is available now; you supply the server and model-provider credentials, so infrastructure and model usage still cost money. The hosted service is not available yet. The repository contains iOS and Android app source, but does not publish app builds.
  • Security boundary: The author clarified on HN that sessions use separate containers within the same host VM. That is not the same boundary as a separate microVM for each task. The guide also warns that the server’s default port 8080 is exposed on all interfaces and should be kept off the public internet until HTTPS and access controls are configured.

This fits someone who already uses pi and wants remote sessions on their own machine. It is more operational machinery than simply running pi locally: a control plane, identity service, database, container service, secrets backup, and a properly sized host. No hands-on sandbox or security testing was performed for this capture.