Pier Cloud
For using Pier across machines, with a team, or inside a company. Looking for design partners.
FAQ
+What is Pier Cloud?
An optional layer on top of Pier for running daemons across machines, syncing config between them, and using Pier with a team or company. Think shared runners, permissions, audit, managed daemons, and org controls.
+Can Pier Cloud be self-hosted?
Yes. The stack is designed for source-available self-hosting: app, daemon, CLI, protocols, and the Cloud control plane. Managed Cloud is the optional paid layer for people who don't want to host it themselves.
+Self-hosted or managed?
Both. The control plane will live in the Pier monorepo so you can host it yourself. Managed is for people and teams who don't want to.
+Does my code go through Pier?
No. Daemons run on your machines and talk to agent providers directly. Cloud handles registration, config sync, permissions, and orchestration. Code and model traffic stay on your machines.
+When will it be available?
Early access for design partners now. No public date. The app and daemon come first.
+How does pricing work?
Not set yet. Design partners help shape it.