How Wang works

You onboard Wang as your AI employee — your CTO hire. Tell it what you need in plain words and it builds and runs your Wok for you: it sets up the database, auth, storage, realtime, functions, scheduler, email, SMS, hosting, the built-in AI model, and key management, then builds your app on top, checks each part actually works, and gives you something live. You own what comes out — the features, the code, the look of the software that runs your business. Wang builds against a live Wok throughout the process, so what you get back has already been provisioned, deployed, and tested on the real system you'll use.

✦

Try Wang now — open the dashboard, sign up, and type what you want to build. Wang has the full toolset (provision a Wok, run SQL, deploy functions, register domains, send email, top up credits) and will call the right tools, recover from errors, and show you what it did with verification links.

✦

Most tools hand you the parts and leave you to wire them together and put them online — and things break in the gaps. Wang does the whole job and checks it works before handing it over, so you don't get "it worked on my screen but broke when it went live."

How Wang builds your Wok

Every change — whether you asked for it or Wang did it — goes through the same four steps on your real Wok:

Work on the real thing — Wang changes your actual Wok, not a draft or a guess.
Build it — sets up the data, the rules, the automations and the app.
Try it — Wang actually uses what it just built: for a UI, it opens your app in a real browser and reads the console and network requests for errors a plain status-200 check would miss; for data and APIs, it runs the queries and calls and checks the responses.
Fix or finish — if something's wrong, Wang sees the real error and fixes the cause; if it works, it's already live.

Because Wang tests on the real, running Wok, the classic "it worked while I was building it but broke when it went live" problem doesn't happen.

✦

Selling, built in — payment is pre-integrated, so anything Wang builds across your funnel can take money without you wiring up a processor. Fill in a little basic info to take your first $600 by card, then a quick KYC/KYB check when you're ready to withdraw.

What Wang can actually do

Ask in plain words and Wang takes the action — set up a Wok, change your database, deploy code, schedule recurring jobs, add logins, register and wire up a domain, put your site online, send and read email, search what you've taught it, top up credits, and connect Slack or Telegram. Developers can drive the same actions directly over the API.

Teach Wang about your business

Onboarding is a conversation: Wang wants to understand where your business is now, where you want it to go, and the end goal — so it can act like a CTO who already works for you. You can hand it your brand up front too — drop in a Claude Design artifact and it picks up your themes and colors. Beyond that first chat, you keep teaching it in the dashboard's Wang tab:

Instructions — a short set of rules Wang always follows: tone, naming conventions, "always provision in ca-central-1", "confirm with me before buying any domain", "we bill in CAD". They're layered on top of Wang's base behavior (and never override the safety rules), so every chat acts like it already works at your company.
Knowledge — keep a small set of plain-text facts that Wang itself should remember: your menu, operating policy, naming conventions, or product details. Wang searches them on each question (typo-tolerant) and answers from your facts instead of generic defaults.
App Documents — when an app needs a large, governed corpus, open its Documents resource. TellWang spins up LangChain or LlamaIndex on request, vectorizes large batches, applies principal/role/group/deny rules before anything reaches a model, and lets you build or turn off a support agent whose answer claims are checked against their cited passages, create new files from selected sources, or analyze the collection. A file can be blocked for one customer-facing agent while remaining available for internal generation and insights. Generated files remain in Documents after refresh. A hard “Do not use” action removes an indexed file from all three uses.
Replay & analytics — choose an app, then inspect its Published sessions or switch to Preview when a staging Wok exists. Replay is owner-controlled, sampled, retention-bounded, and privacy-masked; it is an operational system app rather than another chat or document folder.
Design system — upload your brand as files: a Claude Design export, a tokens.json, a theme.css, a brand guide. Wang reads them when it builds and matches your colors, type and spacing instead of a tasteful default — and a stylesheet of your tokens is auto-served at /assets/tokens.css in every Wok, so generated pages reference your brand variables directly.

Your instructions and knowledge base apply everywhere Wang runs — the dashboard chat and the Slack/Telegram channels — so the whole team gets the same context-aware Wang; your design system applies whenever it builds a frontend.

Picks up where you left off

Wang's answer appears as it's written, so you see progress instead of waiting for a wall of text. Your conversation is saved too — log in from any device and the thread is still there.

One Wang, every channel

Connect a Telegram or Slack bot in the dashboard's Channels tab — paste your bot token and your team can message Wang from the chat app they already live in. Wang answers there grounded in the same instructions and knowledge base it uses everywhere, so a teammate asking in Slack gets the same answer as one asking in the dashboard. Engineers drive that same Wang and the same Wok over MCP (Cursor, Claude Code) or the REST API.

Confirmation & guardrails

Wang handles safe, undoable work on its own, but asks first before anything risky — deleting data, buying a domain, sending email, spending money. And it can only ever touch your team's own Wok — never another team's, even if someone tries to trick it into it.

Portable by default (shipped)

A Wok is yours to take. Your data is plain Postgres you can pg_dump on any plan, so it's always yours. On Pro and Scale, a Wok's entire definition — schema, policies, functions, env, storage config, scheduled jobs, and infra shape — also exports to Terraform HCL in one call:

export.sh

curl https://tellwang.com/v1/woks/$WOK/terraform \
  -H "Authorization: Bearer $TELLWANG_KEY" > wok.tf

terraform init && terraform apply
# → redeploys this Wok on a different cloud, your own account, or self-hosted.

No lock-in: TellWang earns its keep by running your Wok well, not by trapping it.

Proven in practice

We built a full point-of-sale system this way first, and building on the live system beat writing code and deploying it separately every time. TellWang is that, packaged for your team.