The stack

A Wok bundles everything a team needs to run software: database, auth, storage, realtime, functions, scheduler, email, SMS, hosting on your domain, a built-in AI model gateway, and key management. Wang turns each piece on as you need it; you never assemble or wire them yourself.

What's inside

Database — dedicated Postgres 15, instant REST API, RLS, six-hour logical backups, point-in-time recovery.
Logins & users — GoTrue email/password + OAuth (Google, GitHub, Apple, Azure, +10 more).
Files — S3-compatible API, public + signed URLs, RLS-aware buckets.
Live updates — postgres_changes streaming, broadcast, presence — all via channels.
Your own code — Deno-flavored TypeScript edge functions, optionally DB-triggered.
Cache & job queues — Redis 7 wired in by default; process.env.REDIS_URL in every edge function. BullMQ-ready.
Scheduled jobs — pg_cron inside the Wok; no separate cron host to manage.
Email — transactional send + inbound receive on your own domain, via Resend.
Text messages — send + receive SMS from a number your Wok owns; inbound texts run an edge function.
A home for your app — static frontend at the Wok's edge + custom domain with Let's Encrypt TLS on demand.
Built-in AI — OpenAI-compatible streaming gateway with TellWang's private vision-language model.
Key management — generate keys and encrypt, decrypt, or sign (including Solana) through the Wok; private keys stay in the control plane.

✦

Wang flips each piece on as needed. The lightweight data plane is present from the start; heavier capabilities such as Realtime and managed RAG run only when enabled. For the canonical surface, see api-reference → Wok internals.

What it looks like in practice

One Wok provisioning + a handful of cp calls = a full functional product. Here's the customer-onboarding portal from the landing page, wired top-to-bottom:

onboarding.sh

# 1. Spin up the Wok
curl -X POST https://tellwang.com/v1/woks \
  -H "Authorization: Bearer $TELLWANG_KEY" -d '{"name":"onboarding"}'

# 2. Schema + RLS in one SQL hit
curl -X POST https://tellwang.com/v1/woks/onboarding/exec_sql \
  -H "Authorization: Bearer $TELLWANG_KEY" \
  -d '{"sql":"create table signups (id serial primary key, name text, email text, role text, created_at timestamptz default now()); alter table signups enable row level security;"}'

# 3. Edge function to receive the form POST
curl -X POST https://tellwang.com/v1/woks/onboarding/functions/signup \
  -H "Authorization: Bearer $TELLWANG_KEY" -d @signup-fn.json

# 4. Cron job — Monday 9am digest
curl -X POST https://tellwang.com/v1/woks/onboarding/scheduler/jobs \
  -H "Authorization: Bearer $TELLWANG_KEY" \
  -d '{"name":"monday-digest","schedule":"0 9 * * 1","command":"select net.http_post(...)"}'

# 5. Push the static frontend (same-origin to all Wok services)
curl -X POST https://tellwang.com/v1/woks/onboarding/frontend \
  -H "Authorization: Bearer $TELLWANG_KEY" -d '{"files":{"index.html":"...","app.js":"..."}}'

# Done — live at https://onboarding.tellwang.com

Wang composes the same calls on your behalf when you ask in plain English. Every one of these endpoints is documented in api-reference.

Lean by design

A Wok runs only what it needs — not a pile of services you'll never use. That keeps it fast, cheap to run, and simple to reason about.

All yours to keep

Your data is plain Postgres, exportable with pg_dump on any plan. On Pro and Scale, everything in your Wok also exports as standard Terraform HCL in one call (GET /v1/woks/{id}/terraform), so you can redeploy it on another cloud, your own account, or self-hosted — see How Wang works → Portable by default for the working example. We earn your business by running it well — not by trapping your data.