Build software brick by brick.

Production-ready modules with persistent state. Pick a template. Extend. Deploy.

$bun install -g brickend

View on GitHub

terminal

bash

$ brickend init my-api --template crm

$ supabase functions serve

01 — How It Works

Just three steps.

Pick a template

Templates available: CRM, Marketplace, SaaS, Real Estate, and more.

$ brickend init --template crm

Add bricks

Extend with the modules you need. Auth, users, entities, catalog, deals...

$ brickend add catalog

Deploy

Push to production with one command. Migrations included.

$ bash scripts/deploy.sh

02 — Templates

Start with a real use case

Each template includes the necessary bricks, preconfigured and ready to serve.

Starter

Minimal API with authentication

auth, users

$ brickend init my-app --template starter

CRM

Contacts + deal pipeline

auth, users, entities, contacts, deals

$ brickend init my-app --template crm

Marketplace

Products + orders

auth, users, products, orders

$ brickend init my-app --template marketplace

Real Estate

Listings + leads

auth, users, properties, leads

$ brickend init my-app --template real-estate

SaaS Admin

Multi-tenant with workspaces

auth, users, workspaces, entities, catalog

$ brickend init my-app --template saas-admin

Multi-tenant

Workspace isolation

auth, users, workspaces

$ brickend init my-app --template multi-tenant

Business

Full business management

auth, users, entities, catalog

$ brickend init my-app --template business

03 — What Gets Generated

Every brick generates a complete module

Not a template, not a snippet. A database table, migration, RLS policies, Zod schemas, service layer, and API endpoint.

project structure

my-crm/

├── supabase/

│ ├── functions/

│ │ ├── auth/index.ts POST /signup, /signin, /signout

│ │ ├── contacts/index.ts GET, POST, PATCH, DELETE /contacts

│ │ ├── deals/index.ts GET, POST, PATCH, DELETE /deals

│ │ └── _shared/

│ │ ├── core/ CORS, auth, RBAC, errors

│ │ ├── schemas/ Zod validation

│ │ └── services/ CRUD logic

│ └── migrations/ SQL + RLS policies

├── scripts/deploy.sh One-command deploy

├── openapi.yaml API documentation

└── brickend.state.json Persistent project state

04 — For AI Agents

Infrastructure that agents can use

Brickend includes an MCP server so Claude Code, Cursor, and any MCP-compatible agent can build software programmatically. Same operations. Same state. Same results.

Agent workflow

User: "Create a CRM with contacts and deals"

→ brickend_list_templates() discovers CRM template

→ brickend_init({ template: "crm" }) scaffolds project

→ brickend_status() verifies 6 bricks installed

Working API. State persisted. Next session picks up where this left off.

MCP config

{
  "mcpServers": {
    "brickend": {
      "command": "brickend-mcp"
    }
  }
}

05 — Open Source

Open source. MIT License.

$ bun install -g brickend

$ brickend init my-app --template starter

Install with Bun View on GitHub

Available on npm.