DriftFence Workflow Firewall pricing
Pricing

Start with one protected workflow.

DriftFence is priced around private repos and protected workflows. Choose a direct team plan when the first workflow is obvious, or use a paid pilot when you want founder-led setup and shared success criteria.

Unlimited reviewers Workflow owners can review reports without seat math.
Standard CI included Always-on merge gating stays part of the plan.
Workflow-first rollout Start with one risky workflow and expand deliberately.
Fit review first Bring one workflow and get a clear starting path.
Check workflow fit See measured proof

Best fit today: Node.js, TypeScript, GitHub, and a few critical workflows that are genuinely expensive to change silently.

Which path fits you?

The right commercial path depends less on team size than on whether you already know the first workflow and how much help you want applying DriftFence to it.

Start with Team when

You already know the first risky workflow.

You know the repo, the owners, and the CI slice you trust. What you want is a clean annual starting point, not a discovery project.

Start with Pilot when

You want hands-on rollout help.

The workflow matters, but the current test surface, ownership, or rollout sequence still needs shaping with you.

Not the best fit yet

The workflow or CI slice is still undefined.

DriftFence fits best when one or two workflows already stand out as costly to change silently and the repo has a stable CI slice to build on.

Launch plans

The public price anchor is for the first private workflow rollout. Use a pilot when you want DriftFence applied with you; use the annual team plan when you already know the risky path and want to move faster.

Public evaluation

Free

$0 Use the public results, docs, and non-production evaluation path.

Best when you want to understand the product loop, inspect the public evidence, or evaluate the workflow shape before a private rollout. This path is source-available, not an unpaid production license.

  • Public docs and results pages
  • Local CLI and GitHub Action for evaluation
  • Implementation questions answered by email
  • No support or rollout commitment
  • No private production-use grant
Paid pilot

High-touch first workflow

From $15,000 Six weeks, one private repo, up to three workflows.

Best when the workflow matters, the team wants help choosing the first scope, and you want shared success criteria before a broader annual rollout.

  • Founder-led onboarding and weekly working sessions
  • Up to 3 protected workflows in 1 private repo
  • Email-first support, plus shared Slack when active rollout work benefits from it
  • 100% credit toward year-one annual pricing on conversion
Team annual

Protect the first private workflow

$750/month Billed annually at $9,000 for the launch team plan.

Best when you already know the repo and workflow, and you want a clear commercial starting point without paying for passive seats or metered CI. This is the first paid path for private production use.

  • 1 private repo
  • 2 protected workflows
  • Unlimited standard CI runs
  • Unlimited reviewers and approvers
  • Business-hours email support, with Slack for active rollout coordination when useful
+ $2,000 / year per workflow + $3,000 / year per repo
Enterprise annual

Multi-repo rollout and support

From $36,000 / year Custom expansion for larger rollout and governance needs.

Best when multiple private repos share the same operational risk posture and you need support for rollout planning, procurement, or policy ownership.

  • Multiple repos and broader workflow coverage
  • Priority support and response targets
  • Procurement and security review support
  • Training for workflow or platform owners

Why pricing follows workflow risk

DriftFence protects a few workflows with real blast radius, so the pricing follows that risk rather than passive seats.

Commercial unit

Price the governance surface.

The right unit is the private repo and the protected workflow, not every developer who might read a report.

  • Workflow risk is the value driver
  • Reviewer access stays unlimited
  • High-consequence operations justify annual pricing
CI behavior

Do not meter the trust loop.

Standard CI runs, traces, and reports stay included. The product gets more valuable when it is always on.

  • No CI overage math
  • No per-trace billing
  • No penalty for always-on merge gating
Rollout motion

Start narrow, then expand.

The fastest route to value is one fit review and one clear first workflow before a broader rollout.

  • Better workflow selection
  • Cleaner first rollout
  • Less wasted implementation effort

How buying works

Keep the commercial motion simple: one workflow, one fit review, one clear starting package.

Step 1

Bring one workflow and one CI gap.

The best first input is the operation that is risky to change silently, plus the tests or CI slice your team already trusts.

Step 2

Choose direct annual or paid pilot.

Go straight to the Team plan if the first workflow is obvious. Use the Pilot if you want onboarding, rollout planning, and shared success criteria.

Step 3

Protect the first workflow, then expand.

DriftFence earns trust through explicit rollout. Start with one workflow, then add more when the first one proves its value. The first workflow setup path shows the concrete install, trace, contract, agent context, revision, and CI steps.

Pricing FAQ

Choose a buying path without turning DriftFence into a generic seat product.

Why not per seat?

The value is not evenly distributed across developers.

DriftFence is most valuable where a few workflows carry disproportionate operational risk. Pricing by passive readers would underprice the product and create unnecessary friction.

Do you meter CI?

No. The trust loop stays included.

Standard CI runs are part of the core product loop. Metering them would punish exactly the always-on enforcement behavior DriftFence is built to encourage.

Can we start with one workflow?

Yes. That is the intended buying motion.

DriftFence is built for `1-10` critical workflows. The cleanest rollout is to start with one operation, prove value, then expand.

What happens in a pilot?

You scope, instrument, and review one real workflow.

The pilot is a bounded commercial engagement to apply DriftFence to a real workflow with shared success criteria, email-first coordination, and a clear conversion path.

Is there a hosted service?

No hosted dependency is required.

DriftFence is still the same local CLI and GitHub Action. The commercial offer is about rollout and support, not forcing a hosted control plane.

What if we only want to evaluate fit?

Evaluate fit before you choose a plan.

The product page, result pages, and measured examples are the fastest way to qualify interest before you decide whether a Team plan or Pilot is the right start.

Next step

Start with one workflow and one CI gap.

If you already know the workflow that is risky to change silently, the fastest commercial path is a fit review. Bring the repo, the current CI slice, and the behavior your team cannot afford to let drift.

Check workflow fit See measured proof
Bring this context

One repo, one workflow, one reason it matters.

That is enough to tell whether DriftFence fits now, whether the workflow is ready for a pilot or whether a different readiness step comes first.

Commercial start

Team from $750/month. Pilots from $15,000.

Use Team when the first workflow is already clear. Use the Pilot when you want hands-on rollout help, shared success criteria, and a working thread that starts over email.