Softwr

Developer Tools · head to head

Cortex vs Hatchet

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Hatchet logo

Hatchet

Automation Integration

Postgres-backed distributed task queue and workflow engine for Python, TypeScript and Go

From
Free
Free plan
Yes

The short version

  • Hatchet starts at $500/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only Hatchet lists postgres-backed queue.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and Hatchet actually diverge.

Attributes where Cortex and Hatchet differ
AttributeCortexHatchet
Starting priceOn requestFree
Pricing modelQuotePer month by task run count
Free tierNoYes
PlatformsWeb, APILinux, Self-hosted, Web
CategoryDeveloper ToolsAutomation Integration

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

Only in Hatchet

  • Postgres-backed queue
  • Durable execution
  • DAG workflows
  • Concurrency and fairness
  • Rate limiting
  • Cron and scheduling
  • Multi-language SDKs
  • Self-hosting

What people use each for

The jobs each tool is most often brought in to do.

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Hatchet
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Hatchet
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Hatchet
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Hatchet

Hatchet

  • An AI product running long agent pipelines that must survive worker restarts and resume mid-workflownot Cortex
  • A team that outgrew Celery and wants concurrency keys, fairness and rate limiting without building themnot Cortex
  • An engineering group that wants durable execution self-hosted with no datastore beyond the Postgres they already runnot Cortex
  • A multi-tenant SaaS that needs one noisy customer's jobs not to starve everyone else'snot Cortex

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract

Hatchet

  • Postgres as the queue backend simplifies operations but sets a throughput ceiling, and very high task rates require database tuning or partitioning work that a purpose-built queue would not demand
  • Data retention on the managed tiers is three days on Team and seven on Scale, which is short for debugging intermittent failures and forces you to export run history elsewhere
  • The step from the free tier to Team is 500 US dollars a month plus usage, which is a large increment for a small team that simply needs a production SLA
  • Hatchet is a young company in a category with Temporal, Inngest and cloud-native alternatives already established, so ecosystem, hiring pool and third-party material are all thin
  • Self-hosting the MIT engine is realistic but you then run the engine, its Postgres and its workers yourself, and the managed features such as audit logs and support are not part of that

Pricing, plan by plan

Cortex

On request
  • CortexOn request
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Hatchet

Free
  • DeveloperFree
    • First 100,000 task runs included
    • $10 per million task runs after
    • No card required
  • Team$500/mo
    • Usage billed on top of the base fee
    • 10 users and 5 tenants
    • 3 day data retention
  • Scale$1,000/mo
    • Unlimited users and tenants
    • 7 day data retention
    • Audit logs
  • EnterpriseOn request
    • 300 million plus runs a month
    • Latency guarantees and custom SLAs
    • SSO and audit logging

Which should you pick?

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.

Choose Hatchet if

  • You need postgres-backed queue.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web.
  • You also want durable execution.

Questions people ask

Is Cortex or Hatchet better?
Neither clearly leads. Cortex starts at On request and Hatchet at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Hatchet?
Hatchet has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Hatchet.
Does Cortex or Hatchet run on more platforms?
Cortex runs on Web, API. Hatchet runs on Linux, Self-hosted, Web.
Can I use Hatchet for free?
Yes. Hatchet has a free tier, so you can try it without paying. Cortex starts at On request.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Hatchet is typically brought in for.
What can Cortex do that Hatchet cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Hatchet covers Postgres-backed queue, Durable execution, DAG workflows, Concurrency and fairness.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

Hatchet: Is Hatchet open source?

Yes, the engine is MIT licensed and can be self-hosted, with a managed cloud offered alongside.

Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

Hatchet: What does it cost?

Free for the first 100,000 task runs, then 10 US dollars per million. Team is 500 US dollars a month plus usage; Scale is 1,000.

Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

Hatchet: Why Postgres as the queue?

So durable task state lives in a database your team already backs up, replicates and can inspect with SQL, instead of a second system.

Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Hatchet: How does it compare with Temporal?

Lighter to adopt and operate, with a much smaller ecosystem and a lower throughput ceiling from the Postgres backend.

Share

Related pages

Other head to heads