Setu-TS
Plugin-first enterprise backend framework built on Hono.
Enterprise architecture without the weight. Runtime freedom without the chaos.
[!IMPORTANT] Status: v0.12.0 publishes 55 packages to npm under @setu-ts. Versions
published before the move to npm remain on JSR, and nothing new is published there.
The kernel, the runtime layer, 41 plugins, the three starters, the test utilities, the client SDK,
and the setu CLI are implemented, tested, and documented.
Every release from v0.2.0 on is a normal release rather than a prerelease. The registry
points latest at the current one, so a bare install resolves, where every alpha version had to
be pinned by hand.
The label changed; the stability promise did not. This is pre-1.0 software — under semver 0.x
the public API is not stable, and a minor bump carries breaking changes. See
Versioning for what each bump commits us to, and CHANGELOG.md for
known limitations.
Why This Exists
Building enterprise backends today forces a difficult choice:
| Option | Problem |
|---|
| Hono | Extremely fast and runtime-portable, but intentionally minimal — no DI, no modules, no enterprise patterns. |
| NestJS | Rich enterprise features, but tightly coupled to Node.js, requires decorators and DI, and carries a steep learning curve. |
| Fastify | Fast and plugin-oriented, but lacks enterprise abstractions like repository patterns, CQRS, and multi-tenancy. |
| Express | Ubiquitous but aging, callback-based, and Node.js-only. |
Every existing solution forces a compromise: power vs. portability, features vs. simplicity,
opinion vs. flexibility.
Setu-TS resolves this compromise. It combines:
- ⚡ Hono's performance — One of the fastest TypeScript routers available.
- 🌍 Runtime independence — Write once, run on Node.js, Deno, Bun, and Cloudflare Workers.
- 🧩 Plugin-first architecture — Every capability is a plugin. Start minimal, add what you need,
replace what you do not like.
- 🏢 Enterprise capabilities — Authentication, RBAC, CQRS, domain and integration events,
multi-tenancy, audit logging, secrets management, and more.
Without becoming heavyweight. Without forcing opinions. Without locking you in.
Core Principles
| Principle | What It Means |
|---|
| Plugin-first | Every capability — logging, database, auth, validation — is a plugin. The kernel ships with zero features. |
| Runtime independent | No package except the runtime plugin uses runtime-specific APIs. Business logic never touches process.env or fs. |
| Optional DI | Dependency injection is a plugin, not a requirement. Use it if you want it; skip it if you do not. |
| Optional decorators | Decorators are a plugin, not a requirement. Every feature has a complete programmatic API. |
| Explicit APIs | No magic. No hidden globals. No reflection required. Everything is explicit and inspectable. |
| Type safety | Strict TypeScript throughout. No any in public APIs. Full type inference for services, config, and routes. |
| Tree-shakeable | Every package uses ES modules and subpath exports. You ship only what you use. |
| Production ready | Built for scale: graceful shutdown, distributed locking, circuit breakers, audit trails, and observability. |
| Enterprise focused | Patterns that large organizations need: multi-tenancy, feature flags, secrets management, CQRS, domain events. |
Features
Status legend: ✅ Implemented — shipped, tested, and documented · 📋 Designed — specified in
the roadmap, not yet built · 🚧 Planned — future design work.
Every ✅ row is a package in this repository with 90%+ test coverage on branch, function, and line.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
