What problem does it solve? Controlling which features each tenant sees requires a consistent feature flag system, and wiring up GrowthBook across client components, server routes, and plan-based targeting is error-prone without a reference implementation. ## Core Features & Use Cases - Provider Setup: Configures GrowthBookProvider with tenant attributes (tenantId, plan) and streaming updates in a Next.js app. - Client and Server Evaluation: Uses useFeatureIsOn and useFeatureValue hooks in components, plus a server-side GrowthBook instance for API routes. - Plan-Based Targeting: Maps tenant plans (STARTER, GROWTH, ENTERPRISE) to feature availability, with a DB-backed fallback using tenant workflowConfigJson. - Use Case: Gate a new bulk-order-actions UI behind a flag, roll it out only to GROWTH-plan tenants, and read max-export-rows as a numeric flag value with a safe default. ## Quick Start Set up GrowthBook feature flags in the web app with tenant-level targeting and gate the bulk order actions feature behind a flag.