Publish
A live URL in one click.
A web deploy builds the current files on your main branch and publishes them to a shareable URL on managed hosting. Contrast owns the infrastructure. You pick a slug and press deploy.
Production hosting is $10 per live web project each month. The base includes the Contrast URL, routing, TLS, backups, observability, and one custom domain. Run usage is not charged while durable metering is built and calibrated.
Before you deploy
Verify the app in Dev first. The dev preview runs the same build the deploy will, so a broken web preview means a broken deploy. Deploys build from main, so land the work you want to ship onto main before you deploy.
Deploy
- Open the Deploy space and find the Web target.
- Press Deploy. A confirm dialog (Deploy web app or Redeploy web app) states that it builds the current files on main and publishes them.
- Pick or accept the slug, your subdomain. It must be 3 to 30 characters of
lowercase letters, numbers, and hyphens, for example
acme-store. Contrast derives a default from the project name. - Confirm. The Web section tracks the build (Web deploy pending then Published web app) and shows the production URL when it is live.
Your app comes up at https://<slug>.contrast.run, for example
https://acme-store.contrast.run. It runs on managed Cloudflare Workers and
Durable Objects, with its database and Zero sync hosted in-process. There is no
Postgres to provision. The stack explains the full production
shape.
Use your own domain
To serve the same deploy from a domain you own, such as www.example.com, attach
a custom domain from Deploy pane → Web → Custom domain. See
Custom domains for the DNS record and SSL details.
Verify it
Open the Production pane to inspect the real deployed app and click through it. See Production for what each pane in that section shows.
If it does not deploy
- “does not support production web hosting yet”: the template is frontend-only. The Website template publishes local previews only until static hosting lands. App and Game deploy to production. See Deploy targets.
- Production logs are empty: the Health pane reads managed logs from Cloudflare’s Workers Observability telemetry. If that access is not configured for the deployment, the pane says so; fall back to its Worker and Durable Object stats.
- Deleting a deployment did not take the site down: delete only clears history from the pane. It does not unpublish the live URL.