A long term home and governance of the project is #1 priority. And funding is a close #2. After that, getting the docs polished and sharing the amazing Grails productivity/efficiency story is key to expanding usage. I first used Grails in 2010/2011 and then had a long break with projects/companies on other frameworks and languages until 2020, when I began using it on several projects. During those 10 years, I would keep going back to check how Grails was doing and to kick the tires, since the frameworks/languages/platforms being used on my projects left so much to be desired in comparison to Grails (Ruby on Rails 4, Struts, JSF, Stripes, Laravel, WordPress & Magento). Ruby on Rails was easy to pickup after using Grails, but lacked the scalability and breadth of libraries, at least back on 2015. Laravel was concise with high developer productivity but lacked basic things like database connection pooling. Solid Java engineers were/are easier to find than solid php and ruby engineers, in my experience. Grails was closer to Goldilocks for what 95% of startups need, IMO. Over my 25 year career, I've founded, been an employee/exec or consulted for several dozen startups. IMO all of them could/should use Grails. Even the one doing millions of transactions for billions of USD could have started with Grails and maybe still used it at the peak. It is really rare to work at a startup that outgrows what Grails can handle. And for that lucky 5%, there are a lot of choices. Unfortunately the 95% have been conned into thinking they should start on the 5% solution, which they most likely will never need. Grails with GSP and a Bootstrap theme allows 1 developer to build the entire app, when needed. And that is so much more efficient than starting with it split between backend and JS frontend and nearly building the app twice or three/four times with iOS/Android native apps. Grails has an awesome productivity/efficiency story.