TellWang vs Supabase
People searching for a Supabase alternative usually aren't unhappy with Postgres, row-level security, or the client API — they want less of the assembly and operating work that sits around them. That's the actual difference here. A Wok speaks the Supabase API, so @supabase/supabase-js works against it unmodified. What changes is who builds and runs the stack: on TellWang, an agent does.
supabase-js at your Wok's URL and anon key and the same client handles auth, storage, realtime, and functions — see the quickstart.What's the same
Postgres underneath. Row-level security as the authorization model. A PostgREST-style REST API generated from your schema, JWT-based auth, file storage, and realtime postgres_changes subscriptions. If you've built on Supabase, nothing about a Wok's data layer will surprise you, and code you've already written keeps working.
What's different: who does the work
Supabase hands you excellent parts and a good console, and your team does the rest — design the schema, write the policies, wire auth, deploy functions, set up storage rules, and keep all of it healthy after launch. For a team that wants hands on every dial, that's the right shape.
On TellWang the dial-turning is the product. Tell Wang what you need and it provisions the Wok, writes the schema and row-level-security policies, deploys the functions and the frontend, then opens the result in a real browser and reads the console and network requests before calling it done. The operating work after launch — scheduled jobs, email signing, domain TLS, key rotation — stays with Wang too. How Wang works walks through the build loop.
| TellWang | Supabase | |
|---|---|---|
Postgres + RLS + supabase-js API | ✓ (API-compatible) | ✓ |
| Who builds the schema, policies, functions | Wang, the agent | Your team |
| Email signing, domain TLS, cron, key rotation | Built in — Wang operates them | Wire up + maintain yourself |
| Static hosting + custom domain | Built into the Wok — no separate Vercel/Netlify | A separate service you add |
| What MCP controls | The whole platform — provision, SQL, deploy, domains, email | Mainly the database |
| Leaving | pg_dump (any plan) + Terraform HCL (paid plans) | Open source / self-host |
Driven end-to-end by coding agents
Cursor and Claude Code connect to the TellWang MCP server at https://getlollipop.ai/v1/mcp and get the whole platform as tools, not just the database: provision a Wok, run SQL, deploy edge functions, publish the frontend, connect a domain, send email, and verify the live app through the same control plane Wang uses. One MCP session takes a project from nothing to a working URL.
Leaving is allowed
The data is plain Postgres you can pg_dump any time, on any plan. On every paid plan, a Wok's entire definition — schema, policies, functions, env, storage config, scheduled jobs, and infra shape — also exports to Terraform HCL in one API call. Moving in works the same way in reverse: repoint supabase-js, restore your data, go.
Common questions
Is TellWang compatible with supabase-js?
Yes. A Wok speaks the Supabase API, so @supabase/supabase-js works against it unmodified — point it at your Wok's URL and anon key. The same client handles auth, storage, realtime, and functions, not just the database.
Can I move an existing Supabase project to TellWang?
App code written against supabase-js keeps working once it points at a Wok. The database is standard Postgres, so schema and data move with ordinary pg_dump and restore. Storage objects and auth users move in a separate step; Wang can help.
Does TellWang lock me in?
The data layer is plain Postgres you can pg_dump on any plan. On every paid plan a Wok also exports its entire definition — schema, policies, functions, env, storage config, scheduled jobs, infra shape — to Terraform HCL in one API call. You can redeploy the same Wok on another cloud or self-hosted.