Pricing that scales with your team.
Personal use is free. Pay when your team needs shared resources, audit, or compliance.
Personal
For solo engineers who want control running their own agents.
Free
Get started- Unlimited sessions on your own machine
- Personal scope (no team sharing)
- Inbox on web + mobile
- Bring your own model keys
- Open-source daemon, reviewable
Pro
Early accessFor 5–50 person teams shipping agent-driven changes weekly.
Contact Us
Contact for early access- Everything in Personal, plus:
- Team Context, audit ledger, team inbox routing
- Team Git Resource exports under .viewport/
- Approval gates with per-team policy
- Plan reviews routed by team membership
- Org-level self-hosted runners for team-scoped workflows
Enterprise
Early accessFor 50-200+ person pilots that need self-host, audit, and compliance.
Custom
Contact for early access- Everything in Pro, plus:
- Configurable pilot seat limits and rollout support
- Self-hosted relay (your infra), documented HTTP control-plane API
- SSO
- Customer-controlled keys for Team Context
- SOC 2 Type II readiness support (certification not yet complete)
- Audit log + receipt export
- Role-based access control + per-resource ACL
- SLA and dedicated support
What you get at each tier.
| Feature | Personal | Pro | Enterprise |
|---|---|---|---|
| Sessions across your machines | |||
| Inbox on web + mobile | |||
| Open-source runner | |||
| Bring your own model keys | |||
| Team-scoped workflows and artifacts | |||
| Team Git Resource exports | |||
| Org-level self-hosted runners | |||
| Configurable pilot seat limits | |||
| Plan reviews + approval gates | |||
| Team Context | |||
| SSO | |||
| Self-hosted relay | |||
| Documented HTTP control-plane API | |||
| Customer-controlled context keys | |||
| SOC 2 Type II readiness support (certification not yet complete) | |||
| Audit log + receipt export | |||
| Dedicated support |
The things teams ask before signing up.
- What does the daemon actually see?
- Everything you'd expect a process running in your shell to see: working directory, git metadata, agent stdout/stderr, tool calls. It's open source at github.com/ViewportAI/viewport. Read every line that touches your machine.
- What about my code? Does it leave my machine?
- No. Sessions announce metadata (directory, repo, branch, status, summary) to the relay. Transcripts, tool output, and file contents stay on your machine and are fetched on demand. We're control-plane-blind for context bodies.
- Can I self-host?
- Daemon and relay, yes, today. The daemon is open source and the relay ships as a Docker image. The control plane is hosted by us, with a documented HTTP API (generated from our published OpenAPI spec) for teams that build against it. If full control-plane self-host is a hard requirement, get in touch and we'll talk through what's possible.
- Can the open-source runner bypass hosted policy?
- No. The runner can execute work, but hosted Viewport decides whether that work is allowed. Claims, leases, credentials, side effects, billing admission, and receipts are issued and checked by the server. Self-hosted control planes can enforce their own rules.
- Which agents work?
- Claude Code and Codex CLI run out of the box. The daemon is open source, and the runner boundary is provider-agnostic: Cursor, internal agents, custom command agents, and managed sandboxes can be wired through the same workflow contract.
- Why a team Git Resource?
- Viewport is the control-plane source of truth, but teams still need reviewable evidence in Git. A Team Resource exports .viewport/ receipts for workflow definitions, routes, review packets, artifacts, and context decisions, so approvals can be audited alongside code.
- What happens to my data if I cancel?
- Inbox decisions stay yours. Export to JSON anytime. Encrypted context never leaves your edge. The daemon keeps running locally, so Viewport going dark does not break your machine.