Tell Wang
In the app, in Slack, or in Telegram: describe what you need — "set up a customer list with logins and a weekly summary email." Wang builds it on a real Wok, checks each piece works, and sends you a live link.
Tell Wang to make your your way. Tell Wang to build your dream .
For developers (MCP & REST) →Wang and Cursor talk to the same Wok. What one of you sets up, the other can see and change — no parallel system to keep in sync.
In the app, in Slack, or in Telegram: describe what you need — "set up a customer list with logins and a weekly summary email." Wang builds it on a real Wok, checks each piece works, and sends you a live link.
Point Cursor or Claude Code at the TellWang MCP server and your agent provisions, queries, and deploys directly. The REST API and SDK are there if that's the surface you want.
Each Wok is private to your team — your own database and services, strongly separated from everyone else's.
Dedicated Postgres with an instant REST API and daily backups.
Email + password and row-level security wired in from the first request.
S3-compatible API with signed URLs and per-bucket policies.
Subscribe to database changes and broadcast over websockets, no extra infra.
Deploy TypeScript/Deno functions next to your data, with Redis wired in for caching and sessions.
Durable job queues on Redis + BullMQ — payroll runs, print batches, billing. Failed jobs retry, work stays in order, nothing gets lost.
Cron jobs on pg_cron, managed inside your Wok.
Transactional send on your own verified domain.
Send and receive SMS from a number your app owns. Replies run your code.
Ship static frontends and attach custom domains with managed TLS.
An OpenAI-compatible LLM endpoint, metered per plan.
Generate keys and encrypt, decrypt, or sign through your Wok — including Solana transactions. Keys never leave the control plane.
Invite teammates into an org and give each a role — owner, admin, billing, developer, or viewer. The role decides who can build, who handles the money, and who just watches. Flip between your personal workspace and the org's the way you do in Vercel or Linear. And when a build needs more eyes, share that Wang chat with the specific people who should be in it — they see the thread and can steer it, nobody else does.
Top up a credit balance with a card, and usage draws it down — the built-in AI model and the rest, metered as you go. The billing role keeps the card and the invoices with whoever owns the budget, apart from the people shipping.
When you ask Wang for an onboarding portal, the signup page, the team dashboard, the schema behind them, and the Monday digest email get built in the same flow — and tested against each other before Wang hands you the URL.
Build a customer onboarding portal:
- public signup form (name, company, email, role)
- email verification with a one-click confirm link
- a private dashboard where the team sees new
signups, status, and notes
- weekly digest email to me on Monday 9am
A developer can open the browser console, read the error, and trace the failed request. Everyone else just gets a page that doesn't work — and no way to say why. So Wang checks the way a person actually uses the app: it opens your site in a real browser, watches the console and the network, and when something's off it finds the cause and fixes it before the link ever reaches you. The people who can't read a stack trace are the ones this protects most.
Wang owns the work you'd otherwise hire a platform team for: provisioning and tuning Postgres, wiring auth so row-level security holds, scaling realtime channels, running file storage with the right ACLs, deploying your edge functions, running durable job queues and the scheduler, signing SPF/DKIM/DMARC for your domain, renting and routing SMS numbers, managing TLS and hosting, and brokering AI provider keys. That's the platform team you don't have to hire.
TellWang is an agent-native cloud. From a plain-language description it provisions, builds, tests, and ships a complete live backend — called a Wok — and gives you a working URL. The same Wok is reachable through MCP, REST, or the dashboard.
A Wok is a team's whole live backend in one place: a Postgres database, auth, storage, realtime, edge functions, scheduler, email, SMS, hosting on your domain, a model gateway, and key management. Every Wok is private to your team and isolated from every other one.
Yes. The same Wok is reachable three ways: point Cursor or Claude Code at the TellWang MCP server, call the REST API directly, or work in the dashboard. Wang and your IDE act on the same live stack, so nothing has to be kept in sync.
Not yet — SOC 2 is on the roadmap, not certified today. What is in place now: each Wok is isolated at the database, network, and authorization layers, traffic is HTTPS-only, secrets are AES-256-GCM encrypted, and a tamper-evident audit log records every change.
Today every Wok runs in a single region, ca-central-1 (OVH Beauharnois). Multi-region failover and choosing where your data lives are on the roadmap. If your compliance posture needs a specific region now, talk to the founders before provisioning.
Wang sets everything up and checks it actually works before handing it over — so what you get runs right the first time, not after a week of fixes.
Powered by a TellWang Wok — this form runs on the very infra it's signing you up for. · Read the quickstart →
Sizing it for an enterprise rollout, dedicated hardware, or a compliance-scoped Wok? Talk to the founders →