outrider v1.7Live on the GitHub Marketplace →
// security

Security that fits how you already work

Remyx provisions server-side through a scoped GitHub App. Access is per repo and revocable, your keys stay in your own repo secrets, and a human gates every merge.

// 01 where_things_run

The execution boundary

Two planes, one clean line between them. The Remyx engine handles selection; your infrastructure handles everything that touches code.

RUNS ON THE REMYX ENGINE
  • candidate pool + embedding pre-filter
  • ranking against your interest and merge history
  • high-level repo analysis for recommendations
  • run telemetry and the decision record
RUNS IN YOUR GITHUB ACTIONS
  • the repo clone and call-site checks
  • the coding agent session, on your provider key
  • validators, lint, and the focused test pass
  • the commit and push, as remyx-ai[bot]

Model calls go straight from your runner to your provider. Changes reach your repo only as draft PRs from remyx-ai[bot], and a human gates every merge.

// 02 access

Scoped access you control

per_repo_access

Remyx connects through a scoped GitHub App. You grant access one repository at a time, and you can revoke it at any time.

provider_keys

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.

// 03 human_in_the_loop

A human gates every merge

observe_only_default

Remyx starts in review mode. It opens draft pull requests and comments, and earns more autonomy only on your policy and your results.

nothing_auto_merges

Every change lands as a reviewable pull request with its reasoning and gate checks attached. A person decides what merges.

// 04 what_we_keep

Retention, stated plainly

Your source code is never retained. What the engine keeps is the high-level record that makes recommendations sharper for your org.

datawhy it's neededwhere it's processedretained?
repository sourcefit checks, implementation, testsyour Actions runnerno
provider keysmodel invocationyour Actions secrets, direct to providerno
run telemetryrun status, outcomes, and costRemyx enginehigh level only
repo analysisrecommendation ranking · merge history categorized into evolution cyclesRemyx enginehigh level only
recommendationsthe per-org record that compoundsRemyx engineyes · exportable
// 05 agent_guardrails

What the 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.

path_allowlist

Python and markdown only by default, with at most three new files per run. Path violations terminate the run before anything is pushed.

always_blocked

CI configuration, Dockerfiles, shell scripts, and dependency manifests are never editable, in any configuration.

integration_validator

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.

Read the guardrails in the source →

// 06 enterprise

Controls for your environment

scoped per-repo accesskeys in your own repo secretsreview mode by defaulthuman gates every mergeSSO & audit logsVPC or self-hosted eval plane · by agreement

For specific compliance requirements or a self-hosted deployment, we are happy to walk through the details.

Talk to us about security →

Questions about security?

Tell us about your environment and compliance needs, and we will walk through how Remyx fits.

Book a callSee the platform