How IonWarp handles your code

How IonWarp accesses your code

IonWarp installs as a GitHub App on the repositories you choose — and only those. Access is scoped by GitHub's own permission model, visible in your organization's settings, and revocable at any time by uninstalling the app.

IonWarp reads your code; it never writes to your repository. The GitHub App holds Contents: read-only — pull-request comments, inline reviews and one-click suggested changes are the only things it can post.

Every webhook from GitHub is checked against GitHub's signature before IonWarp reads it. A webhook without a valid signature is rejected.

Where reviews run

Each review runs in a sandbox container that is separate from IonWarp's web app and from your own infrastructure. Your repository is checked out into a directory private to that run.

Containers are kept running between sessions, so isolation does not depend on a container being new. Every session — a review, a repository scan or a chat — gets its own environment, holding only that session's credentials, and its own directories for the checkout and the output. When the session ends, all of it is wiped before the container serves anyone else, so one customer's code, credentials or output never reaches another customer's session.

What we store

IonWarp stores what you see in the dashboard: findings, pull request details, scorecard results and run logs.

Review data is deleted 90 days after it was last updated. Every record we keep about a review — the run, its findings, scorecards, learned rules, screenshots, notes about the repository and support tickets — is marked with its delete date when it is written, and a nightly job deletes whatever is past it.

Deleting a project deletes its review data with it.

Enterprise

The Enterprise tier adds SSO/SAML, audit logs, GitHub Enterprise support, a custom security review of your setup, and an SLA — the same list published on our pricing page.