Folium Systems

AI systems for real operations

Launch control room

Public launch is a controlled gate, 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 proof, security headers, and production AI controls.

Cloudflare launch

Authenticate Wrangler, confirm zone access, deploy, attach the demo domain, 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 proof.

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, eval gates, logging, abuse controls, and rollback.

Current truth

The public site is build-ready. Live operation still needs the external gates.

Static build and browser verification are complete.

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 evidence.

Folium treats launch as a controlled operating step: proof, access, security, legal boundaries, device coverage, and rollback before promotion.

Folium operating standard

Proof should move like machinery, but feel human to operate.

Every Folium path points back to the same discipline: protect the business, make the work visible, give people control, and move only when the evidence is strong enough to carry the next decision.

  1. 01 Understand

    Translate pressure into one workflow the team can explain.

  2. 02 Prove

    Make the future visible before private data or dependency.

  3. 03 Control

    Define owners, permissions, runtime, evidence, and rollback.

  4. 04 Operate

    Improve the system after launch instead of leaving a fragile demo.