One dashboard your
whole team works from
Scans pile up in terminals; decisions happen in meetings. Vibgrate Cloud turns CLI scans into the shared view — DriftScore trends, dependency and vulnerability registers, and audit-ready reports — so a tech lead, a security engineer and a CTO all argue from the same numbers.
The demo opens with example data — no sign-in, no card. Unlimited seats on every plan.
How it works
Vibgrate Cloud is the team-facing layer on top of the Vibgrate CLI. You push scan results with vg push, and Vibgrate Cloud handles everything else — reports, trends, modernization tracking, and sharing.
Run the Vibgrate CLI locally or in CI to generate a drift report.
Upload results with `vg push`. Your workspace is provisioned automatically.
Open Vibgrate Cloud to view reports, triage issues, and track upgrade work.
Built for teams, priced for projects
Seats are unlimited on every plan — you pay per project under governance, not per person. Invite the whole team; give each role exactly the access it needs.
Owner, admin, member and viewer roles, plus function roles like security engineer and tech lead. Scoped users see only their assigned business units, applications and repos.
Group repositories by the org structure you already have, and read drift by team, product line or environment.
Set the drift a project may carry, watch consumption, and catch breaches before they become incidents.
Separation of duties for state-changing work: a queue, delegated approvers, and a full decision history.
Every scan, change and approval logged with who, what and when — evidence you can hand to an auditor.
Build shareable reports, schedule scans, and wire findings into the tools your team already uses.
Each feature below shows the plan that unlocks it — approvals and audit tooling arrive on the higher plans.
Drift Reports
OverviewYour whole codebase health, at a glance
Every scan you push becomes a comprehensive drift report. See your estate DriftScore, how it breaks down across runtime, framework, dependency and EOL risk, and exactly what changed since the last scan.
- Composite DriftScore broken down by runtime, framework, dependency and EOL risk
- 30-day trend so you see drift improving or regressing after every push
- Per-project scores inside monorepos
- Code-quality signals — complexity, dead code and nesting — alongside drift
- Shareable, exportable reports (PDF / JSON) for stakeholders and audits
Scans & History
ScansEvery scan, tracked over time
The Scans hub keeps a complete history of every scan — pushed from the CLI or run on a schedule — so you can watch your DriftScore move, catch regressions right after a release, and prove coverage across the estate.
- Full scan history with DriftScore over any 7d / 30d / 90d window
- Regression detection immediately after releases
- Scan status, volume and duration at a glance
- Scheduled and CI-pushed scans in one timeline
- Per-repository scan coverage tracking
Repository Portfolio
EstateEvery repo, ranked by health
Connect GitHub, GitLab, Bitbucket or Azure DevOps and Vibgrate scores and ranks every repository by modernization risk — so you always know which repos need attention first.
- Every connected repo scored and ranked by modernization risk
- Health distribution across the entire estate
- Drift and CVE status per repository
- Works with GitHub, GitLab, Bitbucket and Azure DevOps
- Filter and sort by environment, business unit or score
Dependency Intelligence
EstateEvery package, version and upgrade path
A live register of every dependency across all repositories — versions, licenses, duplicates and known vulnerabilities — with an upgrade backlog ranked by how much of your estate each fix improves.
- Upgrade backlog ranked by how many repos each fix touches
- Every dependency, version and license across all repos
- Phantom, duplicated and deprecated packages surfaced automatically
- Known CVEs mapped to affected and fixed-in versions
- Supplier and license register for governance
Security & Vulnerabilities
SecurityKnow your exposure before it becomes a breach
Surface dependencies with known CVEs, end-of-life runtimes and insecure configurations. Every finding is enriched with severity, fixed-in version and OWASP category so your team can act fast.
- Known CVEs with severity, CVSS and fixed-in guidance
- EOL runtimes and frameworks flagged before they bite
- OWASP Top 10 category mapping across the estate
- Risk distribution and security posture over time
- Secret-scanning and lockfile hygiene checks
Architecture & Layers
EstateUnderstand structure, not just dependencies
Vibgrate detects your architecture archetype and maps the codebase into layers — frontend, backend, data, infra — so you can see where drift concentrates and understand the blast radius of an upgrade.
- Automatic archetype detection — monorepo, microservices, modular monolith
- Codebase mapped into layers: frontend, backend, data, infra
- Layer-level drift and blast-radius for upgrades
- Cross-layer dependency and service-coupling risk
- Project-size classification across the estate
Application Portfolio
EstateGroup repos into the apps your business runs
Roll repositories up into the applications and business units your organization actually runs, so drift and risk are reported in terms leadership understands — by product, team and environment.
- Group repositories into the applications your business runs
- Roll drift and risk up to application and business-unit level
- Technology mix across your whole portfolio
- Discovery from scans, CMDB and manual mapping
- Environment-aware views (prod, staging, dev)
Integrations & Webhooks
IntegrationsDrift signals in the tools you already use
Push Vibgrate events into Slack, Jira, Linear, PagerDuty or any webhook receiver. Fire on new scans, threshold breaches, new CVEs and project updates — with signed payloads and a live delivery log.
- Native Slack, Jira, Linear and PagerDuty connectors
- Fire on scan pushed, threshold breached, CVE detected or project updated
- Signed (HMAC) JSON payloads with full scan context
- Automatic retries with exponential backoff
- Live delivery log for debugging
AI Copilot
AIAsk questions about your estate in plain language
The built-in Copilot turns your scan data into answers. Ask what is driving your DriftScore, which repos need attention, or what an upgrade will impact — and connect Claude Code over MCP to act on it.
- Ask questions about your estate in plain language
- Explains what is driving your DriftScore and what changed
- Ranks what to fix first, with reasoning
- Summarises the difference between any two scans
- MCP token for Claude Code and other AI tools
Modernization Projects
ActTurn upgrade debt into tracked, completable work
Create modernization projects from any set of drift findings, assign owners, set targets and watch progress update from real scan results — perfect for coordinating large dependency or framework migrations.
- Turn scan findings into tracked, ownable projects
- Auto-populate tasks from the highest-impact upgrades
- Progress tied to real scan results, not manual updates
- Effort-vs-value scoring to sequence the work
- Roadmap, timeline and ROI views
SBOM Hub
GovernGenerate, track and attest software bills of materials
Produce CycloneDX and SPDX SBOMs from every scan, track component inventory and coverage, and attach vulnerabilities, licenses and signed attestations — then diff SBOMs between releases.
- Generate CycloneDX / SPDX SBOMs from every scan
- Track component inventory and coverage across repos
- Vulnerabilities and licenses mapped to components
- Build provenance and signed attestations
- Diff SBOMs between releases
Policies & Governance
GovernDefine the rules, prove compliance
Codify your engineering standards as policies and enforce them across every repository. Compliance is scored per policy estate-wide, with violations grouped by category and exceptions tracked with owners and expiry.
- Define policies once and enforce them across every repo
- Compliance scored per policy, estate-wide
- Violations grouped by category with drill-down
- Exceptions with owners, expiry and audit log
- Coverage heatmap across teams and services
Approvals & Sign-off
GovernRequire sign-off before risky changes ship
Add human approval gates in front of high-risk changes. Route requests by risk and scope, track them against SLAs, delegate coverage, and keep a complete approval history for audit.
- Require human sign-off before high-risk changes ship
- Approval queues with SLAs and escalation
- Policy-driven routing by risk and scope
- Delegation and coverage so nothing blocks
- Complete approval history for audit
Which plan do I need?
Each feature above shows the minimum plan that unlocks it. Higher plans include everything below them.
See your codebase in Vibgrate Cloud
Run a scan with the CLI, push results, and your reports are live in under a minute.