# Quickback Stack

**Quickback Stack** is the runtime services that surround your compiled API. While the [Quickback Compiler](/start) generates your routes and security policies, the Stack is everything else you need to ship a real application — auth, storage, realtime, queues, an admin UI, an account UI — all on your own Cloudflare account.

## What you get

| Component | Service | Purpose |
|-----------|---------|---------|
| [Auth](/platform/auth) | Better Auth | Email/OTP, passkeys, organizations, admin |
| [Storage](/platform/storage) | KV, R2 | Session cache, JWT revocation, files |
| [Realtime](/platform/realtime) | Durable Objects | WebSocket for live updates |
| [Queues](/platform/queues) | Cloudflare Queues | Background jobs, webhook delivery |
| [Schedules](/platform/schedules) | Cron Triggers | `defineSchedule` cron jobs, server-internal |
| [Email](/platform/email) | Email Workers | `defineEmail` inbound handlers, server-internal |
| [Vector & AI](/platform/vector) | Workers AI | Embeddings, semantic search |
| [Webhooks](/platform/webhooks) | Hono + Queues | Signed inbound, retried outbound |
| [Push](/platform/push) | Web Push | VAPID subscriptions, typed payloads |
| [API Contract](/platform/api-contract) | Generated | Envelope, errors, pagination, versioning |
| [Admin UI](/ui/admin) | Embedded SPA | Schema-driven admin UI |
| [Account UI](/ui/account) | Embedded SPA | Login, profile, orgs, admin |

## Architecture

```
┌─────────────────────────────────────────────────────────────┐
│                     Cloudflare Edge                          │
├─────────────────────────────────────────────────────────────┤
│   ┌─────────────┐    ┌─────────────┐    ┌─────────────┐    │
│   │   Workers   │    │   Durable   │    │     KV      │    │
│   │  (API/CMS)  │    │   Objects   │    │   (Cache)   │    │
│   └──────┬──────┘    └──────┬──────┘    └──────┬──────┘    │
│          │                   │                   │           │
│   ┌──────┴──────┐    ┌──────┴──────┐    ┌──────┴──────┐    │
│   │     D1      │    │  Realtime   │    │     R2      │    │
│   │  (or Neon)  │    │  (WebSocket)│    │  (Storage)  │    │
│   └─────────────┘    └─────────────┘    └─────────────┘    │
│                                                              │
│   ┌─────────────┐    ┌─────────────────────────────────┐    │
│   │   Queues    │    │         Better Auth              │    │
│   │ (Background)│    │  (Email OTP, Passkeys, etc.)    │    │
│   └─────────────┘    └─────────────────────────────────┘    │
│                                                              │
│   ┌─────────────┐                                            │
│   │  Schedules  │                                            │
│   │   (Cron)    │                                            │
│   └─────────────┘                                            │
└─────────────────────────────────────────────────────────────┘
```

## Your account, your data

Everything in Quickback Stack runs on your own Cloudflare account:

- **Workers** — your deployments, your logs
- **Storage** — your KV namespaces, your R2 buckets
- **Secrets** — your API keys, in your Wrangler secrets

Quickback provides the architecture and the code generation. You own the infrastructure.

## Quick start

```bash
# Scaffold + compile interactively
mkdir my-app && cd my-app
npx @quickback-dev/cli start

# Deploy to your Cloudflare account
npm i -g wrangler
wrangler deploy
```

`start` handles scaffold, login (only when needed), and the first compile in one shot. The deploy step uses your own wrangler auth and ships everything to your Cloudflare account.

## See also

- [Quickback Compiler](/start) — the build tool that generates your API
- [Quickback for Hono API](/api) — what the compiler outputs
- [Definitions](/define) — the security model the Stack runs