Sovereign version control.
Built for the way agents work.
Keep agent tasks, saved source revisions and review conversations together. Pillion uses its own version control system, with Git compatibility.
Work with Claude Code or Codex. Review the changes and selected conversations in Pillion. Your source and saved collaboration data stay in Europe.
Keep your Git clients. Connect your harness. Choose what you share.
Our VCS. Your Git tools.
Native version control with Git compatibility for your existing workflow.
Agent work you can review
Follow task history, compare saved checkpoints and review the result.
The conversation beside the code
Share selected agent messages with a pull request. Keep the rest private.
Sovereignty throughout
European storage for source and collaboration data, with named providers and clear processing boundaries.
Agent work
From task to a change you can review.
Follow saved checkpoints, compare revisions and read the conversation behind a pull request.
Handle expired sessions
Ready for review- 1
Task recorded
Handle expired sessions without losing the return URL.
- 2
Checkpoint 1 · Revision 1
Add the expiry check and a regression test.
- 3
Checkpoint 2 · Revision 2
Keep the return URL when the session expires.
- 4
Ready for review
Compare the saved result and inspect its checks.
Ana
Keep the original destination when a session expires.
Agent
The redirect now preserves the return URL. The regression tests cover both cases.
Check results · Revision 2
Session expiry test passes
Return URL test passes
Native version control
A source system built for agent work.
Pillion stores source history in its native VCS. Saved revisions give each proposed result a fixed identity for comparison and review.
Git compatibility lets existing clients clone, fetch and push. Your team can keep familiar tools while agents use native source operations.
Understand Pillion version control →Save a revision
Keep a fixed source result for the task.
Compare and check
Inspect the result and the checks attached to it.
Approve and publish
Apply repository rules before the shared source changes.
Your existing harness
Keep the agent you work with.
Connect Claude Code or Codex to capture supported conversations. Your harness runs the agent. Pillion saves supported context privately. You choose what to share.
See integrations and setup →Sovereignty
Your code and context. Clear boundaries.
Core source and collaboration data stay in the EU, the EEA, the UK or Switzerland. This includes backups and replicas.
Your harness, model provider and billing have separate processing arrangements. Our trust page explains these boundaries and names the providers.
Read our commitments →European data residency
Source history and saved collaboration data stay within our published European geography.
Named operators
Our trust page identifies the company and providers responsible for core storage and compute.
Control over sharing
Agent conversations stay private until you share selected events with repository collaborators.
Clear processing boundaries
Review the separate arrangements for your harness, model provider and billing.
Move to Pillion
Bring your history and your team.
Import GitHub source history, branches, tags, large files, issues, pull requests, comments, attachments and releases.
Keep using Git clients after the move. Add agent workflows as your team needs them.
Authorise the importer
Authorise access to the GitHub repositories you want to move. Revoke the token when the import finishes.
Import refs and LFS
Bring commit history, branches, tags and large files into your new Pillion repository.
Import collaboration history
Issues, pull requests, comments, attachments and releases, with authors linked or recorded.
Cut over
Point remotes at Pillion, attach runners or use ours, and keep GitHub read-only as long as you like.
Team collaboration
The tools around every change.
Bring people, agents and automated checks into the same review process.
Pull requests
Discuss changes, review code and require approvals before merging. Accept contributions from public forks.
Issues
Track bugs and ideas with Markdown discussions and image attachments that follow repository visibility.
Rulesets
Protect branches with approval requirements and status checks, at repository or organisation level.
Releases
Publish tagged versions with release notes and downloadable assets alongside your code.
Git LFS
Version large files alongside your code with Git LFS, including support for repository forks.
Workflows
Actions-shaped YAML on EU-hosted runners, or attach your own compute. Caches per repository.
Organisations and teams
Manage team permissions, work with outside collaborators and require single sign-on for your organisation.
Tokens, not passwords
Give tools and agents scoped access with fine-grained tokens, repository deploy keys and installable apps.
Room for individuals and teams.
Compare plans and allowances →Free
Free
for people and organisations
Version control and collaboration, with your own AI provider key.
- Public and private repositories
- 10 GiB source storage
- 10 GiB package storage
- SSO, teams and branch rulesets
- Unmetered attached runners
Team
€5
per person / month, excluding tax
More capacity and organisation controls, even if you run your own CI.
- 100 GiB source storage
- 100 GiB package storage
- Up to 180-day artefacts and logs
- Hosted private CI; 2,000 shared minutes
- Organisation policies, access reports and audit exports
Team + AI
€20
per person / month, excluding tax
Everything in Team, with managed AI code reviews.
- 250 GiB source storage
- 250 GiB package storage
- Up to 365-day artefacts and logs
- Shared monthly review allowance
- No provider key required; no automatic overages
Commitments you can check.
Questions about Pillion
Is Pillion built on Git?
Pillion uses its own version control system. Git compatibility lets you clone, fetch and push with existing Git clients. Native revisions keep source history separate from private agent conversations.
Can I use my existing coding agent?
Yes. Pillion captures supported conversation records from Claude Code and Codex through a local connector. The current package supports macOS and requires manual installation. Your harness continues to run your agent.
Who can see my agent conversations?
Uploaded conversations stay private to their creator. You select the saved events to share with a pull request. Current repository collaborators can read that selection. Later events stay private, including on public repositories.
Where does my data go?
Pillion stores source history and saved collaboration data within its published European geography. Your harness and model provider have separate processing terms. Pillion does not use customer content to train models.
Can I keep using Git and CI?
Yes. Use Git clients, GitHub-shaped REST endpoints and the documented Actions-shaped workflow subset. Attach your own runners or use hosted runners. See the compatibility guide for supported operations.
Can I take my work with me?
Git clone and fetch export published source history. Collaboration records use separate API access. Private tasks, checkpoints and conversations are separate records and are not included in a Git clone.
Can I self-host?
Self-hosting is not available. Pillion currently operates as a hosted service.
Join the waitlist.
Tell us what you want to build, where you are moving from, and what kind of repositories you need. We onboard in small batches and will write before yours opens.