Priced by service graph size, not headcount.

A service is any independently deployable unit that Buildpathio scans — a microservice, a serverless function, a backend application. If it has its own repo or deployment unit, it counts as one service. Shared libraries and internal packages do not count toward your service limit.

No. Buildpathio runs as a parallel GitHub check — it does not block your test suite. The graph scan typically completes in under 2 minutes for a 50-service monorepo. For large repos (100+ services), results appear asynchronously and a preliminary score is available within 90 seconds.

Yes. Buildpathio can ingest Backstage service catalogs, PagerDuty service definitions, and custom YAML manifests. Imported data seeds the initial graph; the live scanner then validates and extends it with actual dependency data.

Buildpathio reads your code to build the dependency graph but does not store source code. Only the graph structure (service names, dependency edges, API contract shapes) and risk scores are retained. All data is encrypted at rest and in transit. Enterprise customers can opt for private graph deployment in their own VPC.

Buildpathio will notify you when you're approaching your limit and prompt you to upgrade. We don't cut off scanning mid-build — you'll have 7 days to upgrade before new services are excluded from the graph.

Yes. Annual plans are available on Team and Enterprise tiers. Annual billing saves 20% and includes a single invoice for your finance team. Contact [email protected] for a quote or PO-based billing.