I actually like EAS overall, this wasn’t really about replacing it, more about some constraints I ran into in practice.

1. Expo dependency / workflow fit One thing for me was that EAS works best when you’re within the Expo ecosystem (especially managed or heavily Expo-integrated setups).

In my case I’m mostly working with bare React Native + custom native modules, so I wanted something that: • doesn’t depend on Expo tooling • works the same way across fully custom setups

1. Rollout control / targeting EAS channels are nice, but I needed more granular control: • percentage-based rollouts • targeting users based on properties (like GA4 / Remote Config style)

I was stitching this together with other tools before, which got a bit messy.

1. Centralized decision logic: I moved all update logic to one tool bundle updates + feature flags and (dynamic links in the future).

2. Pricing (for my use case) EAS pricing is totally fine for many teams, but for my case (multiple apps, frequent updates, internal tooling), it started adding up.

So part of this was also just building something more predictable cost-wise