FAQ

Honest answers about Webstead + the beta.

What works today, what doesn't, and how Webstead compares to running the IC yourself.

What's in the box · what isn't

Honest about the beta.

What works today
  • Mainnet ICP asset-canister deploys (we run the deploy, we pay cycles)
  • GitHub import with auto-detected framework presets (Vite, CRA, Astro, Next static export, custom)
  • Auto-deploy on git push via GitHub webhook
  • Direct file/ZIP upload
  • Build-time environment variables (encrypted at rest, injected as -e KEY=VALUE)
  • Custom domain wizard with DNS instructions + IC gateway probe + primary-domain selection
  • Per-site cycle budget + auto-pause when spend hits 90%
  • Self-serve site rename + delete with mainnet cycle reclamation
  • Public /status page with worker liveness, 24h success rate, queue depth
Not in the beta yet
  • SLA — best-effort uptime, no contractual guarantees
  • Automated self-custody export (it's documented + support-mediated)
  • Per-team / per-org collaboration; one user per workspace
  • API keys for programmatic access (CLI / CI integrations)
  • Preview deploys per PR
  • Billing — beta is free; paid plans land before GA
FAQ

The questions you'd ask before signing up.

What is the Internet Computer?

A blockchain that runs full applications, including HTTP servers, at smart-contract level. Your assets live in an 'asset canister' — a small program with its own state and HTTP handler — replicated across a global subnet of nodes. No origin server, no CDN.

Can I leave Webstead and keep my site?

Yes. Every customer canister is yours by ID. Today we transfer controller ownership on request (support-mediated). Automated one-click export is on the GA roadmap. Your canister ID + recipe version is visible on /account/export at any time.

How is this different from Fleek, Spheron, or self-deploying with dfx?

Fleek and Spheron also host on IC, but Webstead is opinionated about a Vercel-style UX: connect a repo, auto-detect the framework, push-to-deploy, custom domain wizard, cycle auto-pause, build env vars. If you'd rather hand-craft icp.yaml and manage cycles yourself, use the icp CLI directly — we just package the boring parts.

Custom domains — do they really work?

Yes, via the IC's official custom-domain gateway. Add your domain, copy the DNS records we generate, click 'Check setup'. We probe the gateway and flip the badge to active when the records resolve. Multiple domains per site supported, with one marked as primary.

What about environment variables for builds?

Set VITE_API_URL, NEXT_PUBLIC_*, or any KEY on the Environment tab of any site. Values are AES-256-GCM encrypted at rest and injected into the build container via -e KEY=VALUE. They're build-time only (asset canisters don't have a runtime to read env vars at request time).

Who pays for the cycles?

We do, during beta. Each site gets a budget; if spend hits 90% of the budget the site auto-pauses to protect the platform cycle pool. When billing ships you'll either fund cycles yourself or stay on a paid plan where we cover them.

Create accountSee pricing →