Static sites
Upload a folder and it is served from its own address. Without a plan, three sites are free.
Free and paid sites
A static site made while you have no plan is a free site. One made while you have a plan is a paid site. A site keeps the kind it was made with.
| Free site | Paid site | |
|---|---|---|
| Plan | none needed | counts as one of your plan's services |
| Sites | 3 per account | as many as your plan's services allow |
| Size per upload | 100 MB | 1 GB |
| Files per upload | 2,000 | 50,000 |
| Address | <label>.projectwabi.app, through Cloudflare | <label>.projectwabi.app |
Both kinds share projectwabi.app and its wildcard certificate, so every site is on HTTPS from its first upload. A free site's address goes through Cloudflare, which takes its traffic in front of wabi, and wabi accepts that site's requests only from Cloudflare.
The label defaults to the service name and is unique across wabi (Domains).
Upload a folder
- Build your site so that you have a folder with
index.htmlat its top, such asdist/orpublic/. - Create a static service in a project, or open an existing one.
- Choose the folder in the dashboard.
Your browser packs the folder into a tar file and uploads it straight to storage. An upload over the site's size or file limits is refused before it starts. Each upload gets its own upload URL, valid for 5 minutes.
The folder must hold regular files and directories. Symbolic links, hard links and paths that leave the folder are refused.
Every upload is scanned
Before an upload goes public, wabi scans it for phishing and wallet drainers, including pages that imitate well-known wallets, exchanges and projects. The deployment shows scanning while this runs.
- An upload that passes moves to
deployingand thenlive. - An upload that matches is
heldfor review. If the review approves it, it goes live. If it breaks the Acceptable Use Policy, it is taken down and the deployment endsfailed.
While an upload is scanned or held, the site keeps serving its current files.
wabi fingerprints the bytes it scans and publishes only a file with that fingerprint, so what goes live is exactly what was scanned. Published sites and web services are also checked daily against Google Web Risk lists.
Switching versions
A new upload is unpacked beside the version that is live, then the site switches to it in one step, so visitors never see a half-updated site.
If an upload fails at any point, the site keeps serving the version it had.
How files are served
Each file is served with the content type of its extension, together with X-Content-Type-Options: nosniff, so a browser treats a file only as the type its extension says.
No server code runs for a static site. It has no variables, no build on wabi and no size to set: build locally, then upload the output.
Custom domains
With a plan, a static site takes your own domains the same way a web service does, and each one counts toward your plan's custom domains (Domains).