Billing

Billing is where you manage your subscription and payments: your plan, upgrades and downgrades, the usage invoice, issue rejection, payment methods, and cancellation. This page explains how those work; it does not list prices. For current numbers, see the pricing page and Settings > Billing.

For how usage becomes charges, see Pricing; for how the prepaid balance works, see Credits. Manage everything here under Settings > Billing.

Plans

Every organization is on a paid credit plan. A plan adds credits and includes a baseline of usage each cycle; plans differ in how much of each they include. Choosing or changing a plan takes effect as described below.

Upgrades and downgrades

• Upgrading takes effect immediately: you are charged for the new plan and its credits are added once payment is confirmed. The upgrade review shows the card being charged and your next renewal, and takes a discount code: apply one and the amount due today drops before you confirm. A discount you already have follows you to the new plan, and a code that repeats is added alongside it for later renewals.
• Downgrading is scheduled for the end of your current billing cycle, so you keep what you are paying for until then. A pending downgrade shows in Settings > Billing and can be superseded by a later change.

The usage invoice

Most metered usage is billed on your billing cycle: log ingestion, issues, and automation runs all appear on your invoice. Only token usage works differently — it draws from your prepaid credit balance instead of the invoice.

Issue rejection

If Sazabi got a finding wrong, you can reject it within 24 hours of its creation, subject to your plan's remaining rejection allowance. An accepted rejection excludes that issue from billable issue usage. Unlike Ignore, rejection cannot be undone or re-opened.

Eligibility and allowance

The allowance applies to the billing cycle in which the issue was created, even if you reject it after the next cycle starts. Changes to your rejection allowance take effect in the next billing cycle. The rejection dialog shows Rejections left and Review by. Opening it does not reserve a rejection: the deadline and remaining allowance are checked again when you confirm.

From the dashboard, Slack, or Microsoft Teams

In Issues, use the issue's Reject action. Review the remaining allowance, deadline, and billing effect, choose a reason, then confirm Reject issue. You can also reject an eligible issue from its Slack or Microsoft Teams issue card. Your chat account must be linked to a Sazabi user with permission to manage that project's issues.

Choose the reason that best describes the problem:

From the CLI, API, or SDK

Sign in with your user account; secret keys cannot reject issues. See CLI reference for installation and authentication. The CLI refuses a rejection that is no longer allowed and tells you why (the review deadline has passed, the cycle allowance is used up, or the plan has no allowance):

sazabi issues reject <issue-id> --reason not_real --json

The public API and TypeScript SDK expose the same behavior, and also let you check eligibility before submitting a rejection. See Get issue rejection eligibility, Reject an issue, and TypeScript SDK.

What changes after rejection

The rejected issue disappears from your issue views and cannot be restored. If you reject it from a Slack issue card, Sazabi attempts to delete that card, or replace it with a rejection notice if deletion fails. In Microsoft Teams, Sazabi attempts to replace the card with a rejection notice. Rejection does not erase other previously delivered messages or copies outside Sazabi.

Billing excludes the rejected issue before applying any included issue allowance. Rejection does not issue a cash refund or change an invoice already issued. If the billing adjustment is still pending when rejection is accepted, Sazabi completes it automatically; you do not need to reject the issue again.

If rejection is unavailable because the deadline passed or the allowance is exhausted, you can still Ignore an open issue. Ignoring retains the issue and does not remove its billable usage.

Payment methods and invoices

Manage your payment method and view past invoices under Settings > Billing. Money is always collected before credits are added: renewals, upgrades, and top-ups apply credits only after a confirmed payment.

When a payment fails

• A failed renewal opens a fixed recovery window during which Sazabi keeps retrying and you can pay through the billing portal. If it is still unpaid at the end of the window, Sazabi cancels the subscription.
• A failed automatic top-up is retried within the same cycle. To retry with a different card, update your default payment method under Settings > Billing.
• An unpaid balance is collected over a few scheduled attempts. If it stays unpaid, log ingestion is denied until a payment settles the balance.

Gates

Two gates decide what your organization can do:

• The subscription gate controls tenancy capabilities — continuous log intake, repository webhooks, and scheduled automations. It closes only when a subscription is winding down.
• The credit gate controls new token usage — it requires a positive credit balance. See Credits.

Cancellation

Canceling takes effect at the end of your current billing cycle — service continues until then, and canceling does not refund or erase your credit balance. You can resume your subscription at any point before the cancellation takes effect. After cancellation, your credit balance is preserved but dormant until you resubscribe.

Further reading