- Which guide should I start with?
- How Vörr works, then Set up your organization. Everything after those two assumes onboarding is complete and at least one repository and cloud account are connected.
- Does every person on my team need to complete onboarding?
- No. Onboarding is organization-wide. Once one administrator completes it, other members enter the configured product directly.
- What is the difference between a connected account and a scanned account?
- Connecting an account only validates the credentials. Vörr does not scan automatically — you start the scan, and only a completed scan produces the resource map an answer can rely on.
- Vörr says no resources were found. Does that mean there are none?
- Only if the relevant area was scanned successfully. Vörr separates a scanned-and-empty result from a resource type it does not index and from a scan that was incomplete because of access, failure or throttling. Check the scan status before treating a zero as proof.
- Does Vörr see my uncommitted code?
- No. Vörr indexes committed repository code. Local, uncommitted work on your machine is not included.
- What happens when two connected tools disagree?
- Vörr queries the relevant sources and reports their results separately, keeping each result's source and match quality. It does not average conflicting values, and one failing source does not erase successful results from the others.
- How long are conversations kept?
- Unsaved conversations expire after seven days. Save a conversation when you need to retain it.
- Does the MCP connector give my AI assistant my cloud credentials?
- No. The authorization is tied to your user and organization and lets the assistant retrieve facts. It does not expose Vörr's stored cloud, Git or observability credentials.
- Workspace
- A logical team or ownership group. Workspaces scope repositories and connections so Vörr knows which team owns a part of the system.
- Environment
- A deployment target such as Production, Staging or Development, each marked production or non-production so Vörr can interpret deployment mappings and production impact.
- Service map
- An explicit mapping between the different names a service has in Vörr, Datadog, Jenkins and other tools. Without it, Vörr can attempt a name-based match but reports the result as inferred.
- Provenance
- The source of each fact in an answer, together with how the relevant service was matched — explicit, inferred or unmapped.
- Blast radius
- The upstream dependencies and downstream systems that could be affected if a resource fails or changes, bounded by the connected accounts and the latest successful scan.