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...
We'd love to show you all the cool stuff we've been building. If you're at AWS re:Invent, stop by Booth 1958 to say hi!
Or book time directly with one of our cofounders to see a demo!
Related posts
Read more on updates and advice from the RWX engineering team

We deleted our Dockerfiles: a better, faster way to build container images
Two weeks ago, we deleted the Dockerfile for our application, and we deleted the step in our CI pipelines that previously ran docker build.


