---
title: "Pricing | Counterpart"
url: https://counterpart.dev/pricing/
html: /pricing/
markdown: /pricing/index.md
version: 0.2.0
updated: 2026-09-17
description: "Counterpart is priced per paired customer, per month, in three tiers set by authority: Knows, Fixes, Acts. The customer side is always free."
---

# Priced like headcount, because that is what it replaces.

Version 0.2.0 Updated 2026-09-17 Markdown twin [/pricing/index.md](/pricing/index.md)

You are buying an engineer for every customer, at a fraction of the cost of the one you can't hire. Tiers are set by how much your engineer is allowed to do.

## The three tiers. {#tiers}

Per paired customer, per month. The same data as JSON: [/api/pricing.json](/api/pricing.json).

### Knows {#knows}

- Reproduces and triages every report
- Reads the changelog and warns affected customers
- Remembers each customer's integration and history

Tier 1. Read-only inside your company.

### Fixes {#fixes}

- Everything in Knows
- Applies patches in a sandbox and runs your tests
- Opens pull requests for your reviewers

Tier 2. Patch and PR, never merge.

### Acts {#acts}

- Everything in Fixes
- Refunds, flags and rollbacks within caps you set
- Owner approval on anything that moves money

Tier 3. Bounded authority, full audit trail.

$0 customer side, always

Your customers never pay to pair with you. Their agent connects over Knock, the open connector, and reaches your engineer for free. Vendor rates per paired customer are set with each design partner during onboarding.

## What each tier is allowed to do. {#compare}

Authority climbs one step at a time. Nothing in any tier can merge code or move money without a person.

Authority by tier

| Capability | Knows | Fixes | Acts |
| --- | --- | --- | --- |
| Reproduce and triage reports | Yes | Yes | Yes |
| Warn customers about breaking changes | Yes | Yes | Yes |
| Apply patches in a sandbox, run tests | No | Yes | Yes |
| Open pull requests | No | Yes | Yes |
| Refunds, flags, rollbacks under caps | No | No | Yes |
| Merge or push code | Never | Never | Never |
| Move money without owner approval | Never | Never | Never |

## Questions vendors ask first. {#faq}

### What counts as a paired customer? {#paired-customer}

A customer whose agent holds an active Knock pairing with your engineer during the month. A customer who never pairs costs nothing.

### Why is the customer side free? {#customer-side-free}

Because the engineer is yours. The more of your customers pair, the fewer tickets your team writes from memory, so charging them would work against you.

### Can we start on Knows and move up? {#move-up}

Yes. Tiers change authority, not setup. Moving from Knows to Fixes grants your engineer a sandbox checkout and the ability to open pull requests.

### Where are the prices? {#where-prices}

This is a prototype. Rates per paired customer are being set with design partners, and this page will list them once they are public.

## Give every customer an engineer. {#start}

We are onboarding a small number of API-first companies whose customers already run agents. If you merge outside pull requests today, you are ready.

- [Talk to us](/talk/)
- [See the loop](/how-it-works/)