Mention of redis-sentinel, prometheus and power dns all make me think that your work is either more sys-admin-ey than Indigo is really intended for, or else (hopefully) if that's just part of your work, you might find you can create a far more productive development environment using Indigo but without those containers. Instead, create a test / staging Docker environment to work on those.
You're right, it really does have a limited selection of services right now. New services are high on my todo 🙂 (including Redis — poke around inside the app bundle for a surprise)
However, it's inevitable that Indigo will not be workable for everybody, but I have personally used Indigo in various forms for over two years developing apps destined for a pretty complex production Docker infrastructure, and originally thought I would inevitably end up still running Docker locally for a few extras that Indigo doesn't support. There are a few things I could still run in Docker without causing me any loss of productivity (your mocked services container might fall into this category?), so running Indigo AND Docker is a reasonable option for some, I think. However as it turned out I never really missed any of it, once I changed my perspective.
And it has changed a lot since using Indigo, and it's been just a real joy not dealing with that kind of stuff when your focus is on coding the app, and not on sys-admin. Indigo will not ever be a help when you need to work on your redis failover, or configuring your application monitoring. But my hope is that you might find a way to develop your app that (most of the time, at least) doesn't need to interact with those things. And that's where a sufficiently-powerful native solution made all the difference to my day-to-day.