Security that fits how you already work
GitHub App access you control. Outrider runs in your Actions runner. Validate runs on Remyx compute. A person approves every merge.
The execution boundary
Outrider runs in your GitHub Actions runner. Validate runs evaluations on Remyx compute. Your team controls repository access and approves every merge.
Your GitHub Actions runner
Outrider and your coding agent run here. Agent logs stay in the runner.
Remyx service
Returns recommendations and short-lived bot tokens. Receives run telemetry.
Your model provider
Receives prompts and code context directly from the runner, using your key.
runner → Remyx recommendation requests and run telemetry · Remyx → runner ranked candidates and short-lived tokens
runner → provider prompts and code context, with your key · nothing routes through Remyx
Your repository
The pull request, the proposed test and your review of it.
Remyx evaluation service
Builds the environment and runs the comparison on Remyx compute.
Connected providers
Uses a connected provider when configured. A limited Remyx-funded model allowance can support a first run without one.
repository → Remyx PR code and the validation request · Remyx → repository proposed plan, PR comment, Check and executed notebook
Remyx → providers model requests, downloads and logging, as configured for the evaluation
What Remyx stores. Run configuration, metrics, artifacts, a log excerpt and cost, attached to the change each run measured.
Merge control. The Validate Check blocks a merge only when your team makes it required in branch protection. Remyx does not merge the change for you.
Scoped access you control
Remyx uses GitHub App permissions scoped to the repositories you select. You can revoke access from GitHub.
Your provider key lives in your repo's own Actions secrets, and model calls go straight from your runner to the provider. Bring your own keys and pay providers directly.
Validate uses your selected connected model when one is configured, or the limited Remyx-funded model allowance for an eligible first run. Results and billed usage are recorded with the validation.
A person approves every merge
Outrider opens draft pull requests and comments. Validate proposes a test and waits for your review before it runs. Both earn more autonomy only on your policy and your results.
Every change lands as a reviewable pull request with its reasoning and checks attached. A person decides what merges.
Where records live
Outrider checks out code in your GitHub Actions runner. Validate runs on Remyx compute and commits evidence back to the repository. The retention details below need a final technical review before publication.
What the Outrider agent can and can't touch
The guardrails are enforced in the open-source action itself, so you can read them rather than trust a claim.
Python and markdown only by default, with at most three new files per run. Path violations terminate the run before anything is pushed.
CI configuration, Dockerfiles, shell scripts, and dependency manifests are never editable, in any configuration.
Every draft must wire into a real, reachable call site. Ideas without one become a discussion Issue instead of a PR, and most runs end in a skip.
Controls for your environment
For specific compliance requirements or evaluations that must run in your own environment, we are happy to walk through the details.
Questions about security?
Tell us about your environment and compliance needs, and we will walk through how Remyx fits.