List Wurk on AlternativeTo (alternativeto.net)
Why this directory, specifically
AlternativeTo exists to answer one question: "what can I use instead of this paid thing?" Wurk's entire positioning is the Pro and Enterprise feature sets, in the free gem, MIT-licensed. That is not a loose fit — it is the exact query the site is built to serve, and people arrive there already intending to switch.
Of everything in the OSS distribution queue, this is the best-matched channel Wurk has.
⚠️ The real gate is the review queue, not the account
Corrected 2026-08-20 against AlternativeTo's own FAQ — an earlier version of this issue cited a
7-day account-age rule taken from a third-party guide. That is not what the site says.
- Prerequisite is only email verification. Sign up, verify, and you can submit immediately.
- The free review queue is "at least a few months" before anyone looks at a submission.
- Priority Review costs $5 and is "usually reviewed within 1-2 business days." Refundable
while still queued, non-refundable once review begins. Explicitly: paying moves you up the
queue, it does not buy approval — the same standards apply either way.
- Some submissions are expedited free for "power users and long-time contributors." We are
neither, so that does not apply to us.
Pay the $5. A few months of queue versus two business days, for the price of a coffee, on the
best-matched directory Wurk has. There is no argument for waiting.
⚠️ Approval risk — read before writing the description
AlternativeTo openly declines: basic tools, AI wrappers, apps "indistinguishable from what's
already widely available", and submissions in over-saturated categories. Two consequences for
how we write this:
- Do not lead with "AI-maintained." It is true, it is central to our story everywhere else,
and here it risks pattern-matching straight into the "AI wrapper" decline bucket by a reviewer
skimming. Wurk is a Ruby background-job system. Lead with that. The AI-maintenance angle can
appear as a single sentence near the end, or not at all in the first submission.
- Make the Pro/Enterprise-for-free angle unmissable in the first two lines. "Another Sidekiq
clone" reads as indistinguishable from what's already available and gets declined. "The paid
tiers' feature set, in the free MIT gem" is a specific, checkable claim that is not
over-saturated — it is close to unique.
Fields to fill
| Field |
Value |
| Name |
Wurk |
| Tagline |
Drop-in replacement for Sidekiq, Pro and Enterprise features included, free and MIT |
| Website |
https://developerz-ai.github.io/wurk/ |
| Repo |
https://github.com/developerz-ai/wurk |
| Live demo |
https://wurk.demo.developerz.ai/wurk |
| License |
Open Source — MIT |
| Platforms |
Self-Hosted, Linux, Mac, Windows (it is a Ruby gem; self-hosted is the meaningful one) |
| Pricing |
Free |
| Categories/tags |
background jobs, job queue, task queue, ruby, rails, redis, developer tools |
Logo: docs/assets/wurk-logo.png in the repo. Screenshots: the dashboard is the strongest visual — live SSE charts and per-job progress. Grab two or three from the live demo.
Suggested description
Wurk is a background job system for Ruby and Rails that is wire-compatible with
Sidekiq — same Redis keys, same job JSON, same Ruby DSL. Swapping one line in your
Gemfile keeps existing jobs, batches, rate limiters, cron entries and live Redis
data working untouched.
The features that Sidekiq splits across its paid Pro and Enterprise tiers ship in
the same free gem, with no license key and no tiers: batches, global concurrency
limits across a cluster, cron scheduling, and a live web dashboard with SSE charts
and per-job progress.
Also included: Kubernetes /live and /ready probes as a config line, a bearer-scoped
HTTP API so non-Ruby services can enqueue and inspect, OpenTelemetry trace
propagation from client to server, and a fork-based multi-core swarm worker model.
Ruby >= 3.2. MIT licensed. Wurk is independent and is not affiliated with or
endorsed by Sidekiq or its maintainers.
Which products to list it as an alternative to
Primary — this is the whole point:
- Sidekiq
- Sidekiq Pro
- Sidekiq Enterprise
Secondary, if the site has entries for them:
- Resque, Delayed Job, GoodJob, Solid Queue, Que
⚠️ Copy rules — non-negotiable, we have been burned on both
1. Never claim Wurk is faster. It is not. Measured at roughly 0.87×–1.02× versus stock Sidekiq: parity on CPU and I/O bound work, still behind on framework overhead (noop) and boot time. The README says this plainly and docs/benchmarks.md publishes the method and the reproduction command.
If the form has room for it, saying so is an asset, not a liability — "we benchmarked ourselves against the incumbent and published losing numbers" is the most credible thing either brand owns. Do not hide it and do not lead with it.
2. Never name or reference the Sidekiq maintainer. Talk about the product and its pricing tiers, never the person. This drew real backlash on r/ruby on 2026-08-07. The README's framing is the correct register and can be reused: "Wurk implements Sidekiq's API because it is a genuinely good API. Sidekiq is human-maintained and funds that work through its paid tiers; Wurk is AI-maintained, which is what lets the same surface be free software."
3. Keep the non-affiliation line. It is already in the README and it belongs in the listing.
After it is published
AlternativeTo ranks alternatives by community votes, so a fresh listing sits near the bottom of the Sidekiq page until it gets some. Do not manufacture votes — vote rings are exactly what gets a listing removed, and getting caught gaming a directory would cost far more than the placement is worth, given the honesty angle is the whole brand. Genuine users voting because they were told the listing exists is fine; anything organised is not.
Reasonable follow-ups once live: mention the listing in the repo README or docs, and let it come up naturally in the Ruby community channels already in the distribution queue.
Also from the FAQ: user profiles may not advertise products — violators get blocked. So set up the account as a normal person's profile, not as a Wurk billboard.
Linking it as an alternative is a separate step from submitting the app. Once the Wurk page exists, go to each target page (Sidekiq, Sidekiq Pro, Sidekiq Enterprise) → "Contribute to this page" → "Suggest Alternatives" → add Wurk.
Acceptance
Context
Part of the OSS distribution queue in the mmarketing.site repo (marketing/campaigns/daily-playbook.md, §4 Lane B Tier 1). Nothing blocks this — it is independent of the Show HN and MCP-registry work.
List Wurk on AlternativeTo (alternativeto.net)
Why this directory, specifically
AlternativeTo exists to answer one question: "what can I use instead of this paid thing?" Wurk's entire positioning is the Pro and Enterprise feature sets, in the free gem, MIT-licensed. That is not a loose fit — it is the exact query the site is built to serve, and people arrive there already intending to switch.
Of everything in the OSS distribution queue, this is the best-matched channel Wurk has.
Corrected 2026-08-20 against AlternativeTo's own FAQ — an earlier version of this issue cited a
7-day account-age rule taken from a third-party guide. That is not what the site says.
while still queued, non-refundable once review begins. Explicitly: paying moves you up the
queue, it does not buy approval — the same standards apply either way.
neither, so that does not apply to us.
Pay the $5. A few months of queue versus two business days, for the price of a coffee, on the
best-matched directory Wurk has. There is no argument for waiting.
AlternativeTo openly declines: basic tools, AI wrappers, apps "indistinguishable from what's
already widely available", and submissions in over-saturated categories. Two consequences for
how we write this:
and here it risks pattern-matching straight into the "AI wrapper" decline bucket by a reviewer
skimming. Wurk is a Ruby background-job system. Lead with that. The AI-maintenance angle can
appear as a single sentence near the end, or not at all in the first submission.
clone" reads as indistinguishable from what's already available and gets declined. "The paid
tiers' feature set, in the free MIT gem" is a specific, checkable claim that is not
over-saturated — it is close to unique.
Fields to fill
WurkLogo:
docs/assets/wurk-logo.pngin the repo. Screenshots: the dashboard is the strongest visual — live SSE charts and per-job progress. Grab two or three from the live demo.Suggested description
Which products to list it as an alternative to
Primary — this is the whole point:
Secondary, if the site has entries for them:
1. Never claim Wurk is faster. It is not. Measured at roughly 0.87×–1.02× versus stock Sidekiq: parity on CPU and I/O bound work, still behind on framework overhead (noop) and boot time. The README says this plainly and
docs/benchmarks.mdpublishes the method and the reproduction command.If the form has room for it, saying so is an asset, not a liability — "we benchmarked ourselves against the incumbent and published losing numbers" is the most credible thing either brand owns. Do not hide it and do not lead with it.
2. Never name or reference the Sidekiq maintainer. Talk about the product and its pricing tiers, never the person. This drew real backlash on r/ruby on 2026-08-07. The README's framing is the correct register and can be reused: "Wurk implements Sidekiq's API because it is a genuinely good API. Sidekiq is human-maintained and funds that work through its paid tiers; Wurk is AI-maintained, which is what lets the same surface be free software."
3. Keep the non-affiliation line. It is already in the README and it belongs in the listing.
After it is published
AlternativeTo ranks alternatives by community votes, so a fresh listing sits near the bottom of the Sidekiq page until it gets some. Do not manufacture votes — vote rings are exactly what gets a listing removed, and getting caught gaming a directory would cost far more than the placement is worth, given the honesty angle is the whole brand. Genuine users voting because they were told the listing exists is fine; anything organised is not.
Reasonable follow-ups once live: mention the listing in the repo README or docs, and let it come up naturally in the Ruby community channels already in the distribution queue.
Also from the FAQ: user profiles may not advertise products — violators get blocked. So set up the account as a normal person's profile, not as a Wurk billboard.
Linking it as an alternative is a separate step from submitting the app. Once the Wurk page exists, go to each target page (Sidekiq, Sidekiq Pro, Sidekiq Enterprise) → "Contribute to this page" → "Suggest Alternatives" → add Wurk.
Acceptance
Context
Part of the OSS distribution queue in the
mmarketing.siterepo (marketing/campaigns/daily-playbook.md, §4 Lane B Tier 1). Nothing blocks this — it is independent of the Show HN and MCP-registry work.