Which systems?
Name the tools Vif must reach: GitHub, Jira, Linear, docs, internal services, databases, build systems, or custom MCP servers.
Tools and access
Tell Vif what tools the work may use.
Some work only needs GitHub. Other work needs Jira, Linear, internal docs, build systems, private APIs, or customer-specific rules. That is when the setup matters.
Which setup fits?
| What the work needs | Recommended setup |
|---|---|
| Standard GitHub issue-to-PR work | Managed hosted runtime. |
| Private tools, internal docs, Jira, Linear, or custom connectors | Dedicated runtime or custom deployment. |
| Customer-specific rules for code, secrets, approvals, or allowed tools | Dedicated runtime or custom deployment. |
| Strict compliance, SSO, audit logs, or private network placement | Custom deployment. |
What to tell us
What is allowed?
Describe what the agent is allowed to read, change, run, or call. Vif can translate that into runtime and workflow boundaries.
Which data boundary?
Say whether the work can run in Vif Cloud, needs a dedicated Vif runtime, or must run in your own cloud.
Start with the systems the work needs.
Answer the plain-language questions in the pricing wizard and Vif will recommend the correct runtime boundary.