Quickback Docs

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.

The Quickback Compiler reads a single set of definitions — schema, firewall, access, guards, masking, views, actions — and emits production output for the target you choose.

The two targets

Quickback for Hono API

Generates a complete Hono application: routes, middleware, types, OpenAPI spec, MCP server. Pair with Cloudflare D1 for SQLite-at-the-edge or Neon for full PostgreSQL with database-level RLS.

providers: {
  runtime: defineRuntime('cloudflare'),
  database: defineDatabase('cloudflare-d1'),
  auth: defineAuth('better-auth'),
}

Use this target when you want Quickback to generate the entire API surface, not just security policies.

Quickback for Supabase

Generates PostgreSQL Row Level Security policies for Supabase. Keep Supabase Auth, Storage, and Realtime — Quickback adds the security layer beneath your application code.

providers: {
  runtime: defineRuntime('supabase'),
  database: defineDatabase('supabase'),
  auth: defineAuth('supabase-auth'),
}

Use this target when you're already on Supabase and want a typed DSL for RLS.

At a glance

Hono APISupabase RLS
What's generatedRoutes, middleware, types, OpenAPI, MCP, RLS (Neon only)RLS policies + helper functions only
DatabaseCloudflare D1 or Neon PostgresSupabase Postgres
AuthBetter AuthSupabase Auth
Application codeCompiler-generatedYou write your own
Deploymentwrangler deploy (or any Hono runtime)supabase db push

The shared core

Whichever target you pick, the input is the same. See Definitions for the DSL that powers both.

On this page