Nubo

background workers

The script that never stops.
Running. Restarting. Logged.

Push a worker like any other Frame. It pulls jobs off a queue, processes webhooks, runs your scheduled tasks, and when something goes sideways at 3am, Nubo restarts it before you notice.

what workers actually need

A place to run. And to recover from.

Same Frame, same deploy flow, same dashboard. Workers just don't have a URL. Everything else is identical.

  • Restarts on crash

    If a worker dies, Nubo brings it back. No PagerDuty page for an OOM at 3am.

  • Frame-level logs

    Tail the worker's output from the same dashboard you deploy from. Search, filter, scroll back.

  • Replicas when you need them

    Set min and max on the worker, Nubo Cloud scales between them as the queue grows.

  • Secrets, scoped per Frame

    DATABASE_URL, REDIS_URL, API tokens, encrypted at rest, never in your repo.

what people ship as workers

The half of your stack with no URL.

  • queues

    Queue processors

    Pull jobs off SQS, Redis, Postgres. Process, ack, sleep.

  • schedulers

    Scheduled jobs

    The script you run hourly. Now it just runs.

  • webhooks

    Webhook receivers

    Stripe, GitHub, Slack. Verify, store, route.

  • etl

    ETL & sync

    Pull from one system, transform, drop into another.

  • consumers

    Stream consumers

    Tail Kafka, NATS, Pub/Sub. React to events as they land.

  • agents

    Headless agents

    Long-running scripts that watch, scrape, or talk to LLMs.

when something dies

Workers come back.
You don't get paged.

OOM, panic, exit 1, whatever. Nubo restarts the Frame and starts the loop again. The crash shows up in the dashboard, not your phone.

jobs / queue-worker live
[14:42:08] info  processed job 0x4f1a · queue=email
[14:42:09] info  processed job 0x4f1b · queue=email
[14:42:11] error uncaught exception: connection reset
[14:42:11] fatal process exited with code 1
[14:42:12] nubo  worker exited · restarting (attempt 1)
[14:42:14] nubo  worker online · resumed queue
[14:42:15] info  processed job 0x4f1c · queue=email

stop reading

Got an idea?
Ship it tonight.

Sign up with GitHub, pick a repo, and we'll take it from there. Seven days on the house, no card and no sales call required.