---
title: Pricing and limits
description: Hosted launch pricing posture, implementation limits, and Cloudflare-dependent constraints.
---

# Pricing and limits

The hosted launch has no billing flow in the current source. The practical model is free while available, with limits enforced by the CLI, API, and Cloudflare.

Self-hosted deployments run in your Cloudflare account. You pay Cloudflare for the resources, traffic, storage, logs, domains, and any platform usage your install creates.

## Source-enforced limits

The current source defines these deploy limits:

| Limit                          |           Value |
| ------------------------------ | --------------: |
| Maximum files per deploy       |           5,000 |
| Maximum single file size       |          10 MiB |
| Maximum total deploy size      |      50,000 MiB |
| Maximum manifest body          | 5,185,536 bytes |
| Deploy preparation TTL         |          1 hour |
| Anonymous project metadata TTL |          7 days |

The total deploy-size constant is intentionally much larger than many practical hosted limits. Cloudflare account limits, request limits, rate limits, Worker limits, abuse controls, and launch policy can reject deploys before that theoretical maximum.

## Expiration behavior

New projects created through the hosted API have project metadata that expires after 7 days unless a non-default domain is assigned.

Static asset publication is updated when the API rebuilds and republishes the manifest. Metadata expiration is therefore not a real-time purge guarantee for already published public URLs. Assigning a non-default project domain removes the metadata expiration while that domain is assigned. Deleting the assigned domain resets the project back to its generated domain and starts a fresh 7-day metadata expiration. Deleting the project removes the project metadata and removes it from the published manifest.

## Custom domains

External custom domains require Cloudflare Custom Hostnames support in the account running the service. The API returns a CNAME target in the form `cname.<base-domain>`; hosted `wgw.lol` returns `cname.wgw.lol`.

DNS propagation, certificate issuance, Cloudflare validation, and hostname conflicts can delay or prevent activation.

## Reserved names

Some project names are reserved and cannot be used as generated project names or subdomains. Current reserved names include `deploy`, `cname`, `x`, `www`, `api`, `admin`, `login`, `app`, `assets`, `cdn`, `mail`, `ftp`, `smtp`, `pop`, `imap`, `status`, and more.

## No SLA in code

The repository does not implement a hosted SLA, paid tier, overage billing, support entitlement, or uptime guarantee. Treat launch hosting as a convenience service for static sites, not as a contractual hosting product.

For production-critical use, self-host in your own Cloudflare account or keep another deployment path available.