# Azure Queue Storage vs Trigger.dev

Canonical: https://inetgeek.com/compare/azure-queue-storage-vs-trigger-dev/

Every value below is read from Azure Queue Storage's and Trigger.dev's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | Azure Queue Storage | Trigger.dev |
| --- | --- | --- |
| Pricing model | Per 10,000 operations plus stored data, with the rate set by redundancy: LRS Class 1 operations are $0.004 per 10,000, ZRS and GRS cost more for the same call. There is no plan fee and no included allowance. | A monthly plan fee that is also a credit balance — the fee buys compute rather than sitting on top of it — with concurrency, preview branches, dashboards and schedules each priced as separate add-ons beyond the plan's allowance. |
| Included per month | None included — every operation is billed. Class 1 operations are $0.004 per 10,000 on LRS in East US, which is $0.40 per million, matching Amazon SQS's standard rate exactly. | Credits rather than a message or execution count: $5 a month free, $10 included on Hobby and $50 on Pro, spent against compute. |
| Maximum message size | 64 KB per message. A queue may hold millions of messages, bounded only by the storage account's capacity rather than a queue-level ceiling. | 3 MB per trigger payload (each batch item up to 3 MB on SDK 4.3.1+); task outputs up to 10 MB; payloads over 512 KB offloaded to object storage. |
| Message retention | Messages in the queue are billed as stored data at $0.045 per GB-month on LRS, rather than granted as a retention window. Azure charges for depth, not for time. | Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching. |
| SOC 2 | Listed among Azure's compliance offerings (SOC 1, SOC 2, SOC 3) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service. | SOC 2 Type II compliant; latest report available on request for Enterprise customers. |
| HIPAA | Listed among Azure's compliance offerings (HIPAA) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service. | Meets HIPAA Business Associate requirements; a signed BAA is a paid add-on for running PHI workloads on Trigger.dev Cloud. |

## Where they differ

### Pricing model

- Azure Queue Storage: Per 10,000 operations plus stored data, with the rate set by redundancy: LRS Class 1 operations are $0.004 per 10,000, ZRS and GRS cost more for the same call. There is no plan fee and no included allowance. ([source](https://prices.azure.com/api/retail/prices))
- Trigger.dev: A monthly plan fee that is also a credit balance — the fee buys compute rather than sitting on top of it — with concurrency, preview branches, dashboards and schedules each priced as separate add-ons beyond the plan's allowance. ([source](https://trigger.dev/pricing))

### Included per month

- Azure Queue Storage: None included — every operation is billed. Class 1 operations are $0.004 per 10,000 on LRS in East US, which is $0.40 per million, matching Amazon SQS's standard rate exactly. ([source](https://prices.azure.com/api/retail/prices))
- Trigger.dev: Credits rather than a message or execution count: $5 a month free, $10 included on Hobby and $50 on Pro, spent against compute. ([source](https://trigger.dev/pricing))

### Maximum message size

- Azure Queue Storage: 64 KB per message. A queue may hold millions of messages, bounded only by the storage account's capacity rather than a queue-level ceiling. ([source](https://learn.microsoft.com/en-us/azure/storage/queues/storage-queues-introduction))
- Trigger.dev: 3 MB per trigger payload (each batch item up to 3 MB on SDK 4.3.1+); task outputs up to 10 MB; payloads over 512 KB offloaded to object storage. ([source](https://trigger.dev/docs/limits))

### Message retention

- Azure Queue Storage: Messages in the queue are billed as stored data at $0.045 per GB-month on LRS, rather than granted as a retention window. Azure charges for depth, not for time. ([source](https://prices.azure.com/api/retail/prices))
- Trigger.dev: Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching. ([source](https://trigger.dev/pricing))

### SOC 2

- Azure Queue Storage: Listed among Azure's compliance offerings (SOC 1, SOC 2, SOC 3) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service. ([source](https://learn.microsoft.com/en-us/azure/compliance/))
- Trigger.dev: SOC 2 Type II compliant; latest report available on request for Enterprise customers. ([source](https://trigger.dev/security))

### HIPAA

- Azure Queue Storage: Listed among Azure's compliance offerings (HIPAA) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service. ([source](https://learn.microsoft.com/en-us/azure/compliance/))
- Trigger.dev: Meets HIPAA Business Associate requirements; a signed BAA is a paid add-on for running PHI workloads on Trigger.dev Cloud. ([source](https://trigger.dev/security))

## Which should you choose?

Pick Azure Queue Storage if Azure-resident systems that want a queue billed like storage — operations plus depth, no plan to choose and no capacity to provision.

Pick Trigger.dev if Teams that want background jobs written as normal code with the bill expressed as compute credits rather than a per-message meter.

Consider something else: Azure Queue Storage — Queued messages are billed as stored data, so a backlog costs money by the gigabyte-month, and there is no free allowance at all where SQS gives a million requests a month.

Consider something else: Trigger.dev — Concurrency is the axis that forces an upgrade — 20 simultaneous runs on free, 50 on Hobby, then $10 a month per additional 50.

## Documented by only one

- Free tier: Trigger.dev: Yes
- Entry paid plan: Trigger.dev: $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits.
- Maximum delay: Azure Queue Storage: Time-to-live defaults to seven days and can be set to any positive number, or to -1 for a message that never expires — the only queue here with an unbounded option.
- Concurrency: Trigger.dev: 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50.
- ISO 27001: Azure Queue Storage: Listed among Azure's compliance offerings (ISO 27001) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
- GDPR / data residency: Trigger.dev: Stated GDPR compliant; DPA forms part of the Terms of Service automatically on sign-up.
- PCI DSS: Azure Queue Storage: Listed among Azure's compliance offerings (PCI DSS) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
- Encryption at rest: Trigger.dev: Data encrypted at rest with AES-256 and in transit with HTTPS/TLS.
- Role-based access control: Trigger.dev: Role-based access control (RBAC) and SSO listed as Enterprise plan features.
- Private networking / VPC: Trigger.dev: AWS PrivateLink to resources in your own AWS VPC; a Pro and Enterprise feature enabled on request.

## Questions this comparison answers

**Should I choose Azure Queue Storage or Trigger.dev?**

Pick Azure Queue Storage if Azure-resident systems that want a queue billed like storage — operations plus depth, no plan to choose and no capacity to provision.
Pick Trigger.dev if Teams that want background jobs written as normal code with the bill expressed as compute credits rather than a per-message meter.