For AI agents: the complete documentation index is available at /worker-manager/llms.txt, the full documentation bundle is available at /worker-manager/llms-full.txt, and this page is available as Markdown at /worker-manager/server-adapters/index.md.

Server Adapters

One server adapter per framework. The core @worker-manager/api package is shared. Pick your framework below.

Tip

Try the live demo first. All 9 adapters serve the same UI.

Adapter matrix

FrameworkPackageDocs
Express@worker-manager/expressExpress →
Fastify@worker-manager/fastifyFastify →
NestJS@worker-manager/nestjsNestJS →
Koa@worker-manager/koaKoa →
Hapi@worker-manager/hapiHapi →
Hono@worker-manager/honoHono →
H3@worker-manager/h3H3 →
Elysia@worker-manager/elysiaElysia →
Bun@worker-manager/bunBun →

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:

  1. Create a server adapter and set its base path (setBasePath(), or constructor options for Elysia).
  2. Call createWorkerManagerBoard({ queues, serverAdapter }) with your queue adapters.
  3. Register the adapter with your app (Express app.use, Fastify app.register, Bun spreads getRoutes() into Bun.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.