Billing
Trunk Subscription Plans
Last updated
Trunk Subscription Plans
Last updated
Trunk offers a free plan to experiment with each of our features. Each feature has a free-tier limit; after exceeding this limit, we prompt you to upgrade to a paid subscription.
Similar to , our free tier limits are calculated based on a 30-day rolling window.
All
Users
5 commiters per month, unlimited on public repos
Code Quality
Quality & security metrics
Up to 100k issues uploaded
Merge Queue
PRs merged per month
100 PRs merged per month
CI Analytics
Real-time ingestion of data
14 days per repo
Flaky Tests
Number of
5 committers and 5M test spans per month
Data backfilling
Up to 30 days
Trunk Team Plans offers a monthly subscription plan using a per-seat model. At the end of every billing period, we calculate the number of users using Trunk and update the next month’s invoice to reflect the latest user count. Each seat has access to all of Trunk's features.
Code Quality
Quality & security metrics
Unlimited
Merge Queue
PRs merged per month
Unlimited
CI Analytics
Real-time ingestion of data
Unlimited
Flaky Tests
Number of
1 million test spans per seat per month.
$3 for each additional 1 million test spans.
Trials
A user is a non-bot user who has made a commit to a private repo with Trunk enabled in the last 30 days. Specifically, we look at their username; if someone changes their username on Git, we would consider that a separate user. We do not count contributions to public (open source) repos. Contributor counts are displayed on Settings > Billing.
For example, consider Alice, Bob, and Charlie are all in the same organization, which owns two private repos: abc/repo1
and abc/repo2
. Given the following timeline of events:
Alice commits code to abc/repo1
.
Bob commits code to abc/repo2
.
Charlie commits code to abc/repo1
.
On Day 1, the user count would be one: just Alice. On Day 15, the user count would be two: Alice and Bob, since the same organization owns both private repos. On Day 22, the user count would be three: Alice, Bob, and Charlie. On Day 30, the user count would be three. We consider days 1 through 30 (inclusive), which include Alice's, Bob's, and Charlie's commits. On Day 31, the user count would be two. We consider days 2 through 31 (inclusive), which only includes Bob's and Charlie's commits.
Your security is important to us. We do not store your credit card information anywhere in our systems. Online payments are processed using Stripe, which is PCI-compliant in accordance with industry standards.
Trunk Enterprise offers powerful admin controls, dedicated support, access to custom billing or terms, and features like SSO. If your team is interested in an enterprise plan, please contact .
You and your team can trial Trunk before signing up for an Enterprise or Team plan. To try Trunk, please contact . To extend or cancel the trial, please contact .
Trunk requires the to be installed in your repo to count seats.
At the end of every billing cycle, Trunk calculates what the next invoice should be. Trunk determines feature usage and the number of seats used over the . See our section on to determine how much we charge per feature usage.
You can edit your payment details by navigating to Settings > Billing and clicking on the pencil icon on the credit card. Trunk accepts both credit card and ACH; if you require a different payment method, please contact us at .
You can cancel an active Trunk subscription by navigating to Settings > Billing and clicking the Cancel Subscription button. Your plan will transition back into the ; if you want to re-enable this plan, please contact us at .
Cancelling a Trunk Plan may result in a degraded product experience. Please contact us at to re-enable any canceled plan.