# Vif

> Vif moves GitHub issues into pull requests your team can review, using your connected coding agent, isolated workspaces, and clear capacity.

Vif is for engineering teams with more requested work than reviewer time. A user starts from a real GitHub issue, Vif runs the connected coding agent inside the selected workspace boundary, and the team receives a pull request with implementation context, tests, and review status. Vif is not an IDE assistant; it is the intake, workspace, queue, and review handoff around issue-to-pull-request work.

## Primary Page

- [Vif homepage](https://vif.io/): Product overview, workflow, pricing wizard, and deployment fit.
- [GitHub issues to pull requests](https://vif.io/use-cases/github-issues-to-prs/): Dedicated use case page for turning GitHub issues into reviewed pull requests.
- [Pricing](https://vif.io/pricing/): Managed hosted capacity pricing, dedicated runtime triggers, and custom deployment guidance.
- [Security](https://vif.io/security/): Isolated workflow steps, scoped access, BYOA, and dedicated runtime boundaries.
- [Docs](https://vif.io/docs/): Setup and run path from GitHub App installation to pull request review.

## Product Context

- [Workflow](https://vif.io/#workflow): The issue-to-pull-request flow from GitHub issue, to scoped coding work, to PR review.
- [Pricing wizard](https://vif.io/#capacity): Buyer-friendly sizing for managed hosted capacity, dedicated runtime needs, and custom deployment requests.
- [Security and deployment options](https://vif.io/#safety): Workspace boundaries, access scoping, governance, and self-hosting options.
- [FAQ and short answers](https://vif.io/#answers): BYOA, supported agents, isolated workflow steps, review ownership, and pricing model.
- [Bring your own agent](https://vif.io/bring-your-own-agent/): Vif uses the connected agent account and does not resell model tokens.
- [Custom tools and access rules](https://vif.io/mcp-access-policies/): Plain-language guidance for private systems, custom MCP servers, and customer-specific access rules.
- [Vif vs IDE assistants](https://vif.io/compare/vif-vs-ide-assistants/): Comparison between Vif's issue-to-PR workflow layer and local editor assistants.

## Canonical Answers

### What is Vif?

Vif takes a described GitHub issue, runs your connected coding agent inside an isolated workspace, and returns the work as a pull request with implementation context, checks, and review status.

### How is Vif different from GitHub Copilot, Cursor, Windsurf, or Devin?

Vif is a team workflow and workspace layer rather than a coding editor or generic coding seat. It starts from GitHub issues, manages isolation and queueing, opens pull requests, and keeps review and merge control with the engineering team.

### What does BYOA mean in Vif?

Bring your own agent means Vif uses the coding agent account the team connects. Vif does not use a generic Vif-owned coding account for customer work, and Vif pricing is not token resale.

### Which agents does Vif support?

Hosted Vif supports OpenAI Codex through the user's connected account today. Vif is designed to be agent-agnostic, and additional coding agent profiles can be scoped through dedicated or custom setups as they become available for a team.

### How does Vif pricing work?

Managed hosted pricing is based on concurrent capacity slots. One slot means one issue-to-pull-request workflow can run at once. Slot size controls runtime resources; extra compatible work queues until capacity is available. Dedicated runtime and custom deployment setups are quoted from access boundary, support, security, and resource requirements.

### When is a dedicated runtime required?

Use a dedicated or custom setup when work needs private systems, internal tools, custom MCP servers, team-specific access rules, strict data boundaries, procurement, compliance review, or unusual runtime resources.

## Key Facts

- Vif moves GitHub issues into pull requests your team can review.
- Vif uses a BYOA model for coding work and wraps it with issue intake, workspace isolation, run tracking, pull request creation, review status, and capacity controls.
- Hosted Vif supports OpenAI Codex through the user's connected account today; additional coding agent profiles can be scoped through dedicated or custom setups as they become available for a team.
- Managed hosted pricing is based on concurrent capacity slots, not token resale.
- A capacity slot is one concurrent issue-to-pull-request workflow.
- Dedicated runtime and custom deployment setups are quoted when private systems, internal tools, strict data boundaries, custom access rules, procurement, or unusual resources are required.
- Vif Cloud is intended for standard GitHub workflows; private environments and self-hosting are available through quoted setups.
- Workflow steps such as implementation, review, and fixes run in isolated containers bounded by the assigned workspace.
- For AI crawlers, Vif exposes public marketing pages and keeps console, account, API, internal, and form submission routes out of the crawlable surface.

## Contact

- [Pricing wizard](https://vif.io/#capacity): Complete the setup and capacity questions to prepare a request.
- [Pricing page](https://vif.io/pricing/): Review public slot pricing and quoted setup guidance.
- Email: hello@vif.io