Metadata
ReadIdentify the repository and installation. GitHub grants this automatically.
TRUST & DATA
Access is explicit. Boundaries are part of the product.
Orylo reviews selected GitHub repositories with DeepSeek, through OpenRouter. This page explains what crosses each boundary, what becomes durable product knowledge, and how a workspace can stop access or leave completely.
GITHUB ACCESS
You choose the repositories. Orylo requests only review access.
GitHub sign-in identifies the person using Orylo. Installing the GitHub App is a separate step that grants access only to the repositories selected in GitHub.
MODEL ACCESS
Reviews run on DeepSeek, through OpenRouter. No Orylo fee.
Repository code, the pull-request diff and discussion, your instructions and memory, and Orylo's review prompt are sent to OpenRouter, which runs them on DeepSeek, from a container that can reach nothing else.
During the beta Orylo's own OpenRouter key pays for reviews, and Orylo charges no fee. A workspace that saves its own OpenRouter key is billed by OpenRouter instead. One fixed guard stops a single job that runs away.
A saved key is encrypted, scoped to one workspace, never displayed after entry, and kept out of jobs, logs, prompts, repositories, session archives, and review results.
SECURITY CHECKS
Known vulnerabilities, committed secrets, risky code.
Before the review, a workspace can have each pull request checked for dependencies with known vulnerabilities, committed secrets, and risky patterns in the code, workflows and infrastructure it changes. The reviewer weighs each result; a committed secret or a known-malicious package always blocks.
In its own container with no network at all and no credentials, reading the checkout without being able to change it. Only what the pull request changed is considered.
Where a finding is and which check found it. A secret is never stored or shown, only the file and line where it was committed.
The vulnerability data is refreshed every few hours from Orylo's own copy, and each review says how old it was.
DATA LIFECYCLE
Durable where it improves reviews. Excluded where it does not.
Orylo retains review history and bounded repository knowledge while a workspace is active. Execution checkouts are temporary and are cleaned after the review.
What Orylo stores
- GitHub installation and selected-repository metadata
- Pull-request delivery, review, finding, and resolution history
- The repository introduction and lenses from its first read, your instructions, and the memory learned from merged pull requests
- Encrypted provider credentials and resumable review-session artifacts
- Each review's room: the agents' conversation, which quotes the pull request's code, kept with the review, readable only by members of the workspace, and deleted with the review or the workspace
What logs and metrics must not contain
- Customer source code or unrestricted diffs
- Raw prompts or unrestricted model responses
- GitHub, model-provider, or connector credentials
- Review-session capabilities or secret-bearing request data
CUSTOMER CONTROL
Pause, revoke, rotate, or delete.
- Pause reviewsStop admitting new review work for a repository.
- Change GitHub accessAdd or remove repositories in the GitHub App installation.
- Rotate or remove the model keyReplace a key safely or block new provider reservations.
- Delete the workspaceRevoke connected access immediately, then complete a durable, retry-safe purge of repositories, reviews, memory, credentials, webhook data, and encrypted session artifacts.
CURRENT RELEASE SCOPE
Review first. Observation later.
Orylo can save post-merge observation guidance with a review. The current release does not claim to monitor production automatically, and production evidence integrations remain optional and inactive until explicitly connected and approved.