Integrating ABP Features with OpenFeature (seeking feedback)

[ahmadalmunajjed]

🚀 ABP Features + OpenFeature Integration

Hi ABP team and community,

I’m exploring integrating ABP Features with external feature flag systems (PostHog, Firebase, etc.) using OpenFeature as a standard abstraction layer.

The goal is to:

• keep ABP Features as the main abstraction for the app
• use OpenFeature-compatible providers for rollout, targeting, and experimentation

---

💡 Possible approaches

• Implement a custom FeatureValueProvider backed by an OpenFeature client
• Use a hybrid model (ABP feature + OpenFeature flag)
• Optional sync (OpenFeature → ABP via IFeatureManager)

---

❓ Questions

• Has anyone tried integrating OpenFeature with ABP Features?
• What would be the best approach within ABP’s architecture?
• Would the ABP team be open to contributions in this area (e.g., an OpenFeature provider/module)?

---

Thanks 🙏

[ahmadalmunajjed]

I’m personally leaning toward approach 3 (sync: external → ABP).

It keeps ABP Features as the single runtime source of truth, so existing code using IFeatureChecker doesn’t need to change. At the same time, it allows external systems (via OpenFeature providers like PostHog) to control rollout and targeting.

From my perspective, this approach gives a good balance:

• no runtime dependency on external services
• no changes to business logic
• still enables gradual rollout and experimentation
• fits well with ABP’s multi-tenant feature model

One concern I have with the sync approach is choosing the right sync interval.

Curious to hear if others have tried this in production or see any downsides with sync-based approaches.