How billing works
Durin bills per enabled connection, not per seat. Understand what counts, what is free, and how pricing tiers work.
Start with the organization’s connection quantity
Billing follows the configured installations that are enabled, verified, and in production. The quantity is calculated from authoritative connection state rather than from a list of employees or the number of tool calls made by an agent.
Before enabling another provider, review the activation preview for the organization. It shows the commercial change associated with that activation. Creating a draft lets you prepare the setup without immediately adding an enabled billable unit.
Connection-only pricing
Durin charges per enabled, verified upstream connection. People, agents, tools, OAuth grants, sessions, calls, SSO, directories, and exports do not multiply the connection count. You can add your entire team without seat charges.
What counts as a connection
An enabled, verified production connection — with its policy and authentication boundary — counts toward the organization’s quantity. Repositories, projects, tools, and users within that configured connection do not add units.
Free tier
The first enabled, verified production connection has no recurring connection charge. Payment setup is still required before activation. Draft, disabled, and synthetic sandbox connections do not add billable quantity.
Pricing tiers
Your first four paid connections are $399 each per month. Each additional paid connection is $199 per month. Payment details are required before your first production connection. Transfer overage is measured but not charged.
Transfer allowance
10 GB per connection monthly, pooled across your organization and prorated by enabled time, including the free connection. Transfer overage is measured, not charged.
Example: grow from one connection to several
With one qualifying production connection, the organization uses its free connection allowance. Additional connections enter the paid tiers in order. The discounted tier applies to connections beyond the first four paid connections; it does not retroactively move every paid connection to the lower tier.
Two teams using the same configured installation do not add a seat charge. Two separate enabled installations count separately even if they use the same provider. Use the installation boundary, not the provider’s name or the number of projects inside it, when estimating quantity.
Understand changes during the month
Enabling or disabling an installation changes its contribution to connection quantity. Invoice amounts may include proration, and transfer allowance is pooled and prorated by enabled duration. Do not compare a partial-month invoice directly with a full-month headline subtotal without checking the effective dates.
Disabling and re-enabling a connection does not erase transfer already measured for the period. Transfer overage is tracked separately and is not charged in the current plan. Historical usage remains relevant even after an installation no longer contributes enabled quantity.
Payment setup is separate from provider activation
Payment details are required before the first production activation, including the free connection. Completing payment setup does not authorize a provider, release a reviewed tool, or enable an installation by itself.
Use the billing settings to inspect connection quantity, the tier breakdown, and transfer usage. Use the connection’s setup guide for authentication and activation blockers. Keeping those two checks separate avoids treating a payment update as proof that tool access is ready.