Quotas & Limits
Quasar Cloud meters usage per organization in quota units. The Community Edition keeps the same accounting, but its limits are set so high (a balance of 100,000,000 units and 100,000 requests per second) that they do not limit a single node.
🧪 Public Beta
Quasar Cloud is in public beta and free of charge:
- Every organization receives 1,000 free quota units when it is created.
- Quota cannot be bought during the beta. If your organization needs more units, write to [email protected] from the email address of your account.
- During the beta, features, limits and the free units may change.
🧮 What Costs Quota
| Operation | Units |
|---|---|
Sync a transaction (POST /v1/engine/pulsar/sync), live app | 10 |
| Sync a transaction, test app | 5 |
| Deliver a webhook | 1, for the first attempt only |
Read the history (GET /v1/engine/pulsar/history) | 0 |
Health check (GET /v1/engine/monitoring/health) | 0 (public, no key) |
Every sync request is counted, also one that Quasar answers with duplicate: true because it already has a transaction with that txKey. A duplicate creates no second record and no second tracking, so a retried onRemoteCreate is safe, but not free.
📉 When the Quota Is Used Up
- Syncs are still accepted so that no transaction of your users is lost: the response has
mode: "lazy"(HTTP202instead of200), and the transaction waits in a queue instead of being tracked right away. - Other requests with a key, including the history, are rejected with
402 Payment Requireduntil the organization has quota again.
Watch the usage of your organization in the dashboard; Quasar Cloud emails the owners when the balance runs low. During the public beta, write to [email protected] for more units.
🚦 Other Limits
| Limit | Value |
|---|---|
| Requests per second | Per organization (5 in Quasar Cloud); more requests are rejected with 429 |
| Transactions per history page | limit up to 100 (default 10) |
| History depth | Pages reach 10,000 transactions back; deeper pages answer 400 page_too_deep (filter by status, chain, wallet or txKey instead) |
| Apps per organization | 30 |
| Webhook endpoints per app | 20 |
localhost webhook endpoints | 1 per organization (see Webhooks) |
| Webhook response time | 10 seconds per delivery attempt |
A synced transaction must also pass the safety limits of Pulsar (sizes of the text fields and of payload); a transaction that does not is rejected with 400.