Precoa AI · Infrastructure Note

Sharing HTML pages: which hosting option, when

Claude and other AI tools generate finished HTML pages — dashboards, one-pagers, decision docs. This compares the realistic ways to get those pages in front of people. Vendor-neutral by design: the standard shouldn't depend on any single AI platform's sharing features.

Updated July 2026 · Pricing checked against current published plans; verify before committing.

Start here: the decision in five rows

Most of the time the right answer falls out of two questions — who needs to see it, and does it need to live at a stable URL.

Any page shared inside Precoa — dashboards, one-pagers, decision docs→Cloudflare Pages + Access
One-off static doc that just needs to travel (email, Teams, drive)→Self-contained .html file or PDF
Real app with a backend, database, or scheduled jobs→Render
Public site with a git workflow and preview deploys per PR→Vercel or Netlify
Docs living next to code in a GitHub repo, fine being public→GitHub Pages

Side-by-side comparison

"Internal-only gating" means restricting viewers to Precoa logins — the deciding constraint for most internal content, and the row where platforms differ most.

Platform Cost to start Deploy effort Internal-only gating Custom domain Best for
Cloudflare Pages $0 · Access free ≤50 users Low — one CLI command or drag-and-drop Free tier via Cloudflare Access (Zero Trust) Yes, free Internal tools & gated pages at a stable URL
Vercel $0 hobby* · $20/seat Pro Low — CLI or git push Paywalled password = Pro; SSO = Enterprise Yes, free Public sites, Next.js apps, PR previews
Netlify $0 · $19/seat Pro Low — best drag-and-drop UI Paywalled password/SSO on paid tiers Yes, free Public static sites, forms, non-CLI users
GitHub Pages $0 (public repos) Medium — repo + Pages config None pages are always public Yes, free Public docs versioned with code
Render $0 static · ~$7/mo services Medium — git-connected services Roll your own in-app auth (as MSA tool does) Yes, free Apps with backends — already in use at Precoa
No host (file / PDF) $0 None — attach or drop in a drive Inherited from wherever it's stored n/a One-off static docs; anything printable

*Vercel's free Hobby tier prohibits commercial use — Precoa work starts at Pro. AI-platform sharing (e.g. claude.ai Artifacts) was considered and deliberately set aside: it works, but it ties internal distribution to one vendor's product decisions.

Strengths and weaknesses

Cloudflare Pages

Cheapest path to gated internal URLs

  • Free: unlimited sites, generous bandwidth
  • Access gates any site to @precoa.com — free ≤50 users
  • Fastest deploys tested (~3s upload-to-live)
  • Dashboard less polished than Vercel/Netlify
  • CLI login requests very broad account permissions
  • Cloudflare steers new work toward Workers; Pages gets features last

Vercel

Best developer experience, priciest gating

  • Smoothest git integration; preview URL per PR
  • First-class Next.js and frontend-framework support
  • Commercial use requires Pro — $20/seat/mo per deployer
  • SSO-gated viewing is Enterprise-only
  • All Pro members see all team projects

Netlify

Friendliest for non-technical deployers

  • Drag a folder onto the browser — no CLI needed
  • Built-in form handling for simple intake pages
  • Free tier allows commercial use
  • Access control paywalled, like Vercel
  • No standout advantage over Cloudflare for this use case

GitHub Pages

Free and versioned, but always public

  • Content versioned with the repo it documents
  • Zero cost for public projects
  • No access control at any price
  • Slower publish cycle (build via Actions)
  • More setup than any option here

Render

Already proven at Precoa (MSA tool)

  • Runs full apps — Python/Node backends, databases, crons
  • Existing org familiarity; one less new vendor
  • Heavier than needed for a static page
  • Access control is whatever the app implements itself
  • Free-tier services sleep when idle; paid ~$7/mo each

No host (file / PDF)

Zero infrastructure, maximum portability

  • Self-contained .html renders anywhere, even offline
  • Access control inherited from Teams/SharePoint/drive
  • Nothing to maintain, no vendor at all
  • No stable URL; versions fork as copies spread
  • SharePoint often downloads .html instead of rendering it

Recommendation for Precoa

  1. Make one org-owned Cloudflare account the default home for shared pages (registered to a shared address like ai@precoa.com, not a personal login). Pages hosting is free, deploys take seconds, and Cloudflare Access gates every site to @precoa.com logins at no cost up to 50 users.
  2. Use self-contained files or PDFs for one-off docs that don't need a living URL — inline everything and they travel fine through email, Teams, or a drive.
  3. Keep Render for real applications — anything with a backend, like the MSA tool. Don't migrate what's working.
  4. Skip Vercel and Netlify for now. Their strengths (git previews, framework builds) fit product teams shipping public sites — not the internal-page use case — and the access-control gap costs real money to close.

Whatever hosts the page, the file itself should follow the portability rules: fully self-contained (CSS/JS inlined), named index.html, HTTPS-only external links, viewport meta tag set.