Templates

Quickback provides pre-configured templates to get you started quickly. Each template combines a runtime, database, and auth provider into a working project.

The fastest way to start is quickback start — an interactive picker that asks for a template + project name and scaffolds in the current directory if it's empty, otherwise creates a subfolder. The picker offers cloudflare, todos, blog, and blank; every template (including saas) is available scriptably via quickback create <template> <name>.

# Interactive (recommended for first-time use)
mkdir my-app && cd my-app
npx @quickback-dev/cli start

# Already know what you want? Skip the prompts:
npx @quickback-dev/cli start blank        # config only, no features
npx @quickback-dev/cli start todos my-app # working CRUD example

Available Templates

Multi-tenant scaffolds

Cloudflare Workers + D1 + Better Auth with the organization plugin and a member / admin / owner role hierarchy wired in.

The todos template is the recommended first read — it exercises every security pillar (firewall, access, guards, masking) plus actions and views in ~80 lines you can scan in five minutes.

Fixed-org starter

The blog template uses pinned organization mode and scaffolds features.pinnedOrganizationId: "org_replace_me".

Blank scaffold

The blank template creates the project structure with quickback.config.ts only. Add your first feature by creating a file under quickback/features/<name>/<name>.ts exporting defineTable(...) — there is no separate init step.

B2B SaaS

What Each Template Includes

The cloudflare, todos, blog, and saas templates all scaffold:

• quickback.config.ts — Pre-configured with the right providers
• quickback/features/ — Feature definitions (empty for cloudflare; populated for todos / blog / saas)
• Deployment scripts — npm run deploy for Cloudflare via wrangler

The blank template includes only:

• quickback.config.ts
• package.json — dependencies ready to install

Choosing a Template

Cloudflare bare scaffold

Best when you already know the conventions and want empty walls. Multi-tenant orgs are wired in; you add your own feature files.

Todos (recommended for newcomers)

Best for learning by reading. Full multi-tenant security pillars, two actions, a named view (/api/v1/todos/views/dashboard), and field masking on the description column — all in a single ~80-line file you can copy-edit into your own table.

Blog (pinned-organization CMS)

Best for personal sites, blogs, or any app that only needs one organization at runtime. Uses pinned organization mode — organization support stays on, but the generated app hard-codes one org id and hides org switching.

• Public JSON API for content
• Admin-only editing
• Pair with any frontend (Astro, Next.js, SvelteKit, etc.)

Blank

Best when you know exactly what you want to build. Gets you the project structure and config without any opinionated features.

SaaS

Best for production B2B work. Adds R2 file uploads, outbound webhooks (with retry/dedupe), split auth/features/webhooks databases, realtime broadcast, and named views.

Template Aliases

For convenience, templates have short aliases:

After Scaffolding

quickback start runs scaffold + login + compile + install + drizzle in one flow. If you used the scriptable quickback create instead (or cancelled at the login prompt), finish setup with:

cd my-app
quickback compile   # prompts for login on first run; reuses session after
npm run dev

See the individual template guides for detailed setup:

• Cloudflare Template
• Blog Template
• Empty Scaffolding
• Pinned Organization Mode