Blueprint · Full-Stack Reference Architecture

KERNSTACK Full-Stack Platform Reference Demo (kernstack init --demo)

Platform demonstration: web app plus REST, GraphQL, tables, websockets, presigned upload, image transform, worker volumes, and a workflow with human approval. Scaffold the complete multi-service architecture in one command.

Functions (WASM)Container Workers NoSQL Tables Object Buckets Approval Workflows Edge Gateway CDN Edge

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

One-Command CLI Initialization

CLI Command platform-demo

kernstack init my-platform --demo

Every core KERNSTACK capability in one runnable repo

The platform-full-stack-demo blueprint (scaffolded via kernstack init --demo) is the canonical reference architecture for the Software Lifecycle Cloud. It combines a SvelteKit static frontend in apps/web with nine Go WebAssembly functions, two container workers, serverless tables, presigned bucket uploads, frozen worker volumes, WebSocket routes, and a multi-step human-approval workflow.

Instead of stitching together separate tutorials for API Gateway, Lambda, DynamoDB, S3, Step Functions, and Vercel, engineering teams can inspect and deploy the entire integrated graph from a single stack.json.

SvelteKit SPA deployed to a CDN-backed prefix bucket route
REST and GraphQL APIs plus real-time WebSocket connections on Go functions
Presigned browser uploads to Buckets with background image transformation workers
Movie-night human-in-the-loop workflow demonstrating pause, approval, and resume

How to use the reference demo as a production foundation

Teams frequently clone the platform demo into a fresh staging environment, ask @agent or Cursor to prune unused routes, and adapt the tables and workflows to their domain model.

The movie-night workflow is the piece to study if you need a pause for a person. It stops, waits for an approval recorded on the project, and resumes on the same run. The image worker and the presigned upload show the bucket path: the browser never receives a storage key, and the transform runs as a worker rather than inside the request that issued the URL.

SvelteKit in this demo is a static app on a prefix route. REST and GraphQL functions are Go WebAssembly. WebSocket routes share the gateway with those HTTP routes. Nothing in the demo asks you to create a second project for the frontend, the API, or the workflow. Delete the sample domain, keep the resource kinds, and the plan diff is the review.

Starter Code — platform-demo go-python-sveltekit

# Initialize the complete reference stack locally
kernstack init acme-demo --demo
cd acme-demo

# Preview all 9 functions, 2 workers, tables, buckets & workflows
kernstack plan

# Deploy the full stack to your environment
kernstack deploy

stack.json — platform-demo plan · deploy

{
  "stack": {
    "target": "__STACK_TARGET__",
    "description": "Platform demonstration: web app plus REST, GraphQL, tables, websockets, presigned upload, image transform, worker volumes, and a workflow with human approval."
  },
  "apps": [
    {
      "name": "web",
      "build": "npm ci --prefix apps/web && npm run build --prefix apps/web",
      "out": "apps/web/build",
      "seed": "seed/buckets/www"
    }
  ],
  "gateway": {
    "routes": [
      {
        "name": "www",
        "type": "prefix",
        "default_key": "index.html",
        "target": {
          "kind": "bucket",
          "name": "www"
        }
      },
      {
        "name": "api",
        "type": "http",
        "target": {
          "kind": "function",
          "name": "router"
        }
      },
      {
        "name": "starter-ws",
        "type": "websocket",
        "target": {
          "kind": "function",
          "name": "websockets"
        }
      },
      {
        "name": "volume-read",
        "type": "http",
        "target": {
          "kind": "worker",
          "name": "volume-read"
        }
      }
    ]
  },
  "resources": {
    "tables": [
      {
        "name": "starter-movies",
        "key_name": "movie_id",
        "key_type": "S",
        "indexes": [
          {
            "name": "year-index",
            "key_name": "year",
            "key_type": "N"
          },
          {
            "name": "director-index",
            "key_name": "director",
            "key_type": "S"
          }
        ]
      }
    ],
    "buckets": [
      {
        "name": "www"
      },
      {
        "name": "starter-uploads"
      },
      {
        "name": "starter-volume-source",
        "volumes": [
          {
            "name": "starter-readonly-volume",
            "read_only": true
          }
        ]
      }
    ],
    "workers": [
      {
        "name": "image-transform",
        "runtime": "binary",
        "env_vars": {
          "KERNSTACK_ACCESS_KEY_ID": "{{ref-access-key-id-current}}",
          "KERNSTACK_ACCESS_KEY_SECRET": "{{ref-access-key-secret-current}}",
          "KERNSTACK_DZONE": "{{ref-dzone-current}}"
        }
      },
      {
        "name": "volume-read",
        "runtime": "binary",
        "volumes": [
          {
            "name": "starter-readonly-volume",
            "mount_path": "/volumes/starter-readonly-volume"
          }
        ]
      }
    ],
    "workflows": [
      {
        "name": "movie-night",
        "description": "Pick a random movie, wait for approval or rejection, then announce an approved pick.",
        "steps": [
          {
            "id": "pick",
            "function": "movie-pick",
            "timeout_ms": 60000
          },
          {
            "id": "approve",
            "human": {
              "title": "Approve this movie?",
              "show": {
                "from_step": "pick"
              },
              "expires_in_seconds": 604800,
              "notify": [
                "console"
              ]
            }
          },
          {
            "id": "announce",
            "function": "movie-announce"
          }
        ]
      }
    ]
  }
}

FAQ

Frequently asked questions

What does kernstack init --demo create?

It scaffolds a complete multi-service project containing a SvelteKit frontend, 9 Go functions (REST, GraphQL, tables, websockets, uploads, volumes, workflows), 2 workers, and a full stack.json.

Can I deploy the demo on the Free or Builder tier?

Yes. Because every resource scales to zero when idle, running and testing the platform demo consumes only a handful of credits.

Can coding agents modify the demo stack safely?

Yes. Agents work on an isolated branch and sandbox environment, and kernstack plan previews every resource change before apply.

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 →