Can I use Workhorse from a serverless app?

Serverless support comes down to two separate rules. Check them in this order, because a runtime can pass the database rule and still be unable to run a worker.

1. Process lifetime: A Workhorse worker is a continuous process. It holds a PostgreSQL pool, renews leases, sends heartbeats, and drains after a termination signal. A request or event invocation does not own that lifecycle, so it cannot host the worker loop.
2. Database connectivity: An enqueue producer needs a supported Workhorse client and a PostgreSQL session. Node.js functions can use the Pool exported by @stablemates/workhorse. An edge runtime may need a platform transport, and transport support alone does not make the published Node.js package compatible with that runtime.

Platform matrix

"Enqueue" means using a package that this repository publishes today. An HTTP database driver may make PostgreSQL reachable from another isolate. It cannot replace the Queryable contract or the versioned SQL behavior that a Workhorse client implements.

Vercel Node functions enqueue normally

The Vercel Node.js runtime is ordinary supported Node.js for this purpose. It can open a pg connection, and Vercel documents pg pools directly. If the function owns a transaction, pass it to Queue.enqueue. The job then commits or rolls back with the business write.

const client = await pool.connect();
try {
  await client.query("BEGIN");
  await client.query("INSERT INTO orders (id) VALUES ($1)", [orderId]);
  await queue.enqueue("order.fulfill", { orderId }, {}, client);
  await client.query("COMMIT");
} catch (error) {
  await client.query("ROLLBACK");
  throw error;
} finally {
  client.release();
}

On Vercel Fluid Compute, call attachDatabasePool after creating the pool so Vercel can release idle clients before suspending the function. That pool management does not weaken transactional enqueue.

Cloudflare Hyperdrive solves connectivity, not lifetime

Cloudflare documents pg as its recommended PostgreSQL driver through Hyperdrive. The documented path uses a current pg, the nodejs_compat flag, and the connection string exposed by the Hyperdrive binding. Cloudflare's TCP documentation confirms that Hyperdrive carries the PostgreSQL wire protocol and manages connection pooling.

That verifies the database path, but @stablemates/workhorse still supports Node.js rather than the Workers runtime. Workhorse therefore does not publish a Cloudflare enqueue client today.

Cloudflare also ties execution to an invocation. Its runtime limits allow a long HTTP response while the caller remains connected. Cloudflare may cancel work after the response or a disconnect. Runtime updates also impose a drain window. That lifecycle cannot own Workhorse leases or an autonomous worker loop.

Put the worker beside the serverless web tier

The web tier and worker tier only need access to the same PostgreSQL database. Keep request handlers on the serverless platform. Run workhorse worker in compute that owns a continuous process, such as a VM, Kubernetes deployment, ECS/Fargate service, or Cloud Run worker pool.

Use Worker processes for the process definition, probes, termination signals, and drain contract. Use Deployment and operations to size pools and operate the shared database boundary.

The compatibility reference records the verification method and date. The Vercel Edge classification follows Vercel's supported API list, which omits the Node.js networking APIs required by pg. AWS explains that Lambda owns and may replace execution environments, even though a function can reuse a database connection while an environment remains warm.

Next

• Transactional enqueue — commit the job with the business write
• Worker processes — run handlers in continuous compute
• Compatibility — check the supported runtime and database matrix

Exact process lifecycle and PostgreSQL ownership rules: architecture reference.