Thirty-one providers can attach evidence to the pull requests opened by Coroid. To find out what evidence is and why it should appear on the pull request, see Review evidence.
Configure providers under the project's integration settings.
Git-native
| Provider | Produces |
|---|---|
| GitHub Actions environments | Web preview |
| GitLab Review Apps | Web preview |
These require minimal setup, as the environment already exists on the git surface that Coroid reads from.
Static hosting
| Provider | Produces |
|---|---|
| Vercel | Web preview |
| Netlify | Web preview |
| Cloudflare Pages | Web preview |
| AWS Amplify | Web preview |
Full-stack previews
| Provider | Produces |
|---|---|
| Render | Web preview |
| Railway | Web preview |
| Heroku Review Apps | Web preview |
| Fly.io | Web preview |
| Northflank | Web preview |
| Qovery | Web preview |
| Porter | Web preview |
Mobile distribution
| Provider | Produces |
|---|---|
| Expo EAS | Mobile build |
| TestFlight | Mobile build |
| Google Play internal testing | Mobile build |
Review and scanning
| Provider | Produces |
|---|---|
| CodeRabbit | AI review |
| Qodo / PR-Agent | AI review |
| Greptile | AI review |
| Cursor Bugbot | AI review |
| SonarQube Cloud | Security scan |
| Snyk | Security scan |
| Semgrep | Security scan |
Coverage and visual
| Provider | Produces |
|---|---|
| Codecov | Coverage |
| Chromatic | Visual review |
| Percy | Visual review |
End-to-end testing and monitoring
| Provider | Generates |
|---|---|
| Cypress Cloud | End-to-end and performance testing |
| Checkly | End-to-end and performance testing |
| Maestro | End-to-end and performance testing |
| BrowserStack | End-to-end and performance testing |
Custom
A custom evidence webhook Covers any tool not listed here. If a tool can post a result, it can supply evidence.
How evidence is ingested
Providers differ in how Coroid picks up their output:
- Git surface — reads from the commit or pull request status that your provider already writes. Requires minimal setup.
- CI output — reads from your pipeline's output.
- Direct API — Coroid calls the provider directly, which provides richer detail but requires credentials.
- Direct deploy — Coroid can trigger the preview itself.
Start with the Git surface where a provider supports it. It usually works without extra credentials since the integration you already use writes the status.
Choosing
Connect what you already run. Review evidence simply surfaces existing verification next to the code, rather than forcing you to adopt new tools — and every extra artefact competes for the reviewer's attention. See Review evidence.