Groovy's still just a dynamically-typed language primarily used for scripting. It has statically typed extensions but they're not used very much. Groovy's used for scripty stuff like the 20-liners you find in a Gradle build script, but you don't find Groovy in Gradle's own codebase, only Java. Despite the heavy promotion since Groovy 2.0, developers aren't using statically-typed Groovy, but dynamically-typed Groovy is doing fine in Grails, Gradle build scripts, Java class manipulation, etc, everything except building systems. I wouldn't even be surprized if the newer additions to Groovy's own codebase like the Android stuff are written in Java rather than Groovy, despite statically-typed Groovy and Groovy for Android having the same author. That would be the ultimate vote of no confidence in Groovy's statically-typed extensions.

I would say yes it fits perfectly, especially if you extend it with java classes for performance critical stuff.