Webflow rebuilds its entitlements/billing infrastructure on Stigg
Webflow's engineering blog discloses that its plan-entitlement engine now runs on third-party platform Stigg, wrapped in an internal service layer built explicitly to allow swapping vendors later — turning plan/entitlement changes from a months-long engineering effort into a largely PM-editable one.
Webflow’s own eng blog (“From months to minutes: How we rebuilt Webflow’s billing infrastructure,” last updated 2025-10-24) discloses that its plan-entitlement engine runs on Stigg, a third-party entitlements platform, accessed only through an internal service layer built with the Strategy Design Pattern — explicitly designed so Webflow “could swap out third-party providers in the future without requiring notable changes across our codebase.” The team also replaced inconsistent per-feature usage tracking with centralized, cached entitlement checks. Net effect, per the post: pricing/packaging changes that “once took months of engineering effort” are now largely non-engineering changes for product managers.