Tell me what you are trying to build, fix, govern, prove, or launch, and I will point you to the public Folium page that fits. It uses public routes only, so do not send private data here.
Launch control room
Public launch is a controlled release, not a button press.
The site build is ready. The next stage is operational launch: Cloudflare authentication, domain attachment, lead capture, legal review, Safari/iOS validation, security headers, and production AI controls.
Cloudflare launch
Authenticate Wrangler, confirm zone access, deploy, attach the approved domain route, smoke test, and record rollback steps.
Lead capture
Choose the form backend or CRM, add spam protection, route notifications, define retention, and avoid collecting sensitive data too early.
Legal and investor review
Have counsel review privacy, terms, investor language, securities boundaries, claims, and any data collection before broad promotion.
Safari and iOS validation
Validate on actual Apple hardware or an approved WebKit/Safari lane before claiming full Apple-device coverage.
Security headers
Ship CSP, permissions policy, referrer policy, HSTS after HTTPS, and content-type protections through Cloudflare static assets.
AI production controls
Before live AI, complete threat modeling, OWASP LLM risk review, NIST AI RMF mapping, evaluation reviews, logging, abuse controls, and rollback.
Current truth
The public site is build-ready. Live operation still needs the external reviews.
Static build and browser verification passed the current gate.
Cloudflare dry-run passes locally.
Live deploy waits on account authentication and zone access.
Public contact intake remains local until a secure backend is approved.
Live AI remains blocked until model/runtime, logging, and safety controls are approved.
Start here
Move from build-ready to launch-ready with records.
Folium treats launch as a controlled operating step: records, access, security, legal boundaries, device coverage, and rollback before promotion.
- 01 Scope
- 02 Build
- 03 Prove
- 04 Operate