Fluxa

Designers want living, GPU-driven backgrounds on their Webflow sites, but doing it means hand-writing shader code, wiring it to the page and keeping it fast on every device.

Fluxa turns that into a panel: pick a preset or tune it, select a section in the Designer, apply. The shader is a native element on the published page.

The gallery has three shader families. Two are self-authored GLSL: a glass-liquid surface with halftone grain, and an evolving noise field. The third, a stable-fluids solver that follows the cursor, runs on WebGL2 and on WebGPU compute with automatic backend selection.

Performance is part of the design: rendering pauses when a shader is off-screen, and resolution adapts to a fixed pixel budget so a gradient that is smooth at 1080p does not stutter at native 4K.

The Designer Extension is React and Vite. The backend is Hono on Cloudflare Workers with Postgres, email and social sign-in, and Lemon Squeezy subscriptions with webhooks, all verified end to end.

Published sites load versioned, hosted, integrity-pinned runtimes registered through Webflow’s Custom Code API, so a release never silently changes a customer’s live page.

I also built Fluxa’s marketing website in Astro: a hero with a fluted-glass backdrop, a WebGL2 logo shader and a GSAP scroll morph, plus a blog and a public gallery of presets with live shader previews.

Marketplace review forced a hard look at how code reaches a customer’s site. I rebuilt the delivery path twice: from inline scripts, to a loader, to self-contained hosted scripts and native elements. Constraints like that make the architecture better.

• TypeScript
• GLSL
• WebGL2
• WebGPU
• Three.js
• React
• Vite
• Hono
• Cloudflare Workers
• Postgres
• Lemon Squeezy
• Rive
• Astro
• GSAP