keel
Opinionated Fastify 5 + Effect backend framework. Glue only — no business logic, no application runtime.
Keel wires Fastify and Effect together and stops there: Effect Schema as the type
provider, controllers as Effect services, tagged errors mapped to HTTP responses,
Pino↔Effect logging, SSE. Your app builds its own ManagedRuntime and hands it
over.
pnpm add @kylobyte/keelWhere to start
Section titled “Where to start”Building something? Your first app goes from an empty directory to a running, documented, tested service one file at a time. Then Adding a feature for the loop you will repeat, and Adding authentication when the routes stop being public.
Working out whether it fits? The shape of an app is the five-minute version; Architecture explains what each part does and how a request actually flows through it; Design decisions covers why it was built this way.
Looking something up?
- Install — entry points and the peer dependencies, and why they are peers.
- Bootstrap — building the runtime and handing it to keel.
- Controllers and Routes — the day-to-day surface.
- SQL — the optional Drizzle +
@effect/sqlentry point. - Troubleshooting — what a compile error from all this means.