Running Hatchet Locally
There are different options to run Hatchet on your own machine:
| Option | Best for | Requires |
|---|---|---|
| Embedded mode | Local development and CI | Nothing (no account or Docker) |
| Hatchet CLI | A full local stack with the dashboard | Docker |
| Hatchet Lite | A single self-managed container | Docker |
| Docker Compose | A local stack with separate services | Docker |
| Kubernetes | Production-like self-hosted deployments | A cluster |
Embedded mode
Embedded mode runs a full Hatchet engine and Postgres instance from inside your worker process. It needs no account, API token, or Docker, which makes it the fastest path for local development and end-to-end tests in CI.
CLI
Using the CLI command hatchet server start, you can run a full local instance, including the dashboard, using Docker under the hood. Add --disable-auth for a no-auth mode aimed at local development: everything runs as a seeded admin user against the default tenant, so there is no signup step.
Hatchet Lite
Hatchet Lite bundles Hatchet into one container. Use it directly when you want to manage the container yourself (the CLI command above wraps it).
Docker Compose and Kubernetes
Docker Compose runs the stack as separate services for a production-like local environment, while Kubernetes lets you mirror a real, self-hosted deployment.
Last updated on September 1, 2026