Pricing
Pricing
Sync is priced per active linked issue. Chains, projects, admins and contributors are unlimited, and tiers differ by sync speed and security rather than by seats. Prices are quoted on request.
The model
One metered unit, no seats
Metered unit: active linked issues
A link is one origin issue paired with its twin, counted once per pair. A link is active if its origin issue is open or changed in the last 30 days. Closed, quiet issues on long projects don't count.
Unlimited chains, projects, admins and contributors
There are no seat prices. Charging per seat would discourage delegation, which is the point of Sync.
Tiers differ by speed and security
Sync speed: the poll interval and webhook priority. Security: SSO, SCIM, customer-managed keys (BYOK), detailed logs and log retention. Later: AI mapping suggestions and custom rules.
Enterprise can be billed per project
A project is a chain's origin container. Enterprise also gets BYOK, SCIM, custom retention and priority support.
Compare tiers
Starter, Team, Business and Enterprise
Every tier keeps the same invariants and the same unlimited chains, projects, admins and contributors. What changes is sync speed, security features and, later, AI suggestions.
| Feature | Starter | Team | Business | Enterprise |
|---|---|---|---|---|
Active linked issuesThe metered unit: a linked pair, counted once, whose origin issue is open or changed in the last 30 days. | Metered | Metered | Metered | Metered, or billed per project |
Chains, admins and contributorsNo seat prices. Charging per seat would discourage delegation. | Unlimited | Unlimited | Unlimited | Unlimited |
ProjectsUnder per-project billing, a project is a chain's origin container. | Unlimited | Unlimited | Unlimited | Unlimited, or the billing unit |
Poll intervalHow often we check a platform for changes when no webhook arrives. | Set per tier | Set per tier | Set per tier | Set per tier |
Webhook priorityWhere webhook-driven changes sit in the processing queue. | Set per tier | Set per tier | Set per tier | Set per tier |
Single sign-on (SSO)Through WorkOS, on plans that include it. | Set per tier | Set per tier | Set per tier | Set per tier |
SCIM provisioningComes later. | Not included | Not included | Not included | Planned |
Customer-managed keys (BYOK)Hold the encryption key in your own cloud account. | Not included | Not included | Not included | Included |
Detailed logsOpt-in. Encrypted per tenant, and every view is audited. | Set per tier | Set per tier | Set per tier | Set per tier |
Log retention | Set per tier | Set per tier | Set per tier | Custom |
Priority support | Not included | Not included | Not included | Included |
Per-project billing | Not included | Not included | Not included | Available |
AI mapping suggestionsLater. | Planned | Planned | Planned | Planned |
Custom rulesLater. Rules are engineer-authored in v1. | Planned | Planned | Planned | Planned |
- Set per tier: the value differs between tiers and is fixed in your quote.
- Planned: on the roadmap, not available yet.
- Prices are quoted on request.
Over your allowance
What happens when you go over
Usage is counted once a day by a background job, never on the sync path. When the count of active linked issues goes over your allowance:
- Existing links keep syncing
Nothing already linked is paused. Stopping live project data would cost you more than the unpaid usage costs us.
- New links pause until you upgrade
New elections, links and filter-admitted creations are blocked while you are over the allowance, and admins see an upgrade prompt.
- You hear about it early
Owners and admins are notified at 80% of the allowance, at 100%, and daily while over it.
Questions about a tier?
Tier contents and prices are quoted on request. Sign up to create your org, or read how we handle your data first.