[Question]: Workflow Dev Kit support for Next.js standalone / Docker deployments

Hi Vercel team 👋

I’m experimenting with the new Workflow Dev Kit and really like the concept of workflows as background jobs. I’ve been able to get workflows working when using a local Postgres database, but I’m running into confusion when trying to use it in more production-like setups.

I’d like to clarify the supported deployment models, specifically around Next.js standalone builds and Docker.

What I’m trying to do

• Run a Next.js app in output: "standalone" mode
• Deploy it inside a Docker container
• Use Workflow Dev Kit with a remote Postgres database
• Trigger workflows successfully (jobs are inserted and visible in the DB)

What happens

• Workflow runs are created and visible in Postgres (status stays pending)
• No workflow execution occurs when using a remote database
• The same code works correctly when using a local Postgres database
• This suggests the producer side works, but no worker is processing jobs
• It also created this pgboss schema. Where in local environment i don't see this pgboss schema
  only workflow and workflow_drizzle is created.

Questions / clarification needed

1. Is Workflow Dev Kit officially supported outside Vercel’s managed runtime?

   • Next.js running as standalone
   • Dockerized environments
   • Self-hosted Node.js servers

2. Does Workflow Dev Kit require a long-running worker process?

   • If so, is this compatible with serverless or standalone Next.js deployments?
   • Is running a separate worker process expected?

3. Is the intended usage limited to Vercel-managed infrastructure only?

   • If yes, could this be documented more explicitly?

4. Are there any examples or reference architectures for:

   • Docker deployments
   • Self-hosted Next.js
   • Non-serverless environments

Why this matters

Understanding the supported runtime model would help teams decide:

• Whether Workflow Dev Kit can be used in hybrid or self-hosted setups
• Or if it’s intended only for Vercel-native deployments

No repository file or test is named. Start by checking the Workflow Dev Kit runtime and worker entry points alongside the Next.js standalone and Docker deployment described here; compare the local and remote Postgres behavior. Done means documenting supported deployment models, worker requirements, and reference architectures if maintainers confirm them.