Web Hosting

Mach Web Hosting is the managed static delivery product. It is separate from mach host, which keeps the existing AWS S3 and CloudFront workflow, and it is separate from OTA updates. Your computer or CI builds the site; Mach receives only the finished static output and serves it through Mach's managed global delivery edge.

This makes it a good fit for Expo Router web exports, React Native Web, Flutter web, landing pages, and SPAs. It does not run customer server code, SSR, databases, or deployable serverless functions.

In Dashboard → Web Hosting, the project owner chooses the production subdomain before the first release. Mach starts with the project slug, so a project named shopreceives the following addresses:

The selected subdomain is globally reserved and becomes locked after the first deployment. This protects links already shared with users, reviewers, and search engines. Service names such as api, ota, files, and mcp cannot be claimed.

Mobile profile names and web aliases solve different problems. Keep your existing names such as qa-mobileor store-release, then map each profile explicitly. Mach never guesses a public URL from a profile name and never copies mobile build secrets into a static web export.

Build where your source already lives—on a developer machine or in CI. The CLI uploads only the output directory. A deployment must contain index.html at its root.

Uploads are batched and sent directly to private Mach storage using short-lived signed URLs. The Mach API stores deployment metadata and does not proxy your website files.

Each upload is immutable. Promotion changes the small alias record that points Production or Staging to one release. Rolling back points that alias at an earlier ready release, so neither action rebuilds or overwrites files.

Dashboard → Web Hosting has the same controls, the immutable preview link, file count, output size, profile, branch, and commit. The unified Release History also shows web deployments alongside native builds.

Free accounts receive 1 GB of retained static storage and 100,000 hosted requests per UTC calendar month, shared by every project the account owns. Open Dashboard → Web Hosting → Usage to see the account totals.

Storage is measured from retained deployment output when a release completes. Requests are reconciled from the previous complete UTC day, so request enforcement is intentionally daily rather than instant. Mach does not write an analytics event or call the Mach API for each visitor request.

Give CI a scoped Mach token, install the CLI, and let the repository build the web output. The profile mapping keeps release intent visible in source control.

The CLI records available branch and commit metadata automatically. Use --no-promotefor pull-request previews, then promote a reviewed deployment by ID.

The included *.getmach.devaddresses are ready immediately. Customer-owned domains are a Premium capability that the Mach operator enables after automated certificate and fallback-origin setup is complete. When enabled, a customer domain always serves Production for now—not Staging.

After adding a domain, open Dashboard → Web Hosting → Domains. Mach displays the CNAME and, when needed, the HTTPS verification record for that hostname, with copy buttons for each value. The table marks detected records separately from records that still need action. Add only the records marked Action required, wait for DNS to update, then select Refresh. The address is not ready until both DNS and HTTPS are active. A subdomain such as www.customer.com is usually easiest; a root domain needs a DNS provider that supports ALIAS, ANAME, or CNAME flattening.

Static web apps can call your normal Mach API or another backend, but browser-visible environment values are public by nature. Keep database credentials and server secrets out of the web bundle; use a backend for privileged work.