██████╗ ██╗ ██████╗ ██████╗██╗ ██╗███████╗███╗ ██╗██████╗
██╔══██╗██║ ██╔═══██╗██╔════╝██║ ██╔╝██╔════╝████╗ ██║██╔══██╗
██████╔╝██║ ██║ ██║██║ █████╔╝ █████╗ ██╔██╗ ██║██║ ██║
██╔══██╗██║ ██║ ██║██║ ██╔═██╗ ██╔══╝ ██║╚██╗██║██║ ██║
██████╔╝███████╗╚██████╔╝╚██████╗██║ ██╗███████╗██║ ╚████║██████╔╝
╚═════╝ ╚══════╝ ╚═════╝ ╚═════╝╚═╝ ╚═╝╚══════╝╚═╝ ╚═══╝╚═════╝
production backend blocks. generated into your project. owned by you.
Blockend generates production-ready backend infrastructure — rate limiting, logging, error handling, validation, response formatting — directly into your project as plain source files you own and modify.
There is no runtime package to install. No API to stay compatible with. No black box to debug inside node_modules.
Blockend is a CLI tool, dependency-free at runtime & MCP-enabled
- Why should rate limiting require learning another package's configuration API?
- Why should your error handler be defined by someone else's opinion of what an error looks like?
- Why should a logging package decide how your request context is shaped?
- Why should you have to read someone else's source when something breaks in production?
By removing the boundary between "dependency" and "your code," Blockend treats backend infrastructure as what it actually is: solved engineering problems that belong in your repository, not in your node_modules.
npx blockend-cli init
npx blockend-cli add request-validatorThe init command sets up your blocks/ directory. The add command generates the block into it.
import { expressValidator } from "./blocks/request-validator/express.js";
import { z } from "zod";
const validate = expressValidator({
body: z.object({
name: z.string().min(1),
email: z.string().email()
})
});
app.post("/users", validate, (req, res) => {
res.status(201).json({ user: req.body });
});The import above resolves to ./blocks/request-validator/express.ts — a file sitting in your own repository. Open it, read it, change it. It belongs to you the moment it is generated.
| Block | Description |
|---|---|
rate-limiter |
Token bucket algorithm with pluggable storage adapters (memory, Redis, Upstash) |
error-handler |
Centralized error pipeline with typed AppError, HTTP status mapping, and logging seam |
logger |
Structured request logging via pino with AsyncLocalStorage context propagation |
request-validator |
Zod-based input validation with adapters for Express, Fastify, and Hono |
response-formatter |
Standardized API response envelope with consistent success, error, and metadata shapes |
# add a block to your project
npx blockend-cli add <block-name>
# list all available blocks
npx blockend-cli list
# initialize blockend in an existing project
npx blockend-cli initBlockend detects your package manager (npm, pnpm, yarn, bun) and generates TypeScript by default. JavaScript output is on the roadmap.
Blockend ships an MCP server so AI tools can add and configure blocks through natural language:
npx blockend-cli mcp initOnce connected, you can ask your AI assistant to add blocks, describe what each one generates, or scaffold entire middleware stacks — the MCP server handles the CLI interaction.
Want to contribute a block? Read the contribution guidelines.
The bar for a new block: it must be infrastructure nearly every backend project needs, it must be implementable without deep runtime coupling, and it must be the kind of code a senior engineer would be comfortable reading in a production codebase.
If you have refined a utility across multiple projects and believe it belongs here, open an issue. Describe what it solves, what dependencies it requires, and what the public API looks like.
git clone https://github.com/codewithnuh/blockend
cd blockend
pnpm install
pnpm devThe monorepo is structured with packages/cli, packages/core, packages/registry, and apps/docs. Each package has its own README with development notes.
another package—
who wrote this, why does it break,
where is the source code
Documentation · npm · GitHub · X
If Blockend is useful to you, a star on the repository helps others discover it.