Cursor and RWX bring first-class CI integration to Origin's marketplace

Every day, we hear from teams looking for alternatives to dated CI platforms. Increasingly, they're also looking for a more reliable place to host their source code.
Recently, Cursor Origin became the latest entrant into the git forge hosting market.
RWX is now an official marketplace integration of Cursor Origin. Teams using Origin can trigger CI runs and report results natively with RWX today. See our Getting Started guide.
A fundamentally different approach to CI
Code is moving faster than any infrastructure was built to handle. Origin was designed for this moment.
Like Origin, RWX is designed for this moment. Every task in an RWX workflow can run on an independent VM. Upon task completion, we snapshot the VM's filesystem and cache it. Subsequent tasks boot on a new VM using a combination of any upstream tasks' filesystem layers. This means:
- Tasks whose inputs would produce the same filesystem snapshot automatically cache hit and do not need to be re-run.
- Tasks that do not depend on each other automatically execute in parallel.
- Each task can run on a VM specifically tuned to its own needs: more CPU and memory for your build step, less for your git clone.
The same compute primitives that make RWX CI faster and cheaper than the alternatives unblock new kinds of agent and human interactions including:
- Syncing local changes into a CI run without round-tripping through a git push and pull
- Running a longer-lived CI task as an agent sandbox
- Debugging CI via SSH or retrying only a single part of a large CI workflow
- Generating an entire preview of your application without deploying
- Building container images quickly and without a Dockerfile
Other CI platforms have native integrations with Origin as well. But none can match the performance or capabilities of RWX because they all are designed around the same legacy technical architecture: an entire workflow runs on a single VM.
Unlock your next git forge migration with RWX
If your team is already using Origin, you can configure it to run with RWX today.
If you are still deciding whether a new git forge is in your future, moving your CI to RWX is an excellent stepping stone to unlock experimentation. When Bonusly wanted to migrate their git forge in 2025, they first migrated their CI to RWX. With CI already decoupled from source control, the remaining source code migration was easy.
RWX already natively integrates with Origin, GitHub, GitLab, Forgejo, and Codeberg. We'll continue to add new forges as they emerge and you can integrate your own via webhook.
We automatically apply $100 in credits to every new account so you can explore RWX without commitment. Get started here.
Related posts

August 4, 2026
RWX raises $12M as the engineering bottleneck moves from writing code to validating it
RWX has raised $12M in Series A financing led by HPVP to rebuild the software forge for agentic software engineering.

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.
