The canonical way to use Profiles, even with Kotlin is with your Maven XML or a web.xml You can set them up other ways, but it just ends up making a lot of sen

The canonical way to use Profiles, even with Kotlin is with your Maven XML or a web.xml You can set them up other ways, but it just ends up making a lot of sense to define them there. To be fair, Ktor is pretty similar with the "application.conf" if you use the built-in Profiles equivalent: https://ktor.io/docs/configurations.html#hocon-overview https://ktor.io/docs/configurations.html#hocon-overview I just prefer that if I'm using DI, the concept of environments be handled by DI. Scoping is what DI does best after all...