I see - GrowthBook is made to be super flexible. What it needs to start serving features and experiments to users are the JSON feature payload and at least one attribute. The payload can come from a network request to GrowthBook or our Proxy, but can also be served via any other methods- from your middleware, from a Reddis instance, and also from a static object baked into the code or baked as part of a deploy step.