Quickback Compiler

The Quickback Compiler is the build tool at the center of Quickback. You write declarative definitions in TypeScript — schema, security rules, validation, custom actions — and the compiler emits production-ready output for your chosen target.

defineTable() ─┐                    ┌─► Hono API     (Cloudflare D1 / Neon)
                ├─► quickback compile┤
defineActions()─┘                    └─► RLS policies (Supabase)

The same definitions, the same DSL — pick the target that fits where you're deploying.

What the compiler does

When you run quickback compile, it:

1. Reads your definitions — every defineTable(), defineActions(), and defineConfig() in your project
2. Validates security — firewall, access, guards, and masking are checked for consistency
3. Generates target output — Hono routes + middleware + types + OpenAPI + MCP, or RLS migrations + helper functions
4. Emits database migrations — runs drizzle-kit generate for schema changes

quickback/
├── quickback.config.ts    # Compiler configuration (target + providers)
└── features/
    └── jobs/
        ├── jobs.ts         # defineTable(...)
        └── actions.ts      # defineActions(...)

Two compile 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'),
}

Quickback for Supabase

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

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

The shared core

Whichever target you pick, the input language is the same:

• Definitions — Schema, Firewall, Access, Guards, Masking, Views, Actions
• Configuration — quickback.config.ts, providers, domains, bindings
• Getting Started — Templates and full examples

The cloud and the CLI

You don't run the compiler binary locally — it runs as a hosted service:

• Cloud Compiler — compiler.quickback.dev, CLI, authentication, MCP server for editors
• Claude Code Skill — AI-powered authoring assistance

Development workflow

1. Define resources in quickback/features/
2. Compile with quickback compile
3. Apply migrations for your provider
4. Test locally with npm run dev
5. Deploy with npm run deploy (Hono target) or supabase db push (Supabase target)

Next steps

• Getting Started — Create your first project
• Definitions — The shared DSL
• Quickback for Hono API — Compile to a Hono app
• Quickback for Supabase — Compile to RLS policies