RWX November 2025 Recap: container image builds, git patching runs, OTEL, and more


At RWX, we use our own product to rapidly prototype, develop, and ship features all the time. Here's what we've built recently...
A radical new way to build container images
We built a faster way to build container images that skips the most frustrating parts of using Dockerfiles and BuildKit and runs natively on RWX. In fact, every step in your RWX build can already be pulled as a container image today.
Check out our how we did it, watch a short demo, or try it yourself by running:
rwx image build <definitions file> --target <task key>
For more information, check out our container image building documentation.
Decouple your development feedback from your version control
The RWX CLI has always given you the ability to develop your CI/CD definitions without first committing and pushing. We've extended the development workflow to capture local changes to any file in your git repo.
This unlocks novel ways to develop and debug hand-in-hand with your CI/CD - we describe some of them in our recent blog post!
Instrument your CI/CD with OpenTelemetry
You can now export RWX run data through OpenTelemetry to Honeycomb, enabling richer insight into the performance of your CI/CD workflows. The implementation is built on standard OTEL, making it straightforward to add support for other backends.
And so much more...
Or book time directly with one of our cofounders to see a demo!
Never miss an update.
Get the latest releases and news about RWX and our ecosystem with our newsletter.
Related posts

May 18, 2026
RWX now supports Codeberg and Forgejo
RWX now supports Codeberg and self-hosted Forgejo repositories, giving teams a reliable CI/CD path outside GitHub.

May 13, 2026
Why the TanStack supply chain attack can't happen on RWX
The TanStack npm compromise hinged on GitHub Actions cache poisoning. RWX's content-based caching and branch-locked vaults make that attack structurally impossible.