Deploy your worker
without leaving the chat.
Point Claude Code, Cursor, Codex or any MCP editor at the folder and say deploy. The process stays connected to your queue and keeps state in memory between jobs, with no cold start and no per-invocation bill.
Free for 7 days, then $3/mo. No card to start.
ONE COMMAND · ALWAYS CONSUMING · NO COLD STARTNow it drains
without being asked.
The process stays connected to your queue and keeps state in memory between jobs. No warm-up, no per-invocation charge, and no scheduled ping whose only job is to wake your own service.
Node or Python, your entry point.
Put connection strings in environment variables, encrypted at rest.
No cold starts, no invocation billing, no keep-alive pings.
The bit you are
actually wondering.
How is this different from a serverless function?
A function starts, runs and stops. A worker never stops, so it can hold connections, keep state in memory and consume a queue without waking up first.
Is it cheaper than serverless?
For always-on work, usually yes, because you pay for a fixed slice rather than per wake-up. For genuinely spiky request-shaped work, serverless will be cheaper and you should use it.
What if a job kills the process?
It restarts and resumes consuming. If it crash-loops we stop retrying and tell you, rather than hiding a broken worker behind an automatic restart.
Whatever it built,
this runs it.
A queue consumer is only useful if it is listening. Serverless bills you to wake up; a container is just awake.
You never open a panel.
Connect once, then deploy, read logs, restart and roll back by asking. No API key to copy.
Priced per app,
not per request.
No metering, no surprise invoice. Seven days free to start, and no card until you keep it.
BUILDER for workers. Workers tend to arrive in groups — a queue consumer, a poller, something that cleans up after them. Five slots is usually the shape.
What people ask
before they deploy.
How is this different from a serverless function?
A function starts, runs, and stops. A worker never stops, so it can hold connections, keep state in memory, and consume a queue without waking up first.
The queue is waiting.
Give it a consumer.
$3 a month, always on. First one free for 7 days, no card.
Cursor and VS Code open and install it themselves. For Claude Desktop or claude.ai, paste the URL under Settings → Connectors → Add custom connector.