If you build Android apps or Spring Boot services, you have probably seen the headline: Gradle is now Develocity. If your first reaction was to check whether your build.gradle files are about to break, you can stop reading and go back to work. They are not.
The short version: the company that maintains Gradle renamed itself. The build tool did not. This article walks through what actually changed, what did not, and why the company says it needed a new name in a world where AI agents write much of the code.
Full disclosure up front: everything here comes from the rename announcements published by the company and the Gradle build tool team, plus the July 2026 Gradle newsletter. There is no insider information and no hands-on testing involved, because a corporate rename is not something you test. It is something you read carefully so you know whether it touches your daily work. In this case, it mostly does not.
What actually changed
On June 30, 2026, the company known as Gradle Technologies took the name of its commercial product and became Develocity. The company now lives at develocity.ai, and gradle.com redirects there.
Here is the part that matters for anyone worried about their projects: the legal entity is still Gradle, Inc. No ownership changed, no money changed hands, no new investors arrived. As the build tool team put it in their own post, a rename is about as uneventful as a corporate event gets. The only thing that moved was the operating name on the door.
This is also the second step of a two-step process. Back in 2023, the commercial product Gradle Enterprise was renamed to Develocity. The company name has now caught up with the product name.
What did not change
For the open source build tool, the list of unchanged things is longer than the list of changed ones:
- The name stays Gradle. The tool is now branded "Gradle by Develocity" in some places, but it is still called Gradle.
- The license stays Apache 2.0. No acquisition, no relicensing, no paid tier sneaking in.
- The home stays gradle.org. If you typed gradle.com looking for the build tool, that was the wrong address all along. The docs, releases, and downloads are where they always were.
- The team stays the same. The same people work on the build tool full time, on the same release cadence as before.
- Your projects are unaffected. Same coordinates, same plugins, same commands. Nothing to migrate.
One more change that is easy to miss but genuinely useful: the word "Gradle" now means exactly one thing again. For years it referred to both the open source build tool and the company behind it, which made every announcement about one sound like news about the other. That ambiguity is the main thing the rename fixes.
Why rename a company with a famous name
The company gave two reasons, and both are visible in what the platform actually does.
Reason one: the platform outgrew the tool. The commercial Develocity product started as build scans for Gradle. Today it captures, analyzes, and governs builds, tests, and artifact production across the major toolchains: Maven, npm, pip, Bazel, sbt, and Gradle, with Docker support generally available as of this month. When your product works across seven toolchains, naming the company after one of them undersells it. From the company's perspective, keeping the name Gradle made a universal platform sound like a single-tool vendor.
Reason two: AI agents changed who needs build data. This is the more interesting argument. Agents now write code at machine speed, but the output is still software, and it still has to be built, tested, and governed before it ships. That means build and test volume is going up, and the company argues that acceleration and toolchain efficiency matter more than ever.
The second part of the argument is about context. When an AI agent has to fix a failing build, it needs to know things no log file carries: which tests flake and why, what changed since the last green run, what the build cache did. Develocity instruments the whole toolchain and aggregates that data into a form agents can query, including through an MCP server and other integrations. The company calls this layer "context engineering": assembling the right information for a system to reason over, so it produces reliable results instead of confident guesses.
Their framing for this is blunt: your toolchain is production now. If agents commit code into a repository, the pipeline that builds and verifies that code is no longer background infrastructure. It is the thing standing between machine-generated changes and your users.
The bottleneck argument, in one number
The company's announcement leans on a finding from GitLab's 2026 AI Accountability Report: 85 percent of developers and technology buyers agreed that AI has shifted the bottleneck of software delivery from writing code to reviewing and validating it.
That number is the whole rename strategy in miniature. When humans wrote all the code, a build tool company could name itself after the build tool, because builds were the slower, riskier half of delivery. When agents write the code, the scarce resources become verification, traceability, and trust in what changed. Develocity is positioning itself as the platform for that layer, which is a bigger story than any single build system.
Whether the strategy works is a separate question. But the logic of the rename is coherent: name the company after the problem it solves, not the first tool it shipped.
What this means for you, depending on who you are
If you only use the open source Gradle build tool: nothing changes. Your builds, your CI configuration, and your plugins keep working exactly as before. The only visible difference might be "Gradle by Develocity" branding on the website.
If you run Gradle Enterprise or Develocity at work: the product, team, and contracts carry over unchanged. The company is explicit that a rename is theirs to manage, not yours. There is nothing to migrate on your side.
If you maintain Gradle plugins: watch for the new "Gradle by Develocity" branding in docs, but the APIs and publishing flows are unchanged. Existing plugins do not need a code change for this.
If you are evaluating AI coding agents for your team: the rename is a signal worth reading. The teams behind the most widely used build tools are betting that agent-generated code volume makes build and test observability a first-class concern. Whatever vendor you pick, the underlying point stands: when agents commit code into a repository, the pipeline that builds and verifies that code is no longer background infrastructure.
Sources
- Gradle Technologies is Now Develocity: AI Moved the Bottleneck in Software Delivery (company announcement, June 30, 2026)
- The Company Formerly Known as Gradle (the build tool side of the story)
- Gradle Build Tool Newsletter, July 2026
- Hans Dockter's LinkedIn post on the rename
Top comments (0)