Why did Grails move under the Apache Software Foundation?

Grails has changed stewards more than once over its life — originally driven by SpringSource/VMware/Pivotal, later by Object Computing Inc. (OCI) — and moving to the ASF addresses the recurring concern any framework tied to a single commercial sponsor eventually faces: what happens to the project if that one company's priorities or funding change.

Apache Software Foundation governance runs on open, vendor-neutral processes (the Apache Way): decisions are made by an open community of committers rather than a single company's roadmap, code and trademark ownership sit with the foundation rather than any one sponsor, and the project's continuity doesn't depend on one company's commercial fortunes. Grails 8, whose first milestone shipped in May 2026, is described as the project's first full development cycle carried out entirely under this open governance model.

For users and enterprises evaluating whether to build on Grails long-term, this is a meaningful signal distinct from any single release's feature list: it's a structural change in who controls the project's direction and how durable that governance is expected to be, independent of any one company's future decisions.