OrosuSecure CI/CD delivery, without the SSH keys

Install orosu-server once on your target machine, then let CI push deployment jobs to it over an authenticated WebSocket connection — no SSH, no SFTP scripts, no exposed production servers.

Getting Started

GitHub Action

No SSH keys to manage

CI authenticates to orosu-server with a short-lived, per-client Ed25519-signed token instead of a shared SSH key spread across every pipeline and repository.

Predefined scripts, not arbitrary commands

orosu-server only ever runs scripts you've explicitly configured on the target machine — CI can trigger them and pass arguments and files, but can't run anything else.

One GitHub Action, no toolchain required

orosu-ci/orosu is a pure-JS action — no Rust toolchain or binary install in your CI job, just a step in your workflow.