Skip to content
GigadriveDocs

Limits and pricing

Message and setting limits, per-plan queue, schedule and storage allowances, and how queue operations are counted and priced.

Queues are billed by operation, and your plan sets how many queues and schedules an environment holds and how much queued data your organization keeps. Every other limit is the same on all plans.

Pricing

The first 1,000,000 queue operations each month are included. After that, operations cost €0.40 per million.

ActionOperations
Send a message1 per started 64 KiB of the body
Deliver a push message, or receive a pull message1 per started 64 KiB, per delivery
Acknowledge, retry or extend a received message1
Acknowledge a batch of received messages1 per started 10 acknowledged
Settle a push delivery, by any responseFree
Create, list, browse or change queues and schedulesFree

A message under 64 KiB delivered on its first try therefore costs two operations through a push queue and three through a pull queue, or a little over two when it is acknowledged in a batch, as consume does. Retries add one delivery each. Queue operations appear under Usage in the console, next to your other metered resources.

Plan allowances

PlanQueues per environmentSchedules per environmentQueued data per organization
Starter251025 MiB
Pro500250256 MiB
EnterpriseNo limitNo limit1 GiB

Queued data counts the bodies of every message your organization holds, dead letters included. When it is full, sends answer 429 backlog_full until messages are processed, expire or are deleted. The same answer, with a message saying the queue service is at capacity, protects every organization if the platform's own storage fills; retry it after a short wait. Creating a queue past the plan's count answers 429 quota_exceeded.

Message limits

LimitValue
Message body1 MiB
Messages per batch send100, with at most 4 MiB of bodies
Headers per message32, each value up to 1,024 characters
Ordering group key128 characters
Deduplication key256 characters
Delay or scheduled timeUp to one year ahead
Messages per receive100
Messages per batch ack100
Long-poll wait20 seconds

Queue settings

SettingDefaultRange
Visibility timeout60 seconds1 second to 12 hours
Retention4 days1 minute to 14 days
Maximum attempts101 to 100
Retry backoff5 seconds, doubling to 15 minutes0 seconds to 1 day each
Deduplication window24 hoursUp to 7 days
Push concurrency1001 to 1,000

A message that is not processed within its retention period is deleted, whether or not it was ever delivered.