RWX now supports Codeberg and Forgejo!
We've heard a common refrain from a lot of teams lately: they're thinking about leaving GitHub for a more reliable service, and they want the rest of their tooling to match the reliability they already get from RWX. Git is portable. Your CI/CD should be too.
#Why use RWX instead of Woodpecker CI or Forgejo Actions?
Woodpecker CI and Forgejo Actions are natural options if you want CI close to your forge. Woodpecker is the primary hosted CI option on Codeberg today, and Forgejo Actions is the Actions-style workflow system built into Forgejo.
For smaller projects, using these CI platforms makes sense. But they're also built around a model that can't quite keep up with the pace of software delivery today.
RWX rethinks CI/CD from first principles to tighten the loop between writing code and validating it. Between representing your workflow as a graph of independent tasks, utilizing automatic content-based caching to reduce duplicate work, and enabling the execution of workflows without having to commit and push code, RWX makes the feedback loop dramatically faster for both humans and agents.
For a small solo open source project, Woodpecker or Forgejo Actions may be enough. For a team of engineers, RWX gives you a build platform designed for performance, repeatability, secrets, observability, and rapid iteration across the whole team. And for teams who already use RWX and are evaluating a move away from GitHub, this makes migration easy. You don't have to change anything about your existing workflows to start experimenting with Forgejo.
#Open source projects on Codeberg
If you're building open source software on Codeberg, you can partner with us through the RWX open source program for free usage.
Email [email protected] to get free open source credits for your project.
#Get started
The Forgejo setup flow works for Codeberg and any other Forgejo instances.
Follow the Forgejo getting started guide to connect your repository and start running on RWX.
Related posts
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.
Unlock agent-native CI/CD with the RWX Skill
RWX has launched an official skill for working with the RWX CLI and run definition files.