Skip to content
inetGeek

Azure Queue Storage vs Inngest

SEPT 2026 audit

A comparison of Azure Queue Storage and Inngest built from values read directly from each provider's own documentation, with the source recorded against every figure.

Updated 16 criteria comparedSources last checked

The short answer

Choose 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.

Editorial · Palash Bagchi · approved

Choose Inngest if…

Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

Editorial · Palash Bagchi · approved

Consider something else if…

  • 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.
  • Inngest: Every step is a billable execution, so a three-step workflow costs three times what the run count implies, and the free plan allows five concurrent steps.

7 sourced criteria separate them — see where, with sources, below.

Visit Azure Queue Storage documentationVisit Inngest documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionAzure Queue StorageInngest
Pricing
Pricing modelPer 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.Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.
Queues
Included per monthNone 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.50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.
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.
4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.
Message retentionMessages 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.Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.
Maximum delay
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.
Step sleeps up to 1 year on paid plans; the free plan supports sleeps up to 7 days.
Compliance
SOC 2Listed 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; report available on request via the trust center.
HIPAAListed among Azure's compliance offerings (HIPAA) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.HIPAA BAAs offered as an add-on for healthcare compliance (Enterprise column of the pricing table).

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

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.
Inngest
Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.
Sources (2) →
  • Azure Retail Prices API — Queues v2, eastus ↗

    “"LRS Class 1 Operations", "10K", 0.004 [...] "ZRS Class 2 Operations", "10K", 0.004 [...] "GRS Class 1 Operations", "10K", 0.008”

    Read 2026-09-06 · official pricing

  • Pricing — Inngest ↗

    “TOTAL EXECUTIONS PER MONTH (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] 500 MB span data ingested [...] 10K scores [...] 500k events ingested [...] 50 realtime connections”

    Read 2026-09-06 · official 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.
Inngest
50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.
Sources (2) →
  • Azure Retail Prices API — Queues v2, eastus ↗

    “"productName": "Queues v2", "meterName": "LRS Class 1 Operations", "unitOfMeasure": "10K", "retailPrice": 0.004”

    Read 2026-09-06 · official pricing

  • Pricing — Inngest ↗

    “50k executions [...] 1M executions included Pay as you go up to 20M [...] (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] A single durable function run or step execution”

    Read 2026-09-06 · official 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.

Inngest

4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.

Sources (2) →

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.
Inngest
Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.
Sources (2) →
  • Azure Retail Prices API — Queues v2, eastus ↗

    “"meterName": "LRS Data Stored", "unitOfMeasure": "1 GB/Month", "retailPrice": 0.045”

    Read 2026-09-06 · official pricing

  • Pricing — Inngest ↗

    “100k queue depth [...] 1M+ queue depth [...] Granular tracing, metrics, alerts + 7 day trace retention [...] Advanced tracing, metrics, alerts + 90 day trace retention”

    Read 2026-09-06 · official pricing

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.

Inngest

Step sleeps up to 1 year on paid plans; the free plan supports sleeps up to 7 days.

Sources (2) →

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.
Inngest
SOC 2 Type II compliant; report available on request via the trust center.
Sources (2) →

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.
Inngest
HIPAA BAAs offered as an add-on for healthcare compliance (Enterprise column of the pricing table).
Sources (2) →

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

Documented by only one.

These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.

Free tierInngest: Yes
Entry paid planInngest: $99/month for Pro, described as a starting price with usage above the included allowance billed on top.
RegionsInngest: All customer data hosted on AWS databases located in the United States; no other region offered on the security page.
ConcurrencyInngest: 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise.
ISO 27001Azure 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.
PCI DSSAzure 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 restInngest: All data in Inngest databases is encrypted at rest and in transit; optional encryption middleware lets you bring your own key.
Customer-managed keysInngest: Bring-your-own-key via SDK encryption middleware that encrypts payloads client-side before they reach Inngest; not a server-side KMS option.
Role-based access controlInngest: SAML, RBAC and audit trails listed as Enterprise plan features.
04.

Questions this comparison answers.

Should I choose Azure Queue Storage or Inngest?

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 Inngest if Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

Provider pages

Azure Queue StorageMicrosoft's managed queue, billed per 10,000 operations with queued messages charged as stored data.InngestDurable execution platform where the billable unit is a function or step execution rather than a queued message.

Related comparisons

Amazon SQS vs Azure Queue StorageAmazon SQS vs InngestAzure Queue Storage vs Google Cloud Pub/SubAzure Queue Storage vs HatchetAzure Queue Storage vs Upstash QStashAzure Queue Storage vs TemporalAzure Queue Storage vs Trigger.devAzure Queue Storage vs Zeplo

Every page here is sourced and dated.