# The CI/CD platform for high velocity teams | RWX

> Markdown mirror of DialtoneApp's public top-site detail page for `rwx.com`.

URL: https://dialtoneapp.com/top-sites/rwx.com/index.md
Canonical HTML: https://dialtoneapp.com/top-sites/rwx.com

## Summary

- Domain: `rwx.com`
- Website: https://rwx.com
- Description: ai readable | score 20 | purchase read only
- Label: ai_readable
- Payment surface: Not available
- Purchase boundary: read_only
- Control boundary: unknown
- Rank: 295814

## robots

~~~text
User-agent: *
Sitemap: https://www.rwx.com/sitemap-index.xml
~~~

## llms

~~~text
# RWX

> The CI/CD platform for high velocity teams.

RWX is a modern CI/CD platform built for the era of AI-assisted development. When agents help developers write code in minutes, validation becomes your bottleneck. RWX gives agents programmatic control, sub-second cached builds, and semantic outputs they can act on. No commits required — just iterate until CI passes, then push.

- Website: https://www.rwx.com
- Documentation: https://www.rwx.com/docs
- Pricing: https://www.rwx.com/pricing
- Status: https://status.rwx.com

## About

### CI/CD Platform

https://www.rwx.com/ci-cd

RWX replaces traditional CI systems that run jobs sequentially, repeat work across VMs, and require manual cache configuration.

**DAG-based execution:** Express dependencies, not pipelines. Tasks execute in optimal order with true parallelization across distributed infrastructure. Only rebuild what changed. Fine-grained retries on failure.

**Content-based caching:** Automatic caching that rebuilds only affected code. Each task is cached independently, so a cache hit is preserved even when other tasks have a cache miss.

**Right-sized compute:** Specify CPU and memory per task. Scale up to 64 cores instantly. Per-second billing with no over-provisioning.

**Developer experience:** SSH into remote breakpoints for debugging. Trigger runs from the CLI to test local changes without committing or pushing. Rich logs exportable via OpenTelemetry.

CI/CD pipelines are defined as YAML files, typically found in a project's `.rwx` directory. See: https://www.rwx.com/docs/guides/ci

### Container Image Builds

https://www.rwx.com/container-image-builds

RWX is a faster way to build container images. Define your build as a graph of tasks, and RWX produces OCI-compatible images without the limitations of Dockerfiles or BuildKit.

- Build steps execute on separate machines in parallel, then layers are combined into a single image
- Content-based caching that survives changes — no more fragile cache invalidation
- Debug builds by setting breakpoints and SSHing into tasks

## Documentation

Use the RWX CLI to interact with the platform.

- Documentation: https://www.rwx.com/docs/cli-reference
- Installation: https://www.rwx.com/docs/getting-started#installing-the-cli
- Source code: https://github.com/rwx-cloud/rwx

### Examples

Launch a run:

```
rwx run .rwx/{pipeline}.yml --wait
```

The `--wait` flag polls until the run completes or reaches its first failure, returning information about what failed.

### Troubleshooting failures

See the latest result status and failure information for the current branch:

```
rwx results
```

### Iterating without committing

Changes to RWX definitions and git-tracked code are automatically synced when you use `rwx run` (when the pipeline uses the `git/clone` package). You do not need to commit, push, or pull to iterate on code.

See: https://www.rwx.com/docs/packages/git/clone
~~~

## llms-full

Not found.