Pricing

Pricing based on repository and organization scope, not developer seats.

Start with a trial, run a guided pilot, or scope an annual plan around the repositories where missing ownership, stale suppressions, and unverifiable exceptions create real operating risk.

14-day enterprise trial

Find the debt before another audit cycle preserves it.

Use a focused repo set to prove whether the first snapshots reveal owner gaps, stale suppressions, policy drift, and evidence worth operationalizing.

14-day trial

$0

time-boxed evaluation

Send the first real snapshots and find out where ownership, suppression review, and policy evidence break first.

  • Up to 10 repos
  • 3 API tokens
  • 100 snapshots per month
  • Self-guided suppression debt review

Guided pilot

$5k

30 days

Leave with scoped production repos, snapshots uploaded, orphaned findings identified, and one leadership evidence readout.

  • One-time Stripe checkout
  • Repo scope planning
  • Scanner snapshot setup
  • Suppression and owner-gap readout

Team

$18k

per year

For a focused platform or product engineering group standardizing ownership and exception governance.

  • Up to 50 repos
  • OIDC/RBAC
  • Slack/Jira accountability routing
  • Signed evidence exports

Growth

$36k

per year

For multiple teams expanding continuous governance evidence across production Go repositories.

  • Up to 200 repos
  • Policy pack reviews
  • OIDC group role sync
  • Customer diligence exports

Enterprise

$75k+

annual

For broader organizations and self-hosted requirements.

  • Custom deployment model
  • Guided governance rollout
  • Security review support
  • Enterprise scope planning

Guided pilot

A 30-day pilot should end with a rollout decision, not a vague demo recap.

The pilot is designed to prove whether Faultline turns real source-free snapshots into evidence your leaders and reviewers can use to defend accepted risk.

By day 30

You know whether this belongs in production.

If the first focused repo set does not reveal useful governance evidence, you should not expand. If it does, rollout has a concrete operating model for ownership, suppression review, and evidence export.

5-20 production Go repos scoped
First source-free snapshots uploaded
Top owner gaps and risky packages identified
Stale suppressions reviewed with owners
Policy drift reviewed against active packs
Weekly digest recipients configured
One signed evidence export generated
Rollout or no-rollout decision documented

Find the continuity gaps your current tooling cannot prove away.

You may have findings, scanners, and tickets. Under scrutiny, that still may not prove governance continuity.