Why Webflow chose Blaxel for AI Code Components.
Webflow moved its AI component build engine to Blaxel for reliability and native storage, after stability and timeout issues on its previous vendor. Generated React components now ship at customer scale without a separate state layer.
- [INDUSTRY]
- AI code and app builders
- [PRODUCTS]
- SandboxesSandbox local filesystemVolumes
[THE STORY]
How Webflow runs on Blaxel
The problem
Webflow's AI Code Components generate React components on demand. On the previous vendor, sandboxes timed out mid-build and lost state between steps, forcing the team to build and operate a separate state layer around the runtime.
What changed
Each component build now runs in a Blaxel sandbox with an in-memory filesystem and snapshots that persist until deleted. Builds resume in about 25 milliseconds with their state intact, so the extra state layer went away.
At scale
Generated components ship at customer scale on the same instant, isolated primitive every Blaxel account gets on day one.
[RESULTS]
What changed
- Reliability
Zero timeouts
Builds no longer die mid-step; suspended sandboxes resume where they stopped.
- Architecture
No state layer
Native storage replaced the separate state service the team operated before.
- Scale
Customer scale
AI Code Components run for every Webflow customer on Blaxel.
