Skip to content

Cloudflare

Purpose

CDN + edge compute + AI Gateway + static site hosting + Zero Trust access control. eco|monetize's chosen platform for hosting internal and public documentation sites with per-user authenticated access — without requiring VPN.

Products in use

Cloudflare Pages (active — docs platform)

Static site hosting with GitHub Actions CI/CD integration. Confirmed 2026-04-21 as the deployment target for the docs platform.

Site Domain Access model Status
Internal docs docs.ecomonetize.com Authenticated (Cloudflare Access) Planning
Public ERI docs help.ecomonetize.com Public (Phase 2) Future

Deploy method: GitHub Actions → wrangler pages deploy (not the legacy GitHub Pages adapter).

Prerequisite: ecomonetize.com and eco-signals.com are currently on GoDaddy nameservers. Both must migrate to Cloudflare nameservers before subdomain routing works. Rick's action item.

Playbook: [[mkdocs-cloudflare-pages-deploy]] (in progress)

Cloudflare Access / Zero Trust (active — docs auth)

Zero Trust access control for docs.ecomonetize.com. Allows granting per-user access to internal documentation without VPN — suitable for investors, contractors, and external reviewers.

Why over Tailscale static server: Cloudflare Access grants per-user access via email/OAuth without requiring the user to install a VPN client or get a Tailscale seat. Investor/contractor use cases drove this decision. Decision log: /Claude/missions/M-2026-0421-local-llm-extraction-assessment/knowledge-base.md

Adding a user: Cloudflare dashboard → Zero Trust → Access → Applications → docs.ecomonetize.com → Add policy rule (email or email domain).

Cloudflare AI Gateway (planned)

LLM routing with caching, observability, and rate limiting. Referenced in Jordan's historical memory. Likely candidate for wrapping LLM API calls with logging. Not yet fully configured as of 2026-04-21.

Cloudflare DNS / CDN (future)

After nameserver migration from GoDaddy, Cloudflare becomes the DNS authority for ecomonetize.com and eco-signals.com. CDN caching for public-facing content becomes available post-migration.

Current DNS state (2026-04-21):

ecomonetize.com  → GoDaddy nameservers (not yet on Cloudflare)
eco-signals.com  → GoDaddy nameservers (redirects to ecomonetize.com — Rick's action)

What runs on it (current)

  • Nothing in production yet — docs platform in build (2026-04-21)
  • AI Gateway: planned for LLM routing

Cost posture

  • Cloudflare Pages: free tier covers most static site needs; Pro plan adds custom Access policies
  • Cloudflare Access: Zero Trust free tier for up to 50 users; sufficient for current scale
  • AI Gateway: included in most Cloudflare plans

Cost tier to be confirmed once accounts are verified.

Credentials & access

  • Cloudflare dashboard credentials in 1Password
  • CLOUDFLARE_API_TOKEN — required for GitHub Actions deploy via wrangler pages deploy; set as GitHub Actions secret in the docs repo

Owner

code.platform (infrastructure ownership). documentation.engineering (Pages deploy and Access configuration for docs sites).

  • [[vercel]] — current platform for ecomonetize.com website (separate from docs)
  • [[ecomonetize-com]] — primary domain, blocked on nameserver migration
  • [[github]] — source repo + CI/CD trigger for Pages deploys
  • [[tailscale]] — alternative for VPN-based access; ruled out for docs (requires client install)
  • [[mkdocs-cloudflare-pages-deploy]] — playbook (in progress)