Illustrative pricing layout
Model a plan ladder without the guesswork.
Sample plans demonstrate comparison and conversion hierarchy; no purchase, trial or subscription is available.
Verify all included capabilities, limits and service levels before publishing.
Available plans
Hobby
An entry-tier example for side projects and early experiments.
- 100,000 job executions / month
- 3 queues
- 5 edge regions
- 72-hour log retention
- Community support
- Dead-letter queue (100 jobs)
Pro
For growing teams that need reliability, observability, and scale.
- 10M job executions / month
- Unlimited queues
- 40+ edge regions
- 30-day log retention
- Priority email support
- Dead-letter queue (unlimited)
- Custom retry policies
- Metrics export (Datadog, Prometheus)
- Webhooks & event streams
Enterprise
For teams with compliance, SLA, and volume requirements.
- Unlimited executions
- Unlimited queues
- Private edge regions
- 1-year log retention
- Dedicated Slack support & SLA
- Dead-letter queue (unlimited)
- Custom retry & timeout policies
- SSO / SAML
- Audit logs
- Custom contracts & BAA
Full comparison
| Feature | Hobby | Pro | Enterprise |
|---|---|---|---|
| Monthly executions | 100K | 10M | Unlimited |
| Queues | 3 | Unlimited | Unlimited |
| Edge regions | 5 | 40+ | Private + 40+ |
| Log retention | 72 hours | 30 days | 1 year |
| Dead-letter queue | 100 jobs | ||
| Custom retry policies | |||
| Metrics export | |||
| Webhooks | |||
| SSO / SAML | |||
| Audit logs | |||
| SLA | 99.9% | 99.99% | |
| Support | Community | Priority email | Dedicated Slack + SLA |
Pricing FAQ
One execution is one call to your job handler — regardless of payload size or runtime duration. Retries count separately only if the original job failed.
Use this slot to explain a real product's proration policy, activation timing, and billing date in plain language.
The sample table suggests a trial, but template owners must replace this answer with their verified duration, payment requirements, and cancellation terms.
Use this answer to state the real overage, throttling, and notification behavior before publishing a pricing page.
Review the surrounding content model
Preview the lead-capture pattern or inspect the sample documentation before adapting this page.