The use case: how Webflow deploys Statsig
Webflow uses Statsig as a single platform for feature flags, experiments, dynamic configs, and session replay, replacing three homegrown systems. Every new feature ships behind a flag so launches are decoupled from deployments, with phased rollouts and fast rollback.
More reported results
Figures published in Statsig’s case study. They are not independently measured by usedby.
At Webflow’s scale, Statsig evaluates about 3.9 million gate checks per day.
Webflow manages about 90 configs to change runtime behavior without code changes.
The team is also working toward standardized rollout patterns with alerting and guardrails, and is addressing hygiene across roughly 150 active flags, including a program to clean up stale flags.
In the customer’s words
The biggest unlock was decoupling launches from deployments. Instead of queuing behind a release train, we push a button. If something looks off, we push another.Other AI tools used by Webflow
Other public relationships recorded on usedby.
Explore Webflow’s AI stack
Statsig users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
See all Statsig customers
Go straight to the source
Based on Statsig’s published case study. We check the public evidence; the results are reported by the vendor.
statsig.com- Last checked
- Nov 12, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 45 teamsChecked
Printed word for word on the page, near the name of Webflow.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Webflow.
- Webflow uses StatsigChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Today, 45 teams across Webflow’s R&D organization use Statsig. Engineers are the primary operators, but PMs, designers, and both customer and technical support teams are active as well, with numerous users in the Console.