Pricing

Per repository, banded, annual.

Priced by repository because pricing by seat would need the product to count people — and it’s built never to. Bearing, the free tool, stays free.

BandRepositoriesAnnual, USD
11–3$4,500
24–15$12,000
316–50$24,000
4Organisation-wideQuote

Start with a 90-day pilot

Bearing Pro installed in your infrastructure, backfilled over your repository’s history on day one alongside us, and run for 90 days with your team. At the end you get a written readout — whatever it says.

Terms

  • 90 days from your first ingested run.
  • Your real repository count.
  • Priced at 90/365 of your band’s annual price.
  • Credited in full against the first annual term if you convert — fifteen months for the price of twelve.

Not free, and not a discount.

Who it fits

  • A .NET solution Bearing already runs on.
  • Three or more years of git history.
  • An inherited codebase with at least one engineer who joined in the last year.
  • Six or more developers with pull-request-based CI.
  • 1–15 repositories.
  • A lead willing to commit engineering hours.

What we ask of you

  • Named participants.
  • A day-one working session.
  • Two hour-long interviews, at day 45 and day 90.
  • A renewal attestation at the end, whether or not you convert.

What you get from us

  • A named contact.
  • Installation help.
  • The day-one session and backfill run with you.
  • A weekly check-in.
  • The written readout.
  • Export help, whenever you ask.

What never happens: your code, analysis and findings never reach us. The only thing that leaves is that attestation: repository identities hashed, nothing about people.

How it works

  • What counts as a repository

    Each distinct repository you declare. Several solutions or projects inside one repository — a monorepo — count once. You’re never charged more for declaring your repositories correctly.

  • Going over your band never blocks anything

    Nothing is refused or degraded. The service shows that you’re over and by how many, and it’s settled at renewal.

  • How buying works

    An order form and a purchase order — band 1 sits under a typical manager’s signing authority. Invoiced annually in advance, net 30, by bank transfer. No card, no checkout.

    No mid-term refund or cancellation; the licence runs to the end of the term. A mid-term upgrade is pro-rated.

  • The licence is granted to your organisation

    Not to an install. Run as many installs as you like; the repository count is across all of them.

  • Support

    One email address — contact@ironmarten.com — on business days, with a target of one business day to first response. No SLA at bands 1–2; at bands 3–4 an SLA can be quoted.

  • Is there a free trial?

    No — the free tool is the evaluation. It’s open source and runs on your own codebase today without asking us. To see the continuous half on your own history, start a pilot.

Start with the free tool

Run it on your codebase now. If it doesn’t build against your solution, finding out now costs nothing — before a pilot or an order form.

$ dotnet tool install -g IronMarten.Bearing
$ bearing ./MySolution.sln

Zero configuration. No account. No network call.

Questions

Does my code reach you?

No, for either product. Bearing makes no network call. Bearing Pro runs in your infrastructure: your code, its analysis and its history stay there, and digests and comments go only to the destinations you configure.

Do I need an account?

No account with us, for either product. Bearing needs none at all. Bearing Pro signs your people in to the server you host, and its licence key is issued to your organisation and verified offline.

What does it analyse?

The C# projects in a .NET solution. VB.NET and F# projects in the same solution aren’t analysed.

Is there a score?

No, and there never will be.

Does it use AI?

No. Findings are deterministic and auditable.

Can managers see who introduced the most findings?

No. It isn’t computed, and it isn’t available in any view, export or filter.

What happens if we don’t renew Bearing Pro?

Nothing changes for 30 days. After that the install keeps running read-only, indefinitely, and everything it holds can be exported.