Home / Compute
Hatchet
hatchet.runPlatform hostcompute/hatchet-runJSONcomparereport an errorprovider JSON
- Free allowance
- No credit card, and the first 100,000 runs are free; the orchestration runs on a user's own workers, so the free unit is runs against a control plane
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-ratethe first 100,000 runs are free
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | no credit card, and the first 100,000 runs are free; the orchestration runs on a user's own workers, so the free unit is runs against a control plane unit objects; metered on request-count |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) the first 100,000 runs are free source
- write-gated workers run on a user's own platform, so the control plane is free but the compute is not source
not stated |
|---|
| Identity | email 'No credit card required', quoted from hatchet.run read 2026-10-22 |
|---|
| Egress | not stated |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | unknown |
|---|
| Reliability | no reliability event recorded |
|---|
| Notes | The free unit is runs against Hatchet's control plane; the user deploys the workers, and the vendor names hosted container platforms (Railway, Render, ECS) for them. |
|---|
| Evidence note | documented the site was read on 2026-10-22 and states the free allowance and that workers run on a user's own infrastructure. The unit is a run count against a queue, not machine time |
|---|
| Parsed numbers | |
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-02 | hatchet.run | not published |
| 2026-10-22 | hatchet.run | 'Get started for free today. No credit card required and your first 100,000 runs are on us.' with 'Deploy workers on Kubernetes, Porter, Railway, Render, ECS, or any container platform. They automatically connect to Hatchet', quoted |
More fields 5
| keep rate basis | no field in the source |
|---|
| billing model | unclassified |
|---|
| session cap | {"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "a run is a task in a DAG; there is no machine and no session clock"} |
|---|
| free tier kind | one-time-credit |
|---|
| ps | {"gib": null,"price": "the persistence layer holds run state; a user's workers do the work","durability": "run state in the queue","on_stop": true,"on_destroy": false,"retention": "the platform's retention policy"} |
|---|
Unknown values 10
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- limits note: a source was read and is silent on this field
- per object cap stated: a source was read and is silent on this field
- reliability note: nothing of this kind was observed
- retention notes: the field may be stated in a source that was not read
- retention stated: a source was read and is silent on this field
- tooling: a source was read and is silent on this field