AI-native · Bun + Hono framework

Blazingly fast.
Zero-config.
Type-safe end to end.

The framework your AI can’t make a mess of. Drop a file, get a typed, documented, validated endpoint.

bun add @prehoy/baguette

api/customers/[id].ts

// api/customers/[id].ts
import { defineRoute, z } from "@prehoy/baguette";

export default defineRoute({
  method: "get",
  request: { params: z.object({ id: z.string() }) },
  response: z.object({ id: z.string(), name: z.string() }),
  handler: (c, { params }) =>
    c.json({ id: params.id, name: "Ada" }),
});

One zod declaration → validation, types, docs, and an error funnel.

Zero to running

A typed API in four commands.

Scaffold, run, hit it. No config, no boilerplate, no wiring — the docs generate themselves and every response is validated and typed.

bun create baguette my-api

zsh — my-api

The whole idea

One file becomes a typed, documented endpoint.

Point serve() at a directory. Every file that default-exports a defineRoute is mounted at the path its location implies. That’s the entire wiring step.

server.ts

// server.ts
import { serve } from "@prehoy/baguette";

serve({ routesDir: "./api" });
// routes loaded · validation on · docs at /api/docs

Runtime validation

Bad input never reaches your handler — 400 automatically.

Inferred TS types

params, query and body arrive fully typed. No casts.

OpenAPI + Scalar docs

The spec and the docs page write themselves.

Error funnel

Unhandled throws become a clean 500. One place to look.

Everything, by convention.

Nine moving parts

File-based routing

The file's location is the URL. api/customers/[id].ts becomes /api/customers/{id}. Nothing to register, nothing to hardcode.

zod-first, one source of truth

Declare request and response as zod schemas once. Validation, inferred handler types, and the OpenAPI spec all fall out of that single declaration.

Auto OpenAPI docs

A live Scalar UI at /api/docs and the raw spec at /api/doc — generated from your schemas, never hand-wired, never stale.

Secure by default

Declarative per-route auth, built-in rate limiting (brute-force + email-bomb protection), security headers, a CORS footgun guard, and body limits — one flag each.

Production-ready

onBoot and onShutdown hooks with graceful SIGTERM draining, static/SPA serving, and a typed defineEnv that replaces your hand-written env.ts.

Real-time WebSockets

Opt-in WebSockets with a built-in room/channel pub/sub — broadcast from any handler, cron, or automation. Bun-native, no socket.io. Off until you set ws.

ORM-agnostic

The framework imports no ORM. Bring Prisma, Drizzle, or raw SQL. Nothing in the hot path you didn't put there.

Optional cron, queues, automations & email

cron/ for scheduled jobs, queues/ for bee-queue background jobs, automations/ for LISTEN/NOTIFY handlers, and React email templates with a browser preview. Each off until you opt in.

AI-proof by convention

One obvious way to do each thing, enforced. A shipped clean-code contract, a baguette/eslint preset, and baguette check keep the codebase boring and typed.

The moat

The framework your AI can’t make a mess of.

Generated code drifts because there are a hundred ways to do everything. baguette ships one. A clean-code contract in AGENTS.md, a baguette/eslint preset, and a checker turn those conventions into CI failures — so an agent physically can’t merge the mess.

One route per file, path from location
All I/O through zod — no manual parsing
No as any / as never in app code
logger, not console.log
Scaffold with baguette new, never freehand
Boring, typed, and deletable beats clever

Read the contract →

terminal

$ baguette check

  api/customers/create.ts
    warn  hardcoded path — derive it from the file location
    warn  manual c.req.json() — declare a request.body schema

  api/legacy/proxy.ts
    error  'as any' in app code — the framework is missing a type

   warnings ·  error ·  routes clean

baguette check runs in CI. Clean code passes; clever code doesn’t.

Backend, handled

Ship it. Or have us ship it.

baguette is built by Prehoy Industries. Deploy your API managed on Berth, or bring us in to build and run the whole backend and infrastructure.

Deploy on Berth →Talk to us

Blazingly fast.Zero-config.Type-safe end to end.