The CI/CD platform built on good ideas and a new runtime
Get StartedTrusted by
The only CI/CD platform that caches everything
Other CI/CD platforms spend a significant amount of time running the exact same commands on the exact same code as has previous been executed. Any caching on those platforms requires manual configuration that is highly error prone from forgetting to include relevant files in the cache key.
RWX caches everything automatically, and it caches perfectly. Executions on RWX are sandboxed, ensuring that files not taken into consideration for the cache key are not present on disk at all.
1tasks:2# system-packages will only run once3- key: system-packages4run: ...56# even though test-suite will run 10 parallel processes7- key: test-suite8use: system-packages9parallel: 1010run: ...
The only serverless CI/CD platform
Other CI/CD platforms define jobs which correspond to VMs. Each VM starts from a blank slate, having to execute the same setup steps as other VMs. The only way to run work in parallel is to run another job on another VM.
With RWX, you define the tasks that you want to run, and RWX automatically distributes the work onto as many machines as possible. Each setup step only runs once, ever. You don't have to make a new job to get a task to run in parallel.
The only CI/CD platform that runs from a CLI
Other CI/CD platforms require a git push to test changes to a workflow. The feedback loop is slow, and pushing broken code, even to a branch, feels bad.
With RWX, you test changes to workflows using a CLI. You won't have to commit and push until you know your changes are working. You'll get feedback in seconds rather than minutes. The feedback loop with RWX is so much faster that our engineering team offers to do free implementations.
The only CI/CD platform with remote breakpoints
Other CI/CD platforms require guessing at fixes, which is especially difficult when running on remote infrastructure. It results in a painfully slow feedback loop.
With RWX, you can set a breakpoint and open a shell within seconds. Set a breakpoint inline, in a shell script, or even in your test code. As soon as the breakpoint is hit, you can connect to that exact point of execution. Plus, with RWX's caching capabilities, you'll likely skip straight to the task that you're debugging.
The only CI/CD platform that can retry failed tests
Other CI/CD platforms require retrying an entire job when a single test fails. If a test fails due to flakiness, this results is an engineer waiting several minutes for something that should only take a few seconds.
With RWX, you can retry only the tests that fail. And with serverless execution, the tests will start running right away — you won't need to wait for all of the setup steps to run before the tests start.
Pricing
Get started for free with a $50 credit. After that, it's only $0.00014 per second.
| Cloud Hosting | Enterprise |
|---|---|
Start with free credit of $50 $0.00014 per second
| Have the RWX engineering team build a proof-of-concept implementation for you during a free evaluation
|