Prompt management you own

Your prompts shouldn't be buried in code.

Edit your system prompts and message templates like documents, version every change, and ship without a redeploy — all running in your own Supabase.

Early access · approval required

Sign up now — we'll email you once you're approved.

system_promptv3 · published
You are a helpful assistant for at . Answer concisely, and cite a source whenever you can.
// read straight from your Supabase, variables passed in
const { system } = await getPrompt('onboarding-email', {
  name: 'Ana', product: 'Acme'
})

Edit the highlighted variables — the prompt and the code update live.

Setup to runtime

install

Authorize Supabase once. We add a prompt schema and two edge functions to your project — that's the whole footprint. Your prompts live in your database; we never store a copy.

edit

Invite your teammates — members write and publish prompts from a clean editor, saved straight to your Supabase. No pull request, no deploy, no waiting on an engineer.

use

Drop the getPrompt helper into your app — or ask your agent to add it — and call it anywhere. It reads the published version directly from your database, through your own edge function. Nothing routes through us.

Scope

Prompt storage, versioning, and runtime delivery. That's the whole job. Not an observability platform, not an evals framework, not a conversation manager — not another Langfuse.

Features

Full version history

Every publish is a version. Roll back to any of them in one click.

Variable interpolation

Use {{variables}} in both system and user templates, filled with real values at runtime.

Your infra, always

Runs entirely on your own Supabase. No new vendors, no data leaving your stack.

Any LLM, any framework

Works with ai-sdk, OpenAI, Anthropic, and anything that accepts a plain string.