Skip to content

Business Perspective: Edge Value, Cost Posture, and Risk

Business Value Delivered by Cloudflare Edge

  • Zero-Trust Boundary: Implements Cloudflare Access as Layer 1 defense for internal documentation and admin tools, drastically reducing public attack surface before traffic ever reaches application code (Layer 2).
  • Secure Network Access: Cloudflare Tunnels allow standby replicas to receive traffic securely without opening exposed inbound firewall ports.
  • Domain Strategy: Cost-effective domain registration at Porkbun combined with Cloudflare's edge capabilities.

Cost Posture

  • DNS routing and Access perimeter protection leverage Cloudflare edge services (TODO(verify) plan tier and monthly cost).
  • Domain registrations remain at Porkbun for registrar cost efficiency (TODO(verify) annual domain renewal costs).

Key Operational Risks & Mitigations

1. Legacy Systems Outage Risk

  • Risk: If any of the 11 legacy A records are accidentally proxied (orange-clouded) in Cloudflare, legacy services will break.
  • Mitigation: Maintain strict grey-cloud DNS configuration and change management controls (TODO(verify) 11 A record list).

2. Access API Configuration Risk

  • Risk: Attempting PATCH calls on Access applications fails with HTTP 10405, risking broken automation scripts. Pinning allowed_idps inadvertently disables OTP login for team members.
  • Mitigation: Enforce full-payload PUT calls for all Access API updates and validate IdP settings to preserve OTP login paths.

3. Failover Proof Risk (WING-225)

  • Risk: Board standby replicas rely on 3 cloudflared connectors on a single tunnel. Failover verification is currently blocked due to Access HTTP 302 redirects.
  • Mitigation: Complete verification testing around the 302 redirect behavior to confirm failover readiness.

4. Front-End Security Interplay Risk

  • Risk: Strict Content Security Policies (CSP) can cause silent failures in UI styling (Angular critical CSS) or admin form interaction (HTMX).
  • Mitigation: Use inlineCritical: false build settings and explicit opt-out of hx-boost on admin forms to preserve functional stability under strict CSP.