Ukue.com reads as µkue, a micro queue. The u stands in for µ, the micro sign, the same way engineers type microseconds as “us” in their logs. Kue is queue, spelled the way it sounds. It’s four letters, and a developer gets it on the first read.
Behind the name: a job queue that lives in a single file, the way SQLite is a database in a single file. Embed it in an app as a library, or run it as one small binary. Failed jobs get retried with backoff, and a job can wait until tomorrow morning before it runs. The ones that keep failing land on a dead-letter shelf for a person to look at.
Why small teams want it
Sending a welcome email in the background shouldn’t need a second server. Yet that’s where most teams end up: Redis or RabbitMQ running next to the app, with its own upgrades and memory alerts, all to send a few hundred emails a day. A queue in one file removes that whole layer. Back it up by copying a file. Move it to a new server the same way.
That reaches a big crowd: solo founders, agencies running dozens of client sites, internal-tools teams, and edge or IoT builds with no room for a broker at all.
A category without a default
People pay for background jobs. Sidekiq sells Pro and Enterprise licenses to companies already running the free version, and job queues in other languages have paid tiers of their own. Lightweight, SQLite-backed queues are spreading across languages, and none has become the default yet. The first one with a short name people can say out loud has the best shot.
The queue is small. The name should be too.