Skip to content
Powabase Powabase Cookbook

Powabase Cookbook

Goal-oriented recipes for building on Powabase. Short, working apps that compose multiple platform features to do something concrete.
Start with Recipe 01 View on GitHub

Recipes

Section titled “Recipes”

01 — Multi-agent customer support team

Supervisor orchestration routes user questions to specialized billing / technical / product agents, each with its own knowledge base. Streams answers and trace events.

Open recipe →

02 — HITL invoice extraction queue

An agent extracts typed invoice fields with per-field confidence; ambiguous extractions escalate to a multi-user review queue with realtime updates, presence avatars, and a chat-thread side-channel for hint-driven re-extraction.

Open recipe →

More recipes coming soon

Supabase-style user management, AI ticket triage with vision, semantic product search, and Q&A over PDFs with citations are next. Check back as they ship.

How recipes are organized

Section titled “How recipes are organized”

Each recipe is one folder with a self-contained working app:

  • A narrative README.md with the story, architecture, and step-by-step build.
  • A run.md with setup and execution steps.
  • A code/ subdirectory with the runnable source.
  • Optional: schema.sql, policies.sql, seed scripts, sample data.

Recipes are independent. cd into any recipe folder, follow run.md, and you have a working app.

UI vs API

Section titled “UI vs API”

Every recipe’s primary execution path is code you can run. Studio is a companion surface — each recipe includes one to three optional Inspect in Studio moments where you’re invited to look at what your code just produced from Studio’s angle. You never need to click through Studio to complete a recipe; it’s there to build intuition.

What you’ll write

Section titled “What you’ll write”

Powabase is a Supabase superset, so the BaaS surfaces — auth (GoTrue), row-level security, REST (PostgREST), and Realtime (Postgres Changes / Presence / Broadcast) — work through the standard Supabase client libraries. Existing Supabase SDK knowledge transfers directly; the recipes use @supabase/supabase-js for those bits.

Powabase’s distinctive surfaces — agents, orchestrations, workflows, sources, knowledge bases — are exposed as plain HTTP endpoints under /api/. Recipes call them with fetch, no separate SDK to install. Each recipe’s narrative shows the exact request shapes inline.