TellWang
Dashboard
Products / Hosting & Domains

Hosting & Domains

Put your website online on a domain you own, with HTTPS set up for you. Static frontend + custom domain + auto-TLS — no DNS plumbing.

Ship a static frontend (shipped)

Upload your built static site as a JSON map of path → content. index.html is required (the frontend is served SPA-rooted there). The cp writes the files into the Wok's edge bind-mount and installs the edge route in one shot:

deploy.sh
curl -X POST https://tellwang.com/v1/woks/$WOK/frontend \
  -H "Authorization: Bearer $TELLWANG_KEY" \
  -H "Content-Type: application/json" \
  -d '{"files":{
        "index.html": "<!doctype html>...",
        "assets/app.js": "console.log(\"hi\")",
        "assets/style.css": "body{margin:0}"
      }}'
# → 200 { wok_id, files, bytes, frontend_url }

Same-origin Supabase paths — the edge proxies /rest/v1, /auth/v1, /storage/v1, /functions/v1, and /realtime/v1 verbatim to your Wok's services, so a supabase-js client pointed at frontend_url needs no CORS configuration. GET /frontend lists deployed files + sizes; DELETE /frontend tears down the edge route + clears the bundle.

Custom domains (shipped)

Two flavours: (1) register through TellWang via Cloudflare Registrar (see Domains API), or (2) bring your own — point the apex/subdomain at the TellWang edge with one CNAME and HTTPS gets issued + renewed automatically via Let's Encrypt.

attach-existing.sh
# 1. On your DNS host (Cloudflare, Namecheap, Route 53, …) add a CNAME:
#    www.acme.com → edge.tellwang.com

# 2. Bind that hostname to your Wok (registers it for TLS on-demand)
curl -X PUT https://tellwang.com/v1/woks/$WOK/domains/www.acme.com \
  -H "Authorization: Bearer $TELLWANG_KEY"
# → 200 { wok_id, domain, tls:"on-demand", verify_url }

# 3. Verify the binding (HTTPS probe against your-domain/__tellwang/dns-verify)
curl https://tellwang.com/v1/woks/$WOK/domains
# → 200 { domains: [{ domain, dns_status: "verified", attached_at }] }
✦
The TLS cert is issued on the first HTTPS hit to your custom domain — no cert pre-provisioning step. Renewal runs ~30 days before expiry.

API reference

Roadmap