ψThe ecosystem
Modules
A keystone kernel with three dependencies; everything else, adapters and extensions, plugs in through blueprints, never the other way around. Deploy to any runtime, add only what you need. Every module links to its documentation.
Primitives
The three dependencies the kernel is built on. Nothing else.
@stone-js/pipeline
The chain of responsibility every event flows through.
@stone-js/service-container
Dependency injection: the ephemeral, per-event container.
@stone-js/config
The Blueprint store, addressed by dotted stone.* keys.
Kernel
The platform-agnostic center. Knows nothing of HTTP, CLI or the browser.
@stone-js/core
Blueprint builder, kernel, lifecycle, hooks, error handling.
Layers
Cross-cutting capabilities, agnostic of the runtime.
@stone-js/http-core
The runtime-agnostic HTTP request/response model.
@stone-js/router
Universal routing for server and browser, plus the light key-router.
Read the docs →@stone-js/env
Typed, validated environment access.
@stone-js/filesystem
File access abstracted from the platform.
@stone-js/browser-core
The browser runtime primitives.
Adapters
Integration. Each turns one platform cause into an intention, deploy anywhere.
@stone-js/node-http-adapter
Production HTTP server on Node.
Read the docs →@stone-js/node-cli-adapter
Your handlers, invoked as CLI commands.
Read the docs →@stone-js/node-ws-adapter
A ws server bridging sockets to realtime.
Read the docs →@stone-js/aws-lambda-adapter
Generic AWS Lambda integration, beyond HTTP.
Read the docs →@stone-js/aws-apigw-ws-adapter
Serverless realtime on API Gateway WebSockets.
Read the docs →@stone-js/gcp-cloud-functions-adapter
Google Cloud Functions, HTTP and events.
Read the docs →@stone-js/azure-functions-adapter
Azure Functions, HTTP and events.
Read the docs →@stone-js/alibaba-fc-adapter
Alibaba Cloud Function Compute.
Read the docs →@stone-js/tencent-scf-adapter
Tencent Cloud Serverless Cloud Functions.
Read the docs →@stone-js/fetch-adapter
One Web-standard adapter: Cloudflare, Deno, Bun, Vercel, Netlify.
Read the docs →@stone-js/browser-adapter
Run the app in the browser (SPA, hydration).
Read the docs →Frontend
The view dimension.
@stone-js/use-react
React pages and layouts, CSR / SSR / SSG.
@stone-js/use-view
The framework-agnostic view engine under use-react.
Extensions
Opt-in capabilities that graft onto the kernel through blueprints. This is the toolbox.
@stone-js/validation
One schema, enforced on the API and the form.
Read the docs →@stone-js/auth
Stateless JWT / OAuth, edge-native, no session.
Read the docs →@stone-js/authz
Isomorphic RBAC + ABAC: one rule set, API and UI.
Read the docs →@stone-js/resources
Deliberate projections from model to public shape.
Read the docs →@stone-js/cloud-file
File storage over S3, GCS and Azure Blob, with signed URLs.
Read the docs →@stone-js/cache
Memory and Redis caching with a single API.
Read the docs →@stone-js/queue
Dispatch now or later, process with a worker, retry with backoff.
Read the docs →@stone-js/realtime
One Broadcaster API, backend and frontend: channels and presence.
Read the docs →@stone-js/event-bus
Emit domain events to local and cloud targets; route them anywhere.
Read the docs →@stone-js/config-source
Load config from env, files, SSM, Secrets Manager, HTTP and KMS.
Read the docs →@stone-js/openapi
A public contract derived from your schemas.
Read the docs →@stone-js/testing
Boot the real app in memory; dispatch real events.
Read the docs →@stone-js/mcp-dev
Serve the framework knowledge + your app to a coding agent via `stone mcp`.
Read the docs →Tooling
Build, scaffold, start.
@stone-js/cli
Builds every project type; codegen into .stone/.
@stone-js/create
npm create @stone-js: the scaffolder.
@stone-js/starters
Templates for each context.
Read the docs →