Introduction
What Pistis is, and where to start.
Pistis is the open-source software factory: self-hostable cloud agents for teams. Anyone on the team hands off a coding task, from the browser, Slack, the terminal, the API or a schedule. An agent works on it in a disposable sandbox on your servers, and the change comes back as a pull request.
Agents on a laptop help one person and stop when they log off; a vendor’s cloud agent needs your code and keys on someone else’s machines. Pistis runs on your servers, with any model, so the work carries on for the whole team and your keys stay on your servers.
Try it
Run Pistis on your laptop and hand an agent its first task.
Run it for a team
Sign-in, GitHub and HTTPS on one server.
How it works
Why a crash loses no work and your keys stay out of reach.
How a task goes
- Describe it. Pick an agent and a repository, and type the task.
- Watch it work. Each command appears as a step with its output, as it runs. You can close the tab; the work carries on.
- Approve what's risky. Steps you marked as risky wait for a yes, in the browser, on your phone or in Slack. When you trust a task, send it in Auto mode (if your admin allows it) and it goes ahead on its own; every step is still recorded as approved by you.
- Review the pull request. The agent opens a pull request on GitHub or a merge request on GitLab, naming who asked.
Why teams use it
The agent's memory, your keys and the record of what ran stay on your server. So the machine that runs the agent's commands can crash, pause or be replaced at any moment.
- Nothing is lost. A crash in the middle of a task loses no work. A risky step, like a deploy or a migration, is never quietly run twice. The agent asks you.
- None of Pistis's keys in the sandbox. It gets a copy of the repository and only the network you allow. Git, API and MCP credentials stay on your server, so a command in the sandbox can't read them.
- Every change is reviewed. Work arrives as a pull request and goes through your checks and your review like anyone else's.
- One change, every repository. A campaign runs the same task across many repositories, each with its own pull request.
- Idle costs nothing. Idle sandboxes are paused, then deleted.
- Any model, any sandbox. Your model provider, on Docker, Kubernetes, a cloud sandbox provider or your own machines.
Pistis is open source under Apache-2.0. Every security feature is in the open-source version.