Your bucket is also a website.
Point a domain at your Storm Bucket and the static files serve. A stormsites.ca subdomain out of the box, or your own custom domain. The same bucket holds your storage and your site.
A site, straight from a bucket.
Put your files in a Storm Bucket and they serve. No separate repo, no build pipeline required. The same bucket holds your storage and your site, on one set of keys.
Subdomain or your own domain.
Every hosting-enabled bucket gets a stormsites.ca subdomain out of the box. Point your own domain at it whenever you're ready. Either way, the files are served from Montreal on Canadian-owned hardware.
Why not GitHub Pages?
GitHub Pages serves a site from a git repo. Storm serves it from an object-storage bucket. Storage is the better fit when your content is large, binary, generated, or pushed from a pipeline rather than committed by hand.
Your storage and your site are the same bucket. No separate repo to keep in sync, no separate asset host for the images and video behind the pages.
The files sit in Montreal on Canadian-owned hardware, under Law 25, with no CLOUD Act data-access exposure. If jurisdiction matters to you, that's settled by where the files physically sit.
Where GitHub Pages wins It's free, it's proven, and the workflow is excellent. If your content lives in git and you don't care about jurisdiction, GitHub Pages is the right pick. That's the honest call, and it's most people.
Hosting is included. You pay for storage.
A $1 / 100 GB block holds a lot more than one site. It holds many sites and the images, video, and PDFs behind them, in the same bucket. Host as many stormsites.ca subdomains as fit in your storage. Hosting adds nothing to the bill.
Storage is billed in blocks, not per byte: $1 per 100 GB, or $9 for a full TB.
01 How is this different from GitHub Pages?
GitHub Pages serves a site from a git repo. Storm serves it from an object-storage bucket. The same bucket is your storage and your site: one set of keys, no separate repo, no separate asset host. It's the better fit when your content is large, binary, generated, or pushed from a pipeline. And it's Canadian-hosted under Law 25.
02 What can I point at it?
Anything that speaks S3, path-style: rclone, the AWS CLI, Cyberduck, your build pipeline. Upload your files to the bucket and they serve.
03 Is my data only in Canada?
Yes. The files sit in Montreal, under Law 25, with no CLOUD Act data-access exposure.
04 What happens if Storm disappears?
It's standard object storage over a standard S3 API. Your tooling already knows how to walk away: point rclone or the AWS CLI somewhere else and copy your files out. Nothing proprietary holds them.