Hosting Readiness

WeAcuRe should launch as a static cultural study site before any custom server, database, checkout backend, or member system is introduced. Hosting choices should protect the private repository, reduce origin exposure, and keep security headers intact.

Preferred first deployment

Before connecting a domain

• Deploy to the Cloudflare Pages default preview domain before binding weacure.com.
• Do not bind weacure.com until homepage, Pricing, Early Access, region pages, 404, 503, robots, sitemap, manifest, favicon, headers, no tracking, no checkout, and no form checks pass.
• Confirm domain ownership, DNS records, TLS, redirects, canonical URLs, robots, and sitemap.
• Review Platform Account Readiness before connecting deployment or DNS accounts.
• Keep the GitHub repository private and use least-privilege deploy access.
• Run the full verification suite and static smoke tests before switching public traffic.
• Review Operations Readiness before public traffic or maintenance changes.
• Confirm security headers are copied into the production build output.
• Do not record platform tokens, verification values, checkout URLs, provider secrets, or account internals.

Before buying a server

• Do not buy a custom server only for the static prototype.
• Use a server only when backend storage, member access, or provider webhooks require it.
• Prefer managed edge functions or hosted providers before maintaining a public origin.
• Review Cost Readiness before adding fixed hosting cost.
• Document DDoS, firewall, backup, logging, patching, and secret handling before any origin launch.

Related pages

Review Launch Readiness, Browser Readiness, Platform Account Readiness, Operations Readiness, Cost Readiness, Provider Readiness, Payment Readiness, Privacy Boundary, and Contact before changing hosting or DNS.