Background jobs.
Without the overhead.

Your app sends emails on a queue. Processes image uploads in the background. Runs a Celery worker or a Bull job processor. In production, these are separate services. In development, they're "I forgot to start the worker again and wondered why emails aren't sending."

Donk lets you define workers as part of your server configuration. A worker is any command — a Celery process, a custom script, a cron-style task. Workers start with the server, run on schedule or on-demand, and auto-pause when CPU or memory is maxed so your laptop doesn't become unusable.

• Define workers alongside servers in donk.toml
• Cron expressions — run every minute, every hour, at midnight
• On-demand triggers — run once now from the GUI or CLI
• Concurrency limit — max 1 or max N concurrent runs
• Auto-pause when CPU or memory exceeds configurable thresholds
• Workers start with the server, stop with the server
• Dedicated Worker Log tab in the debug console
• VS Code sidebar shows worker status — running, idle, paused, failed