Quarkus gRPC Zero
Make gRPC code generation portable: no native protoc, no surprises.
TL;DR
Quarkus gRPC Zero brings gRPC code generation into the JVM so you no longer need native 'protoc' binaries. Add the extension, build your project, and the generated stubs appear just like before.
The important outcome is consistent, portable builds across developer machines, CI, containers, and even unusual architectures.
Why this matters
If you have spent time wrestling with platform-specific protoc binaries, cross-compiled plugins, you know the cost: slow onboarding, fragile builds, extra Docker layers, and ongoing maintenance. Quarkus gRPC Zero removes that operational burden so teams can focus on APIs and features instead of trying to find the right combination of dependencies to compile proto files.
What Quarkus gRPC Zero does
Quarkus gRPC Zero runs the protoc compilation inside the JVM as a pure Quarkus codegen module.
From a developer point of view nothing changes: you keep writing .proto files, run your Quarkus build, and use the generated sources.
The difference is that builds are portable and predictable on any JVM host. It avoids having to download dozen of dependencies to handle every OS/architecture combination.
Benefits
-
Portable builds that behave the same on laptops, CI, containers, and edge devices.
-
Simpler CI and less downloads as you don’t need native executables.
-
Less maintenance for platform teams who no longer manage platform-specific toolchains.
-
A small, self-contained Java dependency that performs
protofile compilation.
Quick start
Add the extension to your project. Replace 'VERSION' with the release you choose.
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-grpc</artifactId>
<exclusions>
<exclusion>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-grpc-codegen</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>io.quarkiverse.grpc.zero</groupId>
<artifactId>quarkus-grpc-zero</artifactId>
<version>VERSION</version>
</dependency>If you are migrating from an existing Quarkus gRPC setup, you need to exclude the 'quarkus-grpc-codegen' artifact from your 'quarkus-grpc' dependency and add 'quarkus-grpc-zero' instead as a drop-in replacement. Build your project as usual and generated sources will appear during the build step.
Example workflow
-
Add the 'quarkus-grpc' dependency with exclusions for 'quarkus-grpc-codegen' and include 'quarkus-grpc-zero'.
-
Keep authoring '.proto' files as before.
-
Run the Quarkus build. Generated stubs will be produced on the JVM and compilation completes normally.
The developer ergonomics are unchanged, but there are no native tools invoked during the process.
Current status and roadmap
Quarkus gRPC Zero is currently experimental but ready for early adopters.
It passes integration tests and works in typical Quarkus builds. We are actively improving the project and welcome feedback, real-world testing, and bug reports to guide stabilization and future features.
Under the Hood
The extension embeds a version of libprotobuf, compiled to WebAssembly (with the CLI stripped out) and translated into pure Java bytecode thanks to Chicory.
The result is a self-contained JAR that provides the full protoc engine capabilities (including plugin support) and runs on any JVM, transparently and portably across platforms.
Try it and report any errors
Please try Quarkus gRPC Zero in your projects. We want real-world feedback and we especially want to hear about any errors, edge cases, or surprising behavior you encounter. We are happy to quickly to turn things around to fix outstanding bugs.
If you see an error, open a ticket at the project repository: quarkiverse/quarkus-grpc-zero issues
Your reports will shape the project and help us make code generation reliable for everyone.
