Amazon SQS vs Hatchet
SEPT 2026 auditA comparison of Amazon SQS and Hatchet built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Amazon SQS if…
AWS-resident systems that want a queue with a permanent free million requests a month and no capacity to plan — SQS scales without a throughput setting to choose.
Editorial · Palash Bagchi · approved
Choose Hatchet if…
Task workloads that want a countable unit — 100,000 runs free and $10 per million is the least ambiguous pricing in this category.
Editorial · Palash Bagchi · approved
Consider something else if…
- Amazon SQS: Billing is per request rather than per message, and a 1 MiB payload counts as sixteen, so chatty polling or large messages cost far more than the message count suggests.
- Hatchet: The jump from free to the first paid tier is $500 a month, which buys retention and throughput rather than volume, so a small production workload pays a lot for features it may not need.
11 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Amazon SQS 0
Hatchet 0
At a glance.
| Criterion | Amazon SQS | Hatchet |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Entry paid plan | No paid plan or minimum fee; billed per request after the free 1 million requests a month. | $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month. |
| Pricing model | Per request, not per message: every API action counts, and a 1 MiB payload is billed as 16 requests. FIFO queues cost $0.50 per million against standard's $0.40 in us-east-1, and fair queue requests add $0.10 per million on top of the standard rate. | Usage-first: every plan is "free + usage" or "$N/mo + usage" at $10 per million task runs, with the plan fee buying users, tenants, retention and throughput rather than volume. Self-hosting is offered with support on the enterprise tier. |
| Infrastructure | ||
| Regions | 34 commercial AWS Regions plus 2 AWS GovCloud (US) Regions listed in the SQS service endpoints table. | 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2. |
| Queues | ||
| Included per month | 1,000,000 requests a month free, permanently and across all regions. Beyond that, standard queues are $0.40 per million in us-east-1, falling to $0.30 above 100 billion and $0.24 above 200 billion. | 100,000 task runs included free, then $10 per million. The cleanest per-unit rate in this category — Hatchet counts task runs where Cloudflare counts 64 KB operations and Inngest counts steps. |
| Message retention | 4 days by default; configurable from 60 seconds up to 14 days per queue. | 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. |
| Concurrency | Approximately 120,000 in-flight messages per standard queue (received but not yet deleted); API call rate on standard queues is nearly unlimited. | 500 requests per second of throughput on Team; higher tiers are not published as a number. |
| Compliance | ||
| SOC 2 | Listed as SOC-compliant on AWS's own compliance scope page. | SOC 2 Type II compliant; reports available through the Hatchet Trust Center. |
| HIPAA | Listed as a HIPAA-eligible service on AWS's own reference page. | HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA. |
| GDPR / data residency | AWS customers can process personal data on all AWS services in compliance with GDPR, and choose the storage type and geographic region for their data. | GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland). |
| Encryption at rest | Server-side encryption of queue contents with SQS-managed keys (SSE-SQS) or AWS KMS keys (SSE-KMS). | Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit. |
| Role-based access control | IAM identity-based policies on users, groups and roles plus resource-based queue policies control access to queues and actions. | Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member. |
Where they differ.
Entry paid plan
- Amazon SQS
- No paid plan or minimum fee; billed per request after the free 1 million requests a month.
- Hatchet
- $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
Sources (2) →Sources ↓
- Amazon SQS Pricing ↗
“With AWS SQS, you pay only for what you use and there is no minimum fee.”
Read 2026-09-13 · official pricing
- Pricing — Hatchet ↗
“Team $500 /mo + usage Everything in Developer, plus: 10 users & 5 tenants 3-day retention 500 RPS throughput [...] Scale $1,000 /mo + usage”
Read 2026-09-06 · official pricing
Pricing model
- Amazon SQS
- Per request, not per message: every API action counts, and a 1 MiB payload is billed as 16 requests. FIFO queues cost $0.50 per million against standard's $0.40 in us-east-1, and fair queue requests add $0.10 per million on top of the standard rate.
- Hatchet
- Usage-first: every plan is "free + usage" or "$N/mo + usage" at $10 per million task runs, with the plan fee buying users, tenants, retention and throughput rather than volume. Self-hosting is offered with support on the enterprise tier.
Sources (2) →Sources ↓
- AWS Price List API — AWSQueueService, us-east-1 ↗
“"$0.50 per million Amazon SQS FIFO requests in Tier1 in US East" [...] "$0.40 per million Amazon SQS standard requests in Tier1" [...] "$0.10 per million Amazon SQS fair queue requests in US East"”
Read 2026-09-06 · official pricing
- Pricing — Hatchet ↗
“Developer Free + usage $10 per 1M task runs [...] Team $500 /mo + usage [...] SSO Audit logging Bring your own cloud Self-host support Custom SLAs”
Read 2026-09-06 · official pricing
Regions
34 commercial AWS Regions plus 2 AWS GovCloud (US) Regions listed in the SQS service endpoints table.
3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2.
Sources (2) →Sources ↓
- Amazon Simple Queue Service endpoints and quotas - AWS General Reference ↗
“Region Name Region Endpoint Protocol US East (Ohio) us-east-2 sqs.us-east-2.amazonaws.com [...] AWS GovCloud (US-West) us-gov-west-1 sqs.us-gov-west-1.amazonaws.com”
Read 2026-09-13 · official docs
- Region Availability - Hatchet Documentation ↗
“aws-us-west-2 Oregon (US) Live aws-us-east-1 N. Virginia (US) Live aws-eu-west-1 Ireland Live aws-ap-southeast-2 Sydney Private Beta”
Read 2026-09-13 · official docs
Included per month
- Amazon SQS
- 1,000,000 requests a month free, permanently and across all regions. Beyond that, standard queues are $0.40 per million in us-east-1, falling to $0.30 above 100 billion and $0.24 above 200 billion.
- Hatchet
- 100,000 task runs included free, then $10 per million. The cleanest per-unit rate in this category — Hatchet counts task runs where Cloudflare counts 64 KB operations and Inngest counts steps.
Sources (2) →Sources ↓
- AWS Price List API — AWSQueueService, us-east-1 ↗
“"First 1,000,000 Amazon SQS Requests per month are free" [...] "$0.40 per million Amazon SQS standard requests in Tier1 in US East" [...] "$0.30 per million ... Tier2" [...] "$0.24 per million ... Tier3"”
Read 2026-09-06 · official pricing
- Pricing — Hatchet ↗
“Developer Free + usage $10 per 1M task runs First 100,000 runs included”
Read 2026-09-06 · official pricing
Message retention
4 days by default; configurable from 60 seconds up to 14 days per queue.
3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling.
Sources (2) →Sources ↓
- Amazon SQS message quotas - Amazon Simple Queue Service ↗
“Message retention By default, a message is retained for 4 days. The minimum is 60 seconds (1 minute). The maximum is 1,209,600 seconds (14 days).”
Read 2026-09-13 · official docs
- Pricing — Hatchet ↗
“10 users & 5 tenants 3-day retention 500 RPS throughput”
Read 2026-09-06 · official pricing
Concurrency
- Amazon SQS
- Approximately 120,000 in-flight messages per standard queue (received but not yet deleted); API call rate on standard queues is nearly unlimited.
- Hatchet
- 500 requests per second of throughput on Team; higher tiers are not published as a number.
Sources (2) →Sources ↓
- Amazon SQS standard queue quotas - Amazon Simple Queue Service ↗
“For most standard queues (depending on queue traffic and message backlog), there can be a maximum of approximately 120,000 in flight messages (received from a queue by a consumer, but not yet deleted from the queue).”
Read 2026-09-13 · official docs
- Pricing — Hatchet ↗
“3-day retention 500 RPS throughput See all features”
Read 2026-09-06 · official pricing
SOC 2
- Amazon SQS
- Listed as SOC-compliant on AWS's own compliance scope page.
- Hatchet
- SOC 2 Type II compliant; reports available through the Hatchet Trust Center.
Sources (2) →Sources ↓
- AWS Services in Scope for SOC ↗
“Amazon Simple Queue Service (SQS) listed with a checkmark on the SOC services-in-scope page.”
Read 2026-09-12 · official site
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant. Company-level security practices, compliance reports, and security documentation are available at the Hatchet Trust Center .”
Read 2026-09-13 · official docs
HIPAA
- Amazon SQS
- Listed as a HIPAA-eligible service on AWS's own reference page.
- Hatchet
- HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA.
Sources (2) →Sources ↓
- AWS HIPAA Eligible Services Reference ↗
“Amazon Simple Queue Service (SQS) listed on the HIPAA-eligible services reference page.”
Read 2026-09-12 · official site
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant.”
Read 2026-09-13 · official docs
GDPR / data residency
- Amazon SQS
- AWS customers can process personal data on all AWS services in compliance with GDPR, and choose the storage type and geographic region for their data.
- Hatchet
- GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland).
Sources (2) →Sources ↓
- GDPR — Amazon Web Services ↗
“AWS customers can use all AWS services to process personal data [...] in compliance with the GDPR. [...] Customers have control of their customer data. With AWS, customers can: Determine where their customer data will be stored, including the type of storage and geographic region of that storage.”
Read 2026-09-12 · official site
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant.”
Read 2026-09-13 · official docs
Encryption at rest
- Amazon SQS
- Server-side encryption of queue contents with SQS-managed keys (SSE-SQS) or AWS KMS keys (SSE-KMS).
- Hatchet
- Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit.
Sources (2) →Sources ↓
- Encryption at rest in Amazon SQS - Amazon Simple Queue Service ↗
“SSE protects the contents of messages in queues using SQS-managed encryption keys (SSE-SQS) or keys managed in the AWS Key Management Service (SSE-KMS).”
Read 2026-09-13 · official docs
- Security - Hatchet Documentation ↗
“Encryption at rest : data stored in Hatchet Cloud is encrypted at rest.”
Read 2026-09-13 · official docs
Role-based access control
- Amazon SQS
- IAM identity-based policies on users, groups and roles plus resource-based queue policies control access to queues and actions.
- Hatchet
- Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member.
Sources (2) →Sources ↓
- Overview of managing access in Amazon SQS - Amazon Simple Queue Service ↗
“An account administrator can attach permissions policies to IAM identities (users, groups, and roles), and some services (such as Amazon SQS) also support attaching permissions policies to resources.”
Read 2026-09-13 · official docs
- User Roles - Hatchet Documentation ↗
“Every user in a tenant has a role that controls what they can do in the dashboard and REST API. Roles are hierarchical: each role can do everything the roles below it can.”
Read 2026-09-13 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
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.
Questions this comparison answers.
Entry paid plan: Amazon SQS or Hatchet?
Amazon SQS: No paid plan or minimum fee; billed per request after the free 1 million requests a month.
Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
Should I choose Amazon SQS or Hatchet?
Pick Amazon SQS if AWS-resident systems that want a queue with a permanent free million requests a month and no capacity to plan — SQS scales without a throughput setting to choose.
Pick Hatchet if Task workloads that want a countable unit — 100,000 runs free and $10 per million is the least ambiguous pricing in this category.
