Question 1

Do you charge per developer?

Accepted Answer

No. Most of Vibgrate's work runs automatically in CI, where seats are irrelevant — charging per developer would mean paying for people who never log in. We charge per project under governance, with unlimited seats included.

Question 2

We use a monorepo with hundreds of projects. How does that work?

Accepted Answer

We detect each independently-versioned project inside the repo from its manifest or build target, and you choose which to put under governance. You're billed only for those — and each is sized first, so tiny ones cost a fraction. 200 services in one monorepo cost exactly the same as 200 services across 200 repos — you're pricing the software, not your git layout.

Question 3

I have a serverless monorepo with hundreds of functions. Will I be billed for all of them?

Accepted Answer

No. Each function is measured automatically and billed as a fraction of a project — a tiny single-purpose handler counts as a twenty-fifth (the nano tier) and a typical Lambda as a tenth (the micro tier). We total the fractions across your repositories and round down. So 247 detected projects might be just 49 billable projects. Drag the "average project size" slider in the estimator to a nano-heavy estate to see this.

Question 4

How is a project's size — and its billing fraction — decided?

Accepted Answer

By three measured signals: source-file count, source byte size, and declared dependency count. A project lands in the lowest tier whose limits it meets on any two of the three — Nano (×1/25), Micro (×⅒), Small (×⅓) or Standard (×1). It's automatic on every scan, with nothing to configure. Size is measured on source code only — lockfiles, generated files, and vendored or build directories are excluded, so a big lockfile never pushes a small project into a higher tier.

Question 5

My project grew. Will my bill jump immediately?

Accepted Answer

No. An upward reclassification keeps your current cheaper rate for the rest of the billing cycle, and the higher rate starts next cycle — flagged in advance in the dashboard as a pending upgrade. A project that shrinks gets the cheaper rate right away. Your bill never rises unexpectedly mid-month.

Question 6

Do nano, micro and small projects count for less toward my DriftScore too?

Accepted Answer

No — billing weight is not risk weight. Every project, whatever its size, is fully included in your DriftScore, the portfolio view, and every risk and compliance report. Only the billing fraction is reduced. The CTO dashboard never under-counts risk.

Question 7

What exactly is free?

Accepted Answer

Point-in-time scanning of unlimited repositories and projects, your DriftScore, the top-10 prioritised findings, and a shareable report — free forever. Up to 10 billable projects can be continuously monitored on the Free plan.

Question 8

How is the per-project price banded?

Accepted Answer

The marginal rate drops as your governed estate grows — the first billable projects cost more per unit than the five-hundredth. Banding is applied to your billable projects (after micro-project sizing), not the raw detected count. The calculator above shows the bands and itemises the math, so you can always reconcile your bill. No hidden steps.

Question 9

How does annual billing work?

Accepted Answer

Pay annually and you get two months free — you're billed for ten months of usage across the year. Switch the calculator to Monthly to compare.

Question 10

What are VM minutes, and what does overage cost?

Accepted Answer

Scheduled scans and migrations run on our cloud VMs, and the compute time they use is metered in VM minutes — scans and migrations draw from the same monthly pool. Every plan includes an allowance, even Free: 30 minutes on Free, 1,000 on Team, 5,000 on Business (Enterprise is custom). If you enable overages, minutes beyond your allowance are billed at $0.02 per minute. With overages off, scheduled scans and migrations pause once the allowance is spent — and the dashboard breaks down exactly which repositories, applications and environments used the minutes.

Question 11

What are remediation tokens, and what do they cost?

Accepted Answer

When you hand a fix to a Vibgrate remediation agent (Business plan and up), the coding model it drives consumes LLM tokens. Two ways to run cost you nothing in tokens: a local open-weight model on the Vibgrate AMI — your code never leaves the instance — or your own provider key (BYOK), where you pay your provider directly. Both are tracked for transparency but never billed by us. If you'd rather use Vibgrate's hosted model key, those platform-key tokens meter at $15 per million (premium frontier models meter at 2×). There's no bundled allowance, so platform-key tokens meter from the first token when overages are on — turn overages off, or pick a local / BYOK model, to keep remediation runs free of token charges.

Question 12

When do we need to talk to sales?

Accepted Answer

Only for Enterprise controls — SSO/SAML, on-prem or VPC deployment, custom policy and SLAs. Everything up to and including portfolio governance and the compliance audit trail is self-serve by card.

Capability	Free	Team	Business	Enterprise
Limits & cloud compute
Repositories under continuous monitoring	1	10	50	Unlimited
Scan credits / mo	5	100	500	Unlimited
MCP tokens / mo	10,000	2.5M	10M	Unlimited
Included VM minutes / mo (scans + migrations)	30	1,000	5,000	Unlimited
VM-minute overage rate (when enabled)	—	$0.02 / min	$0.02 / min	Custom
Remediation-agent tokens (platform key)	—	—	$15 / 1M	Custom
Analyse & measure
Repository, stack & dependency inventory	Included	Included	Included	Included
DriftScore + top-10 prioritised findings	Included	Included	Included	Included
Continuous monitoring & historical trends	Not included	Included	Included	Included
Living SBOM (CycloneDX / SPDX)	Not included	Included	Included	Included
Signed SBOM attestations	Not included	Not included	Included	Included
Risk & roadmap
Full risk register & EOL report	Not included	Included	Included	Included
Vulnerability prioritisation (SCA / VEX ingest)	Not included	Included	Included	Included
Upgrade roadmap & investment plan	Not included	Included	Included	Included
Govern & automate
Workflow automations (alert & route)	Not included	Included	Included	Included
Automated remediation workflows	Not included	Not included	Included	Included
Custom (build-from-scratch) workflows	Not included	Not included	Not included	Included
Merge gates & drift policies	Not included	Not included	Included	Included
Drift budgets & team accountability	Not included	Not included	Included	Included
Remediation hand-off + verification	Not included	Not included	Included	Included
Portfolio & board-level dashboards	Not included	Not included	Included	Included
Push to IDP (Cortex / Backstage) · multi-VCS	Not included	Not included	Included	Included
Audit trail & compliance export	Not included	Not included	Included	Included
Controls
SSO / SAML, on-prem, SLA	Not included	Not included	Not included	Included

Pay for what drifts.

What counts as a project

Not every project is billed the same

Nano

Micro

Small

Standard

How sizing works

Billing weight ≠ risk weight

No surprise mid-cycle rises

Automatic & measurable

Four plans. One free forever.

Free

Team

Business

Enterprise

Compare every capability

Questions, answered plainly

Every plan reports compliance posture

Get your DriftScore in minutes.