Dedicated runtime
Use this when work needs private tools, internal docs, Jira or Linear, custom tool connectors, customer-specific access rules, or private network access.
Vif does not sell model tokens. Your connected agent account handles model usage. Vif pricing covers where the work runs, how many runs can happen at once, and the handoff back to GitHub.
Hosted capacity is for GitHub issue-to-pull-request work that does not need private systems or customer-specific tool rules. One slot means one workflow can run at the same time. Extra compatible work waits in the queue until capacity is available.
| Slot | Good fit | Monthly price |
|---|---|---|
| Small | Small fixes, copy changes, low-risk code edits, and simple tests. | $299 per slot |
| Medium | Everyday application work, typical test runs, and normal review cycles. | $699 per slot |
| Large | Bigger repositories, heavier builds, or workflows that need more headroom. | $1,499 per slot |
| Xlarge | Very large test suites, unusual builds, or workflows that need much more headroom. | $2,999 per slot |
Use this when work needs private tools, internal docs, Jira or Linear, custom tool connectors, customer-specific access rules, or private network access.
Use this path for SSO, audit logs, procurement, compliance review, strict data boundaries, self-hosting, or support requirements.
Use this when the slot sizes do not match your resource needs, such as very large repositories, GPU builds, or unusual storage needs.
Buy the number of slots your reviewers can realistically handle. More slots create more PRs, not more reviewer time.
Match slot size to build and test needs. Increase size only when the workflow needs more CPU, memory, storage, or time.
If a workflow needs private tools or customer-specific rules, treat the runtime boundary as the pricing driver.
Answer a few plain-language questions and Vif will recommend hosted capacity, a dedicated runtime, or a custom deployment.