Questions before you buy or adopt Dulvarn.
Dulvarn Core is the engine. MCP/CLI is the main workflow. Dulvarn Tools sells audits and kits that lead into both.
Get Release Risk AuditFAQ
Product and workflow
Is Dulvarn an AI dashboard?
No. Dulvarn is a release risk engine that analyzes repository changes, test impact, and CI signals. The portal is a control plane for license, tokens, and report history — not a heavy analytics dashboard.
Does AI make the final release decision?
No. Dulvarn produces a deterministic GO / CONDITIONAL GO / NO-GO recommendation from structured signals. Your team keeps the final release decision and audit trail.
Can it run locally?
Yes. Use the Dulvarn CLI (`dulvarn analyze --repo .`) or MCP server (`dulvarn mcp serve`) from your machine or CI without opening a dashboard first.
Does it support GitHub?
Yes. GitHub is the primary supported provider today for connected repositories and PR/MR workflows.
Are GitLab and Bitbucket planned?
Yes. GitLab, Bitbucket, and Azure DevOps connectors are on the roadmap. You can still run local analysis via CLI and MCP on any Git repository today.
Can I buy an audit without using the SaaS?
Yes. Release Risk Audit and QA Release Risk Kit are standalone offers on Dulvarn Tools. Many teams start with a manual audit or kit, then adopt Dulvarn Core/MCP when they are ready to automate.
CLI & MCP
Run Dulvarn where your team ships code.
Dulvarn also runs directly inside your workflow through CLI and MCP for IDEs like Cursor and Windsurf.
dulvarn analyze --repo .
dulvarn mcp serve
Still deciding? Review a sample report or book a fixed-scope audit.