Server Adapters
One server adapter per framework. The core @worker-manager/api package is shared. Pick your framework below.
Try the live demo first. All 9 adapters serve the same UI.
Adapter matrix
Sails
No dedicated Sails adapter. Sails runs on Express, so use @worker-manager/express inside a Sails controller. Working example: examples/more/sails.
Next.js
No dedicated Next.js adapter. Mount Worker Manager inside a Next.js API route using the Hono adapter (App Router) or the Express adapter (Pages Router). The Vercel deployment needs a small bit of next.config.js, see Next.js & Vercel and the nextjs/app-router / nextjs/pages-router examples.
Shape
Most adapters follow the same three steps:
- Create a server adapter and set its base path (
setBasePath(), or constructor options for Elysia). - Call
createWorkerManagerBoard({ queues, serverAdapter })with your queue adapters. - Register the adapter with your app (Express
app.use, Fastifyapp.register, Bun spreadsgetRoutes()intoBun.serve, etc.).
Elysia and Bun are a bit different, the adapter pages show exactly what goes where.
See Your first dashboard for a concrete Express walkthrough.