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.
Sync your built site to a Storm Bucket and it serves. 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, provisioned to approved accounts under the Acceptable Use Policy. Point your own domain at it whenever you're ready. Either way, the files are served from Montreal on Canadian-owned hardware.
Built for the site your pipeline already produces.
Served out of Montreal, so a Canadian visitor gets a short trip, and the files sit under Canadian jurisdiction.
Hugo, a CI job, rclone, the AWS CLI. Deploy is a sync to a bucket. No repo to keep in step with the site, no build service to wait on, no deploy hook to debug. Connect a client →
Hosting is not a separate line. The block you bought for storage is the block the site is served from, and egress rides the same 3x allowance as everything else on that endpoint.
How it differs, and where it stops.
GitHub Pages serves a site from a git repo. Vercel builds it through a pipeline and serves from its edge network. Storm serves it straight from an object-storage bucket. A bucket is the better fit for generated build output, images, video, and PDFs that belong alongside the pages, pushed by a tool rather than committed by hand.
Your storage and your site are the same bucket. No separate repo to keep in sync, no build step to wait on, no separate asset host for the images and video behind the pages.
GitHub Pages runs on Microsoft's US infrastructure. Vercel is a US company subject to the CLOUD Act. Storm is Canadian-owned and Canadian-operated, with no US parent and no US infrastructure: the CLOUD Act binds US providers, and Storm is not one. The files sit in Montreal on Canadian-owned hardware, under Law 25, Quebec's privacy law, and PIPEDA, Canada's. If jurisdiction matters, it's settled by where the files physically sit.
Static only A bucket serves static files, fixed pages with no login or database behind them; it does not run code. No serverless functions, no server-rendered pages, and no endpoint a third party can upload through. If you are shipping a dynamic app, Storm Sites is not it.
No CDN One node, in Montreal. Canadian visitors get a short trip; international visitors see higher latency. A worldwide edge network is a hyperscaler capital expense, and Storm puts the money into Canadian ground instead.
Priced as storage Hosting rides on a storage block you are already paying for, so the floor is the block price. A single hobby page does not need a terabyte, and Storm does not sell a smaller one.
Hosting is included. You pay for storage.
A $9 / 1 TB block covers a deployed site and the assets it serves, in the same bucket. Hosting is not a separate line on the invoice. What you pay for is the storage the deployment occupies, bounded by the block you bought.
Storage is billed in blocks, not per byte: $9 for a full TB, stacked as you grow.
Storm Sites serves the static content of your own projects, under the Acceptable Use Policy. Reports go to Report Abuse and are acknowledged within 48 hours.
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 for generated build output, images, video, and PDFs that belong alongside the pages, pushed from a pipeline rather than committed by hand. And it's Canadian-hosted under Law 25 and PIPEDA.
02 What can I point at it?
Anything that speaks S3, path-style: rclone, the AWS CLI, Cyberduck, your build pipeline. Sync your site to the bucket and it serves.
03 Is my data only in Canada?
Yes. The files sit in Montreal under Law 25, Quebec's privacy law, and PIPEDA, Canada's. Storm is Canadian-owned and Canadian-operated, with no US parent and no US infrastructure. The CLOUD Act binds US providers, and Storm is not one.
04 How do I move my site somewhere else?
Copy the files down and upload them wherever you're going. It's standard object storage over a standard S3 API, so rclone and the AWS CLI already know how, and your domain follows over DNS. Nothing proprietary holds a static site in place.