Skip to content
Patrol

Patrol Cloud

Plans and what each one allows

The library stays free under BSD-3-Clause on every plan, including no plan at all. What follows is the hosted side: storage, the console, ingest keys and the fan-out. Limits are enforced by the API, not by the honour system, and the numbers here are the ones it checks.

Patrol Cloud plans, limit by limit
LimitFree$0a monthOne service, one alert channel, no card.ProPricing coming soonA production service with a team watching it.BusinessPricing coming soonMany services, longer history, more people.
Events a month10,000500,0005,000,000
Event history7 days30 days90 days
Projects21050
Destinations per project21025
Largest batch4 MiB16 MiB32 MiB
Included
  • Sign in with GitHub
  • Slack, Discord, email and Twilio destinations
  • Stacktraces with editor deep links
  • Ingest keys you can revoke
  • Everything in Free
  • One rule per destination, filtered by event type
  • Delivery failures kept per destination
  • Email support from the people who wrote the library
  • Everything in Pro
  • 90 days of event history
  • Batches up to the 32 MiB the library allows
  • A named contact for incidents
Sign upStart freeOpen the consoleOpen the console

Need more than Business, or an invoice instead of a card? Write to us from thecontact page and say what your volume looks like.

FAQ

Billing questions

What counts as an event?

One element of the JSON array your producer posts. A batch of 40 events is 40, whatever their type. Debug events count only when the project keeps them, which is a per-project switch. Events refused because the batch was malformed, too large or over quota are not stored and are not billed, though they are counted as rejected on the usage page so a misconfigured sender is visible.

What happens when I pass the monthly limit?

Nothing is dropped on the spot. Patrol Cloud keeps accepting and storing events for 24 hours past the limit and marks them as over quota, so an incident in the last week of the month does not go dark. After that window the ingest endpoint answers 429 with RESOURCE_EXHAUSTED, which a Client surfaces as a ServerError. Your own destinations, configured in the library, keep working the whole time.

Why do Pro and Business have no price yet?

Because they are not priced yet. The limits are settled and the plans are built; the amount is not, and a number on this page would be a guess. Start on the free plan, and the console will show the price and the upgrade button the moment there is one to show.

Do I need a plan to use the library?

No. The library is BSD-3-Clause and complete on its own: Slack, Discord, Twilio, email, SQL and your own patrol server all work with no account here. A plan buys the hosted side, which is storage, the console, per-project ingest keys and the fan-out running somewhere other than your process.

The library is on GitHub under BSD-3-Clause. The console is at patrol.hellenic.dev/app.