Softwr

Automation Integration · head to head

Hatchet vs Split

Hatchet logo

Hatchet

Automation Integration

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

From
Free
Free plan
Yes
Split logo

Split

Testing

Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME

From
On request
Free plan
No

The short version

  • Hatchet starts at $500/mo; Split prices on request.
  • Only Hatchet lists postgres-backed queue; only Split lists feature flags with targeting.
  • Prices and features on this page were last checked on 20 November 2026.

How do Hatchet and Split differ?

Hatchet and Split differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Hatchet and Split actually diverge.

Attributes where Hatchet and Split differ
AttributeHatchetSplit
Starting priceFreeOn request
Pricing modelPer month by task run countQuote
Free tierYesNo
PlatformsLinux, Self-hosted, WebWeb, API, iOS, Android, Windows
CategoryAutomation IntegrationTesting

Which features does each one have?

They share no listed features; 8 appear only for Hatchet and 8 only for Split. 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 Hatchet

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

Only in Split

  • Feature flags with targeting
  • Metrics impact engine
  • Guardrail metrics
  • Statistical significance testing
  • Event ingestion
  • SDKs and streaming updates
  • Audit and approvals
  • Harness platform integration

What is each one used for?

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

Hatchet

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

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Hatchet
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Hatchet
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Hatchet
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Hatchet

Where do Hatchet and Split fall short?

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

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

Split

  • Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
  • Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
  • The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
  • Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
  • As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product

How much do Hatchet and Split cost?

Hatchet has a free plan, with paid plans from $500/mo; Split is priced on request. Plan by plan below, from each vendor's own pricing page.

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

Split

On request
  • Harness FreeFree
    • Harness Open Source and community support
    • Intended for individuals and small teams
    • Feature management capability limited at this tier
  • Harness EssentialsOn request
    • Bundled DevOps modules including CI, CD, IaC and security testing
    • Standard support
    • Pricing requires contacting sales
  • Harness EnterpriseOn request
    • Mix and match from 15 or more modules including Feature Management and Experimentation
    • Premier support with a dedicated account manager
    • Higher pipeline concurrency and organisation limits

Which should you pick?

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.

Choose Split if

  • You need feature flags with targeting.
  • You work on Web, API, iOS, Android, Windows.
  • You also want metrics impact engine.

Questions people ask

Is Hatchet or Split better?
Neither clearly leads. Hatchet starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hatchet or Split?
Hatchet has a free tier; the other does not. Paid plans start at Free for Hatchet and On request for Split.
Does Hatchet or Split run on more platforms?
Hatchet runs on Linux, Self-hosted, Web. Split runs on Web, API, iOS, Android, Windows.
Can I use Hatchet for free?
Yes. Hatchet has a free tier, so you can try it without paying. Split starts at On request.
What is Hatchet best used for?
Hatchet is most often used for an ai product running long agent pipelines that must survive worker restarts and resume mid-workflow, a team that outgrew celery and wants concurrency keys, fairness and rate limiting without building them, an engineering group that wants durable execution self-hosted with no datastore beyond the postgres they already run, a multi-tenant saas that needs one noisy customer's jobs not to starve everyone else's. Of those, an ai product running long agent pipelines that must survive worker restarts and resume mid-workflow and a team that outgrew celery and wants concurrency keys, fairness and rate limiting without building them are not what Split is typically brought in for.
What can Hatchet do that Split cannot?
Hatchet covers Postgres-backed queue, Durable execution, DAG workflows, Concurrency and fairness. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Hatchet: Is Hatchet open source?

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

Split: Is Split still called Split?

It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.

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.

Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

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.

Split: What does it do that a plain flag service does not?

It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.

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.

Split: Do we need a lot of traffic?

Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.

Share

Related pages

Other head to heads