This message was deleted.

We don't support this currently. You could build your own back-end service though. It could use one of our back-end SDKs, connect to your database to populate attributes, and expose an API endpoint to get a variation. We're planning to build a proxy server similar to this in the future.

@future-teacher-7046 could you explain more about this proxy server? Which use cases does this cover? Is it meant as reverse proxy to tunnel request to a frontend through a GB instance?

Initially it will serve 2 primary purposes. 1. Highly scalable cache/proxy for the GrowthBook API that can support millions of client SDK connections. 2. Option to shift feature flag evaluation to the proxy server so you don't expose all of your rule evaluation logic to client SDKs. Instead, you just get back the state of all the features for a specific user.

I see ... but does the 2nd point fit to your general API based approach? Or do you aim to move SDK logic to the API?

We want to support both. Evaluating feature flags within the SDK is ideal for back end applications and when you want full control over how things are implemented. Evaluating feature flags in an API call is great for client-side apps when you don't want to expose all of the rules to users or if you prefer a simple http request instead of an SDK.

thanks for the explanation.