Verity
Self-hosted fleet of coding agents

Run your agent fleet from your phone.

Claude Code and Codex behind a credential broker, plus open-source models through OpenCode. All on your own server, each session in its own sandbox and worktree, with your history on your server.

Early access details
Parallel coding-agent sessions running on iPad and iPhone

Brokered Claude and Codex credentials stay outside

Claude and Codex tokens, signing keys, and infrastructure access stay brokered outside the sandbox.

Parallel without collisions

Every session gets its own branch and clean worktree.

Your infrastructure. Isolated execution.

Agents run in project sandboxes with the assigned workspace mounted for development.

Built for real development

Agent speed. Professional safeguards.

Verity keeps the workflow you already trust — branches, CI, review, and secrets — while your agents do the work.

01

Review and ship safely.

Every agent branch passes secret scanning and an isolated code review. Follow PR and CI state in the thread, then merge when the required checks are complete.

Gitleaks secret scan Isolated code review PR + CI gates
02

Run the fleet from anywhere.

Start several agents on the same repository from your phone. Isolated worktrees keep their branches clean and their changes apart; the attention queue shows which session needs you.

Worktrees Attention queue Voice input
03

Use the best model. Stay ahead of limits.

Move between Claude Code and Codex — or connect open-source models through OpenCode. Verity keeps your history and paid-plan usage in view before a limit interrupts the work.

Claude + Codex Open-source via OpenCode Subscription usage Google Drive import File browser
Secure by design · Supply-chain protection

Keep Claude and Codex credentials outside agent runtimes.

Isolated project containers and external credential boundaries reduce the blast radius of software supply-chain attacks. Claude and Codex provider requests cross a brokered gateway; signing and infrastructure actions are brokered outside the project runtime. OpenCode is supported separately and is not covered by this credential-isolation claim. Run Verity on a Linux workstation, dedicated server, or private cloud; the self-hosted server currently requires an x86_64/amd64 Linux host, and ARM64, macOS, and Windows hosts are not supported.

On brokered Claude and Codex paths, a compromised dependency may reach the sandbox — but it finds no reusable provider credential.
✓ Claude and Codex tokens stay behind the broker
✓ Commit signing key stays outside
✓ Git push and infrastructure access are brokered
✓ Secret-manager and database credentials stay server-side
Scope

What Verity is not.

Not an editor

Verity does not replace your IDE. There is no completion and no inline edit loop.

Not a prototype builder

Agents work on your existing repositories and your existing Git workflow, not on generated starter applications.

Not a hosted service

Verity runs on your own host. A local installation does not require a paid service from us.

Put your agent fleet under control.

Verity is rolling out to early users in waves. Public signup is not open yet.