Full-stack TypeScript framework

The whole stack, one framework.

Routing, views, models, auth, CMS, commerce, AI, and cloud deploys. The same UI ships to web, desktop, and mobile, first-party and fully typed throughout.

Get started Explore features

app/Models/Post.ts

import { defineModel } from '@stacksjs/orm'

export default defineModel({
  name: 'Post',
  traits: {
    useUuid: true,
    useTimestamps: true,
    useApi: { uri: 'posts' },     // REST routes + actions
    useSearch: { searchable: ['title'] },
  },
  attributes: {
    title: { fillable: true, required: true },
    status: { default: 'draft' },
  },
})

$ buddy migrate # models to migrations, applied $ buddy deploy # web, docs, blog, API, cloud

Running in a few minutes.

Pantry provisions Bun, SQLite, and everything else the project declares. Install it once, then Buddy takes over.

Install PantryOne installer provisions Bun, Git, SQLite, and every tool a Stacks project declares.
Create a projectpanx runs Buddy in an isolated environment and sets up the generated project’s toolchain.
Start buildingbuddy dev serves the frontend, API, and dashboard together, with hot reload.

Read the docs Source on GitHub

$ curl -fsSL https://pantry.dev | bash ✓ pantry installed $ panx @stacksjs/buddy new my-project ✓ project scaffolded $ cd my-project && buddy dev ✓ web · api · dashboard hot reload on

One install, every layer.

Each system is first-party and shares the same types, config, and tooling. No glue code, no plugin roulette.

Application core

Routing, STX views, models, actions, middleware, and validation in one typed application.

Queues and mail

Jobs, batches, schedules, events, notifications, and worker-ready background workflows.

Native apps

The same STX UI ships as a web app, an iOS or Android app, and a desktop app with a system tray, from one codebase.

CMS

Posts, pages, taxonomy, media, a real dashboard, and generated content APIs.

Auth

Sessions, tokens, passkeys, social login, magic links, policies, guards, and rate limiting.

Commerce

Products, orders, customers, coupons, payments, shipping, tax, and gift cards, as models you already know how to query.

Dashboard

A generated admin panel for every model, plus analytics, jobs, and settings, in 250-plus components.

Storage

Local, S3, signed URLs, uploads, visibility, and file utilities.

AI

Anthropic, OpenAI, and Ollama behind one chat driver, Bedrock alongside for AWS-hosted models, plus RAG, embeddings, and MCP.

Testing

Unit, feature, HTTP, browser, and database tests with factories and helpers.

Realtime and search

Channels, broadcasts, websocket drivers, and app-level search workflows.

Cloud deploys

AWS, DNS, CDN, TLS, and mail, described in TypeScript config and shipped by Buddy.

Two ways to size it up.

What people build with it, and how it lines up against whatever you are using today.

Use cases

Same install, 18 shapes of project.

SaaS, storefronts, content sites, APIs, internal tools, native apps. Not editions or plans: the same framework pointed at a different problem, with the layers each one leans on spelled out.

SaaS applications Online stores Marketplaces Content sites and blogs Marketing sites Documentation sites

All 18 use cases

Compare

18 honest comparisons.

Every one says where the other framework is the better choice before it says where this one is, and the table is about what ships in the box rather than which is faster.

vs Next.js vs Nuxt vs NestJS vs AdonisJS vs Laravel vs Ruby on Rails

See the comparison table

One UI. Web, desktop, and mobile.

The STX views, components, and routes already written for the web are the application. Craft wraps that same UI in a desktop window with a system tray, or a native iOS and Android shell, so a feature built once ships everywhere.

Web macOS desktop System tray iOS Android

$ buddy dev:desktop ✓ Craft window dashboard, hot reload $ buddy build:ios ✓ Xcode project config/mobile.ts $ buddy build:android ✓ Gradle project config/mobile.ts

From first commit to production.

Buddy is the command center. It scaffolds, serves, tests, builds, and deploys the whole project.

Scaffold

buddy make:model Post generates the model, migration, factory, and REST actions in one pass.

Build

buddy dev serves the app, docs, blog, and dashboard locally with hot reload and typed routes.

Ship

buddy deploy builds every surface and publishes the AWS infrastructure from the same config.

Developer experience, agent experience

Written for you. Legible to the agent next to you.

AGENTS.md is the one file a coding agent already knows how to read, checked into the repo like everything else. buddy setup:ai generates CLAUDE.md, .claude/skills/, and .cursor/rules/ from it, so Claude Code, Codex, and Cursor all work from the same source instead of three drifting sets of instructions.

AGENTS.md, checked inThe one file a coding agent reads first, versioned with the code it describes instead of living in someone’s head.

140-plus dedicated skillsOne per subsystem, from auth to deploys, so an agent reaches for the real API instead of guessing one.

Typed the whole way downA model, its migration, its API, and its view are typed against each other, so a rename is either everywhere or it does not compile.

One CLI, one waybuddy lint, buddy typecheck, buddy test: the same commands an agent runs are the ones that gate a human’s pull request.

Read AGENTS.md Browse the skills

$ buddy setup:ai ✓ CLAUDE.md generated ✓ skills written to .claude/skills/ $ buddy lint && buddy typecheck ✓ 0 errors · 0 warnings

One repo, all the way to the edge.

The site, the docs, the blog, the API, the queues, and the infrastructure they run on. Same config, same types, same deploy.

A CMS your editors will actually use.

Markdown for developers, a real dashboard for editors. Content ships with generated APIs, so the site, docs, and blog stay in the same repo.

PostsMarkdown body, excerpt, author, tags, and a generated API.

PagesStructured content with stable slugs and dashboard editing.

TaxonomyTags, categories, and editorial filters that stay searchable.

MediaFirst-party storage hooks for images, attachments, and assets.

Custom resourcesModel-backed resources with generated endpoints and screens.

Docs and blogBunPress docs at /docs, Markdown blog with RSS at /blog.

One command to production.

buddy deploy builds the site, docs, blog, and API, then publishes DNS, CDN, storage, and mail from the same config.

stacksjs.com stacksjs.com/docs stacksjs.com/blog stacksjs.com/api stacksjs.com/dashboard

$ buddy deploy ✓ web built and uploaded ✓ docs mounted at /docs ✓ blog feed and sitemap live ✓ cloud DNS, CDN, TLS, mail

Stacks

Build

Run

Ship

Products

Workloads

Teams

Full-stack JS

TypeScript backends

Other ecosystems

The whole stack, one framework.

Running in a few minutes.

One install, every layer.

Application core

Queues and mail

Native apps

CMS

Auth

Commerce

Dashboard

Storage

AI

Testing

Realtime and search

Cloud deploys

Two ways to size it up.

Same install, 18 shapes of project.

18 honest comparisons.

One UI. Web, desktop, and mobile.

From first commit to production.

Scaffold

Build

Ship

Written for you. Legible to the agent next to you.

One repo, all the way to the edge.

A CMS your editors will actually use.

One command to production.

Stacks

The whole stack, one framework.

Running in a few minutes.

One install, every layer.

Application core

Queues and mail

Native apps

CMS

Auth

Commerce

Dashboard

Storage

AI

Testing

Realtime and search

Cloud deploys

Two ways to size it up.

Same install, 18 shapes of project.

18 honest comparisons.

One UI. Web, desktop, and mobile.

From first commit to production.

Scaffold

Build

Ship

Written for you. Legible to the agent next to you.

One repo, all the way to the edge.

A CMS your editors will actually use.

One command to production.

Release notes, occasionally.