Tech Stack Matrix · Languages, Frameworks & Services

Your languages and frameworks on one cloud fabric.

Browse implementation guides with real SDK code and stack.json declarations across Go, Node.js, Python, PHP, SvelteKit, React, Vue, Angular, Next.js, and Ionic.

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

Go (wasm-function)

Go is the platform’s first-class language: Wasm functions for handlers, binary workers for long processes, and the typed Go SDK across every resource.

Go + functions Go with KERNSTACK functions Go with KERNSTACK Functions: handlers compiled to WebAssembly, routes declared beside them, local serve and scoped deploys built in. Go + tables Go with KERNSTACK tables Go with KERNSTACK Tables: handlers and key-value tables in one declaration — keyed reads, change streams, typed SDK access. Go + search Go with KERNSTACK search Go with KERNSTACK Search: text indexes declared over your tables, queried from Go functions that enrich results from live rows. Go + inference Go with KERNSTACK inference Go with KERNSTACK Inference: catalogue models called from Go handlers — embeddings, sentiment, vision — plus workflow AI steps.

Node.js (container-worker)

Node.js runs as container workers — existing servers and TypeScript backends declared with runtime, sizing, and idle behaviour in stack.json.

Node.js + workers Node.js with KERNSTACK workers Node.js with KERNSTACK Workers: your TypeScript/JavaScript processes declared with runtime nodejs — sizing, idle timeout, HTTP port. Node.js + tables Node.js with KERNSTACK tables Node.js with KERNSTACK Tables: the typed Node SDK against declared key-value tables — sessions, feeds, and records without a database server. Node.js + workflows Node.js with KERNSTACK workflows Node.js with KERNSTACK Workflows: TypeScript workers as workflow steps — order, retries, and human approvals declared around your code.

PHP (container-worker)

PHP runs as container workers — classic server-rendered apps and APIs declared beside the tables they use, without a separate hosting stack.

PHP + workers PHP with KERNSTACK workers PHP with KERNSTACK Workers: classic PHP applications and APIs as declared php workers — routing, sizing, and secrets in stack.json. PHP + tables PHP with KERNSTACK tables PHP with KERNSTACK Tables: the typed PHP SDK over declared tables — sessions, catalogues, and settings as keyed records.

Python (container-worker)

Python runs as container workers for data, document, and model work, with bucket volumes for files and typed SDK access to tables and buckets.

Python + workers Python with KERNSTACK workers Python with KERNSTACK Workers: data and document pipelines as declared python workers — extraction, ETL, and ML-adjacent jobs beside the data. Python + inference Python with KERNSTACK inference Python with KERNSTACK Inference: custom inference endpoints in Python — your model, weights from your bucket, catalogue models beside it. Python + vector-search Python with KERNSTACK vector search Python with KERNSTACK Vector Search: corpora prepared by Python workers, vector indexes declared over them, retrieval in one project.

React (static-app)

React apps ship as static builds into buckets served by prefix routes, calling the project’s functions and workers through the same stack.json.

React + buckets React with KERNSTACK buckets React with KERNSTACK Buckets: Vite/CRA builds published to a bucket prefix on deploy and served by a prefix route — hosting as declaration. React + analytics React with KERNSTACK analytics React with KERNSTACK Analytics: product events to a declared analytics project — write key in the app, retention in stack.json.

SvelteKit (static-app)

SvelteKit apps build into bucket-published frontends served by gateway prefix routes, with KERNSTACK services behind them in the same project.

SvelteKit + buckets SvelteKit with KERNSTACK buckets SvelteKit with KERNSTACK Buckets: adapter-static builds published to bucket prefixes, replace-on-deploy, CDN-ready by declaration. SvelteKit + gateway SvelteKit with KERNSTACK gateway SvelteKit with KERNSTACK Gateway Domains: custom hostnames, path prefixes, canonical redirects, and API keys declared in one block.
FAQ

Frequently asked questions

When you scaffold a function or worker with kernstack add, the CLI automatically downloads and vendors the typed SDK into .kernstack/sdk-<lang>-v1/ so both your IDE and coding agents have full type definitions.

Declare your frontend build in the apps[] section of stack.json, point its out directory at a bucket seed, and expose that bucket over a CDN-enabled prefix route on the gateway.

Yes. A single KERNSTACK project routinely combines a SvelteKit or React frontend with Go WebAssembly functions for low-latency APIs and Python workers for AI or document pipelines.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Blueprint · goGo WebAssembly HTTP Function Starter (func-go-minimal)Deploy a minimal Go WebAssembly HTTP function on KERNSTACK with gateway routing declared in stack.json and no idle infrastructure cost.Blueprint · go-python-sveltekitKERNSTACK Full-Stack Platform Reference Demo (kernstack init --demo)Explore the official KERNSTACK platform demo: SvelteKit frontend, REST and GraphQL functions, tables, websockets, image worker, volumes, and approval workflows.Blueprint · goGo Container Worker Starter (work-go-minimal)Scaffold a long-running or high-concurrency Go container worker on KERNSTACK with mounted bucket volumes, internal service routing, and unified credits.Blueprint · nodejsNode.js Container Worker Starter (work-nodejs-minimal)Start a Node.js and TypeScript container worker on KERNSTACK for SSR apps, API integrations, background jobs, and AI agent tool execution.Blueprint · phpPHP Container Worker Starter (work-php-minimal)Deploy modern PHP container workers on KERNSTACK for e-commerce integrations, ERP connectors, legacy modernization, and European agency projects.Blueprint · pythonPython Worker Starter for AI & Data (work-python-minimal)Launch a Python container worker on KERNSTACK for RAG pipelines, document parsing, vector embeddings, and scientific workloads.

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 →