Credit model
Checks consume credits based on check type and interval. Shorter intervals consume more credits.
Credits are purchased in advance via PayPal and expire 365 days after purchase. Prices follow the current price list.
Credits per run (reference)
| Check type | Credits per run | Notes |
|---|---|---|
| DNS | 1 | Default check per application. |
| SSL | 1 | Default check per application. |
| Uptime | 1 | Default check per application. |
| Header | 2 | Security header evaluation. |
| Simple HTTP | 1 | Custom checks for endpoints and APIs. |
| WAF | 8 | Baseline + probe logic for WAF changes. |
| WAF profiling | 200 + 3 per payload | Credits per profiling run plus payloads. |
Credit calculator
The calculator helps estimate costs before committing to a monitoring setup.
Purchase credits
Projects can purchase credits via PayPal to fund monitoring. Purchases appear in the credit ledger, and unused credits expire 365 days after purchase.
Spend log
The spend log lists credit usage by check and time window.
Budgeting tips
- Start with default intervals and adjust only when needed.
- Use custom checks for critical endpoints only.
- Run WAF profiling in batches instead of continuous runs.