Platform · Static hosting
Static hosting for Vite and prebuilt sites
A clear release workflow for landing pages, documentation, and small browser apps. Bring your build output, review a private preview, and publish when you're ready.
Limited early access with shared request and storage capacity. Check current signup availability and limits before moving a site.
From build output to a live release
-
Prepare your site
Build locally or in your own CI. ZIP the contents of the output directory with
index.htmlat the archive root. Include public assets and use relative asset paths. -
Stage a private preview
Open your workspace and create a project. In the project's Deployments section, choose Upload a ZIP. Your staged release is ready to preview before publication.
-
Review, then make live
Check pages, assets, and navigation in the preview. Open Details for the staged release, choose Make live when it is ready, then open the project URL.
Deploy from a terminal or CI
Install the CLI with Node.js 22 or later. Create a project deploy token in deployment history and set STACKR_DEPLOY_URL and STACKR_DEPLOY_TOKEN in your terminal or CI environment.
For a Vite project with its default output directory and zip installed, run these commands from the repository. Vite build guide
npm install -g https://stackr.grasany.com/grasany-stackr-cli-0.13.0.tgz
npm run build -- --base=./
(cd dist && zip -r ../site.zip .)
stackr deploy-static site.zip --tag v1
Delivery can generate a workflow for GitHub Actions, GitLab CI, or Bitbucket Pipelines to build and stage pushes to your selected branch. Another runner can use the same CLI and project deploy token. Set up CI deployment
Know the limits before uploading
| Resource | Current limit |
|---|---|
| ZIP size | 512 KiB compressed and 1 MiB unpacked |
| Individual files | 40 files per ZIP and 256 KiB per file |
| Retained static files | 5 MiB per project |
| Shared static storage | 120 MiB across Stackr |
| Included workspace requests | 10,000 per UTC calendar month across projects |
| Shared hosting capacity | 15,000 requests per UTC day across Stackr |
Browsers request pages, scripts, styles, images, and fonts separately. Static preview requests also count toward these limits. Stackr returns HTTP 429 when the daily or monthly request limit is reached. Include costs for any separate backend or CI runner when planning your site. Free workspace and availability
Keep a clear release history
A staged upload leaves the current live release in place while you review. Deployment history keeps your retained releases available for comparison and recovery. Select an earlier retained release to restore it. Named previews and gradual rollouts are available in Delivery for compatible releases.
Package the scripts and assets that your pages load. For single-page apps, test nested routes and consider hash routing for reliable relative paths in previews.
What can run on static hosting?
A static site serves files built ahead of time. Its JavaScript can run in the visitor's browser, so a site can include interactive pages or a product catalog.
For hosted Supabase, connect your existing project using a publishable key and enable browser access for the live release when you need it. A site that needs request-time rendering, private API keys, checkout sessions, or server-side logic needs a compatible backend. Check what your application requires before moving it. Vercel migration guide