Blueprint · Node.js Container Worker

Node.js Container Worker Starter (work-nodejs-minimal)

Minimal Node.js worker that responds with 'hello from nodejs worker' on every invoke. Deploy Node.js backends, webhook consumers, and full-stack SSR workers on KERNSTACK with the official Node.js SDK and zero AWS configuration.

Container Workers NoSQL Tables Approval Workflows

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

One-Command CLI Initialization

CLI Command work-nodejs-minimal

kernstack add worker --name node-svc --blueprint work-nodejs-minimal

Full npm ecosystem compatibility inside a governed stack

The work-nodejs-minimal blueprint lets JavaScript and TypeScript teams bring their existing npm packages, PDF generators, Stripe/Mollie webhooks, or SSR servers onto KERNSTACK without rewriting into proprietary edge dialects.

Every resource the worker touches — Tables, Buckets, Search indexes, Secrets, and Workflows — is declared alongside it in stack.json.

Standard Node.js runtime with full npm dependency support
Pre-configured .kernstack/sdk-nodejs-v1 client for zero-boilerplate data access
Ideal migration target for Lovable, Bolt, Vercel, or Railway Node backends

Designed for human and agent co-development

When an agent in a KERNSTACK sandbox adds an endpoint or background job to work-nodejs-minimal, it can test against an isolated preview environment and share a secured preview link directly in the project thread.

Node.js workers without a second platform

work-nodejs-minimal gives Node teams the npm ecosystem inside a worker that is still declared next to tables, buckets, and workflows. Package installs happen in the build, not as a snowflake on a long-lived VM. The usual first endpoint is a JSON handler; the usual second step is calling the vendored SDK for a table read or a presigned upload.

Because the worker is one resource in the project graph, a frontend app in the same repository can call it through a gateway route without a separate origin, CORS product, or secret store. Preview and production differ by target, not by a rewritten server.

Starter Code — work-nodejs-minimal nodejs

const { run, WorkerInvokeResponse } = require('kernstack-sdk');

run(async (req) =>
  new WorkerInvokeResponse({
    body: Buffer.from('hello from nodejs worker'),
    statusCode: 200,
    headers: { 'Content-Type': 'text/plain' },
  }),
);

stack.json — work-nodejs-minimal plan · deploy

{
  "stack": { "target": "saas.prod" },
  "gateway": {
    "routes": [
      {
        "name": "app-api",
        "type": "http",
        "target": { "kind": "worker", "name": "node-svc" }
      }
    ]
  },
  "resources": {
    "workers": [
      { "name": "node-svc", "runtime": "nodejs" }
    ],
    "tables": [
      { "name": "accounts", "key_name": "id", "key_type": "string" }
    ]
  }
}

FAQ

Frequently asked questions

Can I use npm packages with work-nodejs-minimal?

Yes. Node.js workers run in a full container environment and support standard package.json dependencies, native addons, and TypeScript builds.

Is work-nodejs-minimal suitable for migrating from Vercel or Bolt?

Yes. Server routes and background tasks from Vercel, Lovable, or Bolt map cleanly onto a KERNSTACK Node.js worker while keeping your frontend in apps[].

How does the worker authenticate to Tables and Buckets?

The KERNSTACK runtime injects scoped environment credentials automatically so the Node.js SDK connects without manual API key management.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →