Static websites, not surprise infrastructure
Build and operate landing pages, brochure sites, docs, portfolios, waitlists, and campaign pages on Cloudflare Pages. Upload a ZIP, register GitHub metadata, or use schema-based AI with visible validation gates and fallback hostnames.
Choose how you want to create
The launch contract is intentionally narrow: ZIP bundles, GitHub-linked static sources, or a constrained AI builder that outputs deployable static projects.
Upload ZIP
Send a static site bundle into the validation and deployment queue.
AI Builder
Describe a brochure-style site through a constrained schema, then deploy the result.
Import from GitHub
Register GitHub metadata for supported static projects without exposing privileged controls.
Operate the release path in plain view
Validation-first releases
Success is not implied. Install, lint, build, preview, SEO, accessibility, performance, and compatibility checks stay visible.
Fallback hostnames
Every site keeps a managed `*.docuhost.cloud` hostname so DNS or SSL issues never remove the recovery path.
Constrained AI
AI generation stays static-only, Vite-oriented, and scoped to landing pages, brochure sites, docs, portfolios, and waitlists.
Launch in 3 controlled steps
Create a site shell
Reserve the managed fallback hostname and choose ZIP, GitHub, or AI as the intake path.
Submit source
Queue a ZIP bundle, GitHub metadata, or a schema-based AI request into the shared release flow.
Watch the gates clear
Validation, build, and deploy states stay visible before the site turns live.
Free keeps the launch scope tight and usable
Start with one static site, the managed fallback hostname, limited AI credits, and basic validation visibility. Upgrade when you need more sites, custom domains, rollback, and stronger AI capacity.
Ready to launch your next website?
Start with one static site, then move to Pro when you need custom domains, stronger logs, rollback, and more AI credits.
Static websites only at launch