Development, with fewer loose ends

Your project.
Already running.

Your API, database, and workers, started with one command. Pitchfork handles readiness, retries, and logs so you can get back to work.

Get started Build your first project

mise use -g pitchforkMore ways to install

~/projects/my-appexample session

$ pitchfork start api

redisready:6379

└─ dependency ready. Starting api.

apiready:3000

$ pitchfork start api

Already running. You're good to go.

Any languageOne TOML fileProject-awareOpen source · MIT

A little config. A lot less juggling.

Check in the setup.
Check off the busywork.

Put the commands you already run in pitchfork.toml. Give each service a name, declare what it needs, and share the setup with your team.

1
Describe your services
Commands, environment, and dependencies in one place.
2
Start what you need
Dependencies start first. Running services stay running.
3
Work from any terminal
Inspect, restart, or stop services whenever you need to.

Walk through this setup

pitchfork.tomlproject config

[daemons.redis]
run = "redis-server --port $PORT"
port = 6379
ready_cmd = "redis-cli -p $PORT ping"

[daemons.api]
run = "node server.js"
port = 3000
depends = ["redis"]
ready_http = "http://localhost:3000/health"
retry = 3

Bring your own commands. Pitchfork takes care of their lifecycle.

Made for the way you develop

Less process management.
More making things.

Start once. Stay ready.

Run a command again without launching a duplicate. Wait for dependencies to accept requests before starting the next service.

Define readiness

Let services follow you.

Enter a project and start its services. Leave the last session and let them stop. Keep separate names for separate worktrees.

Connect your shell

Keep the feedback loop short.

Restart after a source edit, retry a crashed worker, or catch a service that is running but no longer responding.

Keep services healthy

Give every service a home.

Assign ports, handle conflicts, and use a stable local URL even when the underlying port changes.

Set up local URLs

See what is happening.

Follow logs across services. Filter structured output by level or field. Inspect processes in a terminal or browser dashboard.

Find the right logs

Use the tools you have.

Run shell commands in any language, activate your mise environment, or connect an assistant through the built-in MCP server.

Explore integrations

From the big picture to the last log line

A place for every process.

See what is running, find what failed, and open the logs.
Use pitchfork tui in your terminal or enable the web dashboard.

Terminal dashboard Web dashboard

Pitchfork web dashboard showing daemon status and controls

Summon your daemons.

Then get on with your day.

Run your first daemon Browse the CLI

Your project.Already running.

Check in the setup.Check off the busywork.

Less process management.More making things.