Tenancy & isolation

Every team's Wok is its own private setup. Your data is isolated from every other tenant from the moment the Wok is provisioned — at the database layer, at the network layer, and at TellWang's authorization layer.

Your own database

Each Wok gets its own Postgres instance in its own container, with its own credentials — not a shared table with a "company id" column you have to trust. A bug in someone else's app simply can't reach your data, because it's a different database.

Each Wok also runs on its own private network, so no other team's services can reach yours — even when they share a host. Inbound requests are routed to your Wok by hostname, and no other tenant ever sees it.

Authorization boundary

Every request that touches a Wok is authorized server-side against the team that owns it. If it comes from another team, the response is a 404 with no leak (not a 403 — the Wok's very existence isn't revealed). A leaked key from one company can never operate on another company's Wok, even with a correctly-guessed Wok ID.

TellWang enforces this on every request.

Isolation tiers

Every paid plan runs your Woks on your own private server. Free Woks run on the shared platform, each with its own database and services in their own containers, isolated at the database, network, and authorization layers. Teams whose compliance calls for a sandboxed runtime or confidential-compute hardware can arrange it with us. See isolation.

Built to survive failures

Your Wok's database, storage files, and deployed code are backed up to storage in a separate availability zone. Continuous WAL archiving keeps the database recoverable to within minutes. Recovery is exercised against scratch space rather than live data, so a restore is never rehearsed on top of something you depend on.

Where it runs: the free shared platform runs in AWS Canada (ca-central-1). Private servers for paid plans run on Cherry Servers in US-Chicago; Scale + HA and Enterprise add a second server in LT-Siauliai. Backups survive a host or availability-zone failure.