Launch static websites with validation, domains, and AI guardrails built in
DocuHost is a control plane for Cloudflare Pages websites. Bring a ZIP, register GitHub metadata, or submit a constrained AI schema, then track validation, deploy, domain, SSL, and credit state from one workspace.
Static only
Vite-first generation
DocuHost keeps launch scope tight so every generated project is deployable on Cloudflare Pages.
16 gates
Validation before success
Install, typecheck, lint, build, preview, SEO, accessibility, performance, compatibility, and secret hygiene.
1 fallback host
Always-on default hostname
Every site keeps a working `*.docuhost.cloud` address even while custom domain setup is still in flight.
Launch path
Uploads in, status out, nothing privileged exposed
ZIP source uploads
Create a signed upload session, send a ZIP directly to R2, and finalize it into a queued validation/deploy workflow.
GitHub import metadata
Register repository, branch, and commit metadata without exposing privileged deployment controls through the public API.
Schema-based AI jobs
Capture site type, audience, CTA, sections, visual direction, SEO, and legal requirements before generation begins.
Tightly scoped
Build static sites, not surprise infrastructure
DocuHost is designed for landing pages, brochure sites, docs, portfolios, waitlists, and campaign pages. Dynamic backends, databases, and custom APIs stay out of scope at launch.
- Cloudflare Pages as the deployment target
- ZIP import, Git import, and AI text-to-website
- Static-only enforcement before anything goes live
Operationally clear
Every deploy shows the exact state of the pipeline
Users see install, validation, build, deploy, domain, and SSL states in plain language instead of guessing whether a job actually succeeded.
- Queued, running, failed, deploying, and live states are explicit
- Validation reports stay visible with technical detail and human summaries
- Rollback and deploy history become product features, not support tickets
AI with boundaries
A constrained builder, not an unconstrained coding agent
AI requests are schema-first, static-only, and Vite-oriented. When a request needs backend behavior, DocuHost refuses it and suggests a static alternative.
- Section-based site generation rather than arbitrary app scaffolding
- Credit estimates before expensive jobs
- Change summaries, token usage, and failure reasons on every AI run
No green check until every required gate passes
Custom domains never replace the safety net
Every DocuHost site keeps a managed default hostname, then layers custom domains on top with platform-controlled verification, SSL state, and DNS instructions. If custom DNS breaks, the fallback hostname still works.
Provisioned from the moment the site exists.
DNS instructions, verification, and SSL state stay visible to the user.
Monetize the site platform, keep the scope clean
Start here
Free
$0
A single static site with the default hostname, limited AI credits, and enough visibility to get something live safely.
Operational plan
Pro
$29 / month
More sites, custom domains, better logs, rollback, and a much stronger AI allocation for real launch work.
Secondary utility
Keep the files workspace, but do not let it drive the product
The original file-sharing flow still lives in the workspace for handoffs and asset delivery. It is preserved as a useful side feature, not the main product narrative.
Open files utility