Your agent account
Vif uses the coding agent account your team connects. Hosted Vif supports OpenAI Codex through the user's connected account today; Vif is designed to stay agent-agnostic.
Security
Keep agent work where your team can see it.
Vif does not merge code for you. It gives each requested change a bounded place to run, then brings the result back as a pull request your engineers can review, change, approve, or close.
What Vif controls
Isolated runs
Implementation, review, and follow-up steps run in isolated containers. A workflow can share issue and PR context without turning every step into the same shared environment.
Tool boundaries
Tools, secrets, and MCP access are tied to the runtime boundary. Dedicated setups are the right path when those rules must be specific to one customer.
When the hosted runtime is enough
The hosted runtime is for standard GitHub workflows where Vif only needs repository access, the connected agent account, and a normal pull request review loop.
Good hosted fit
- Public or normal private GitHub repositories.
- No internal network access required during the run.
- No customer-specific MCP rules or private tool boundary.
Use a quoted setup instead
- Private systems or internal documentation must be reachable.
- Custom MCP servers, tool rules, or secret boundaries are required.
- Procurement, audit logs, SSO, or compliance review are part of rollout.
When to use a dedicated setup
A dedicated runtime lets Vif place workflows behind a boundary that matches one customer. Self-hosting is available when your infrastructure team needs the runtime in your own cloud or private network.
Need private tools or stricter access rules?
Use the pricing wizard to describe the systems Vif must reach and the boundary your team expects.