SELF-HOSTING
Your brain, your hardware.
Run the Pipo workflow engine on infrastructure you control. Bring your own model providers, storage, network boundary, and sidecars.
The same product model, owned by you.
DaemonRun the persistent brain, workflow engine, memory, authority rules, and dashboard on a computer, Linux host, VPS, or container.
SidecarsConnect your connected computer and other computers with scoped JWT-enrolled sidecars for local control.
ProvidersConfigure the AI providers and fallback routing your organization is approved to use.
StorageChoose where memory, logs, workflow versions, and workspace data live.
A minimal production baseline.
docker-compose.yml
services: pipo: image: pipo/engine:latest ports: [3000:3000] volumes: [pipo-data:/var/lib/pipo] environment: PIPO_AUTHORITY_MODE: review
Self-hosting moves responsibility to your team.
Do not expose the dashboard without an authenticated boundary.
Review the authority and disclaimer docs, keep backups, and start with side effects disabled. A persistent agent with terminal and browser access should be treated like a trusted operator.
Review the authority and disclaimer docs, keep backups, and start with side effects disabled. A persistent agent with terminal and browser access should be treated like a trusted operator.
THE NEXT REPEAT IS ALREADY THERE
Make it visible.
Connect the context. Keep the boundary. Let Pipo handle the repetition.
Start with Pipo ↗