Static files and assets
Deploy the complete browser-ready output: its entry page, stylesheets, JavaScript and assets.
Host HTML, CSS and JavaScript files or the static build of your React, Vite or Astro project with nginx. Every application gets a free *.shardweb.app HTTPS address; connect your own domain with Core or higher.
A public address for your build
nginx
static HTML, CSS and JavaScript
index.html + .shardcloud
index.html and static assets
*.shardweb.app
free HTTPS address for every application
Core+
custom domains from Core
Deploy the files visitors load in their browsers. Projects that require server rendering or a backend process need an application runtime instead.
Explore capabilitiesPublish HTML pages, stylesheets, images and JavaScript for a portfolio, landing page or documentation site.
Build your frontend for production and deploy its generated files. Check client-side routes as well as the homepage before launch.
Deploy Astro output generated in static mode. Astro projects using server rendering need a runtime that runs their server.
The static runtime serves browser-ready files through production-configured nginx, CDN delivery and automatic optimization. The deployment guide covers the current configuration format.
Deploy the complete browser-ready output: its entry page, stylesheets, JavaScript and assets.
Choose the static runtime to serve browser-ready HTML, CSS and JavaScript through the platform's production-configured nginx, with CDN delivery and automatic optimization.
Keep static assets on the 10 GB persistent disk across application restarts.
Connect a custom domain with the Core plan or higher when you are ready to publish under your brand.
Use application logs and resource metrics in the dashboard to inspect your deployment.
Application processes restart automatically; use dashboard logs to investigate a deployment that does not start.
Prepare the production files, deploy with the static runtime and test the published site.
Get startedFrom connection to the first decision, in one flow.
Put index.html in the root of your project and set MAIN=index.html in .shardcloud. Keep your CSS, JavaScript, images and other referenced files alongside it so every path resolves.
No. Every application receives a free HTTPS address under *.shardweb.app. Connecting your own domain is available with Core or a higher plan.
Static hosting runs your website as an application served by nginx, with its own public address. The CDN resource provides file storage and delivery for assets such as images and downloads. Choose static hosting for the website itself and CDN for assets you want to store and deliver separately.
Static sites need at least 256 MB. Use 512 MB for public web publication, then increase memory only when observed usage requires it.
The static runtime serves the deployed files through nginx, so no application server needs to bind a port.
Read the full static deployment guide
Publish HTML or a frontend build with nginx and free HTTPS. Compare the current plans below.
Guided setup with no commitment
Production files ready
Locate index.html and the assets generated by your production build.
Deployment guide reviewed
Review the current static configuration guide, then confirm the site and its assets load at the public address.
Publish your static site
Create an application with the static runtime and test its HTTPS address.
Perfect for freelancers or individuals who need to host applications and bots.
For small teams and startups that need infrastructure for multiple projects.
Built for scaling companies with high project volume and advanced support.