Quickback for Hono API
Compile your TypeScript definitions into a production-ready Hono API on Cloudflare D1 or Neon — with security, validation, and OpenAPI built in.
Quickback for Hono API is the default compile target. Your defineTable() and defineActions() files become a complete Hono application: routes, middleware, types, OpenAPI spec, and an MCP server, all generated and ready to deploy.
What you ship
src/
├── routes/ # One file per resource — GET/POST/PATCH/DELETE + batch
├── middleware/ # Auth, firewall, access, guards, masking
├── types/ # TypeScript interfaces inferred from your schema
├── openapi.json # Generated spec, served at /openapi.json
└── index.ts # Hono app entry pointThe generated app runs on Cloudflare Workers (recommended) or any Hono-compatible runtime. Pair it with Cloudflare D1 for SQLite-at-the-edge or Neon for full PostgreSQL with database-level RLS.
Pick your database
| Database | Best for | Notes |
|---|---|---|
| Cloudflare D1 | Most projects | SQLite at the edge. Application-level security. Free tier covers a lot. |
| Neon | PostgreSQL features needed | Full Postgres with database-level RLS via Neon Authorize. |
Pick your runtime
| Runtime | Notes |
|---|---|
| Cloudflare Workers | Default. Edge-native, integrates with the rest of Quickback Stack. |
| Bun / Node | Supported via the same Hono output. Less first-class for Stack services. |
In this section
- Cloudflare — Compile and deploy to Workers
- Neon — Compile to PostgreSQL with RLS
- Database — D1, Neon, schema and migrations
- Using the API — CRUD, batch operations, query params, OpenAPI, errors
Compile Targets
Quickback compiles your definitions to one of two targets — a Hono API on Cloudflare/Neon, or PostgreSQL Row Level Security policies for Supabase.
Cloudflare Workers
Quickback generates Hono-based API routes for Cloudflare Workers with D1 database, application-level security, and full batch operations.