Submitters

A submitter is any entity that sends events to Buildnote. An active submitter is one who submitted at least one event during the billing period. This could be a developer committing code to a repository or any process (e.g. GitHub’s dependabot) triggering a build that results in events being sent to Buildnote.

Buildnote counts the number of active submitters on a monthly basis, with the billing period ending on the last day of each month. This means the number of active submitters may vary from month to month depending on your team’s activity patterns, allowing for natural fluctuations in your development cycle without penalty.

Additional Events

Buildnote allocates 400k events per month for each active submitter. This creates a total event pool for your team:

Total allotted events = Active Submitters × 400k

When your team exceeds this allocation, Buildnote charges for additional events in 1M event increments. Please refer to plan for pricing and cost calculator for a more accurate estimate based on combination of submitters and events.

Additional Storage

Buildnote allocates 1GB of storage per active submitter. This creates a total storage pool for your team:

Total allotted storage = Active Submitters × 1GB

Important: Storage is cumulative and represents your total data stored, not a monthly allocation. Storage only decreases when events expire (after 400 days for Pro plan), unlike the monthly event allocation which resets each billing period.

When your team’s total stored data exceeds this allocation, Buildnote charges for additional storage at £0.50 per GB. Please refer to the cost calculator for accurate estimates based on your specific storage requirements.

AI Requests

Buildnote charges separately for AI-powered features such as test failure summaries and chat interactions with AI models. Each request to an AI model incurs a charge of £0.05, billed monthly based on actual usage.

AI requests are tracked independently of other metrics and include any interaction with Buildnote’s AI capabilities, whether for automated analysis, summaries, or interactive assistance.

Pricing Examples

Consider a team subscribed to a plan priced at £15/submitter, £4/1M events, £0.50/GB storage, and £0.05/AI request, with 5 active submitters (e.g. developers regularly triggering builds) generating 1.7 million events monthly, with a total accumulated storage of 4GB, and making 150 AI requests:

Cost calculation:

• Submitter cost: 5 × £15 = £75
• Event allocation: 5 × 400K = 2 million events (monthly)
• Additional events: 0 (£4 per million) = £0
• Storage allocation: 5 × 1GB = 5GB (total storage allowed)
• Additional storage: 0GB (£0.50 per GB) = £0
• AI requests: 150 × £0.05 = £7.50
• Total monthly cost: £82.50

Now, if the same team generated 3.2 million events monthly, had accumulated 8GB total storage, and made 300 AI requests:

• Submitter cost: 5 × £15 = £75
• Event allocation: 5 × 400K = 2 million events (monthly)
• Additional events: 1.2 million (requires 2 × £4) = £8
• Storage allocation: 5 × 1GB = 5GB (total storage allowed)
• Additional storage: 3GB total (3 × £0.50) = £1.50
• AI requests: 300 × £0.05 = £15
• Total monthly cost: £99.50

For a larger team with 10 active submitters, 8 million events monthly, 25GB total accumulated storage, and 800 AI requests:

• Submitter cost: 10 × £15 = £150
• Event allocation: 10 × 400K = 4 million events (monthly)
• Additional events: 4 million (requires 4 × £4) = £16
• Storage allocation: 10 × 1GB = 10GB (total storage allowed)
• Additional storage: 15GB total (15 × £0.50) = £7.50
• AI requests: 800 × £0.05 = £40
• Total monthly cost: £213.50

Note: Storage accumulates over time as events are collected and only decreases when events expire after the retention period (400 days for Pro plan). This differs from the monthly event allocation which resets each billing period. AI requests are billed monthly based on actual usage during that billing period.

Our pricing model scales efficiently with your team’s activity, build volume, storage needs, and AI usage, providing predictable costs while accommodating usage spikes.