DOCS

Billing and quota: understand plans before traffic scales.

KillBot plans are based on protected routes, monthly checks, Traffic Log history, and feature access. Start with a 1-day trial, fund your wallet, and upgrade when traffic volume grows.

1-day trial Monthly checks Wallet-funded plans Upgrade anytime Traffic Log retention
Billing model

How KillBot billing works.

1-day trial

Test one route before committing to a paid plan.

Wallet-funded plans

Paid plans are funded from the KillBot wallet.

Monthly checks

Each plan includes a monthly traffic-check allowance.

Upgrade anytime

Higher plans unlock larger check limits, more routes, and longer log history.

Usage

What counts as a check.

A check happens when KillBot evaluates a visit through a Protected Page, Smart Link, or configured install mode. The exact behavior can depend on the route and package.

Limit behavior

What happens at the monthly limit.

When the monthly check limit is reached, full checks pause and traffic is allowed by default until the plan renews or the account upgrades. This prevents surprise hard blocking from a billing limit.

Safe quota behavior is part of the product model: usage limits should never silently turn into stricter blocking.
What changes by plan

Plan comparison mini table.

Plan area What changes
Protected pages Higher plans allow more protected routes.
Monthly checks Higher plans allow more evaluated visits.
Traffic Log history Higher plans keep longer decision history.
Advanced rules Higher plans can include more rule depth.
Alerts/API Available based on plan capability.
Safety principles

Billing safety principles.

Warn before limit

Show usage and warnings before monthly checks are exhausted.

Do not silently block at quota

Allow traffic by default when full checks pause so a billing ceiling does not create hidden hard blocking.

Keep usage visible in dashboard

Make route count, monthly checks, and retention obvious before teams need an upgrade.

Get started

Start with the smallest plan that fits your first route.

Use the trial to validate one route, then upgrade only when volume demands it.