Pricing
Use this page to understand the billing model for 1stLine by Burava.
Open Billing to view and manage plans for your organization.
Billing is controlled in Burava Platform. 1stLine receives the active billing controls from Platform and applies the resulting plan limits and capabilities inside 1stLine.
Billing model
1stLine is not priced by the number of responders.
You can add the Users, Teams, Lines, Line Members, Schedules, Escalation Chains, and Routing Rules you need for your on-call process. The main billing dimensions are:
- Accepted alert events: alert events accepted by 1stLine for processing.
- Retention: how long accepted alert history stays available in normal 1stLine views.
- Plan capabilities: plan-based features such as event packs, default communication integration, and AI Escalation.
This means a team can model a real escalation process without worrying about a per-responder cap. Billing is tied to alert volume, retained history, and enabled capabilities.
1stLine bills around alert volume because alert events are the workload the product processes. At the same time, incidents are exactly when alert volume can spike. Paid-plan protection features are designed so you are not punished immediately just because a real incident sends more alert events than usual.
Accepted alert events
An accepted alert event is counted when 1stLine accepts an alert payload for an active shared 1stLine organization and creates or updates the matching Alert Instance workflow.
Accepted alert events can come from:
- new firing alerts
- repeated firing alerts that are accepted as another occurrence
- resolved alerts that are accepted as a resolution occurrence
- internal alert-instance creation flows that create accepted alert usage
Events that fail before acceptance, such as invalid Schema Token authentication or failed schema validation, are not accepted alert events.
Surge protection and first overage grace
Some paid plans can include surge protection, first overage grace, or both.
Surge protection is for sudden alert spikes. If an incident causes a sharp increase in accepted alert events, surge protection can absorb the spike before hard-cap decisions are applied.
First overage grace is for the first time a paid plan goes over its included accepted alert-event amount. When available, 1stLine can keep ingestion active for that first overage period instead of immediately hard-capping the organization.
These features are not a replacement for the right long-term plan size. They are there because production incidents are noisy, and your escalation system should keep helping during the incident instead of making the spike worse.
If the included amount is reached and your organization has no event-pack credits, no applicable surge protection, and no applicable first overage grace, a hard cap can become active. When that happens, new schema ingestion can be disabled until the cap is cleared.
Retention
Each plan includes a retention window in days.
Retention controls how long accepted alert data remains available in normal 1stLine views. Older alert data is processed by the retention lifecycle after it falls outside the active retention window.
For downgrade behavior, see Limits.
Event packs
Some plans allow event packs. Event packs add extra accepted alert-event capacity on top of the plan’s included monthly amount.
Event-pack credits are used before a hard cap is applied. They are useful for temporary spikes. If your normal usage is consistently above the included amount, changing plan is usually the better fit.
How plan selection works
Billing supports two visible paths:
- No active plan access: you can use Choose Plan on a plan card to start checkout.
- Active plan access: your current plan is marked as Current, and plan changes are handled through Open customer portal.
If a plan does not have self-serve pricing available, Billing can show Contact sales.
Who can manage billing actions
Billing actions are available to organization admins.
Other roles can still open Billing and review usage and plan details, but billing action buttons are disabled.
Need help choosing a plan?
Contact support@burava.com if you need help estimating accepted alert-event volume, retention requirements, or event-pack usage.