Ah, good question! We've spent some time at larger tech companies, and realized that when you have many distributed teams, you can actually run Reploy with smaller subsets of your stack, and treat external dependencies like you would for external providers.

For example, maybe your team contributes to a frontend/backend regularly; you'd just staticly point the Reploy environment to other service dependencies that don't change as often.

That being said, market-wise we're targeting <200 eng companies, but definitely a cool thing to think about.