Thirty-one providers can attach evidence to the pull requests Coroid opens. For what evidence is and why it belongs 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 need the least setup, because the environment already exists on the git surface Coroid is reading.
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 and monitoring
| Provider | Produces |
|---|---|
| Cypress Cloud | End-to-end, performance |
| Checkly | End-to-end, performance |
| Maestro | End-to-end, performance |
| BrowserStack | End-to-end, performance |
Custom
A custom evidence webhook covers anything not listed. If a tool can post a result, it can contribute evidence.
How evidence is ingested
Providers differ in how Coroid picks up their output:
- Git surface — read from the commit or pull request status your provider already writes. Least configuration.
- CI output — read from your pipeline's output.
- Direct API — Coroid calls the provider directly, which gives richer detail and needs credentials.
- Direct deploy — Coroid starts the deployment itself, from the task's branch in Coroid, so no push is needed.
Start with the git surface where a provider supports it. It usually works with no extra credentials because the integration you already have is writing the status.
Direct deploy and the task preview
Three static-hosting providers support direct deploy:
| Provider | How it builds | Where it shows |
|---|---|---|
| Vercel | Coroid uploads the branch; Vercel builds it | The task's Preview in the review |
| Netlify | Coroid builds the branch, then uploads the output | Review evidence |
| Cloudflare Pages | Coroid builds the branch, then uploads the output | Review evidence |
With Vercel connected for direct deploy, the task preview is built by Vercel instead of in a Coroid sandbox. Stopping that preview deletes the Vercel deployment. Repositories in local-only mode are never uploaded to a provider.
Without direct deploy, Coroid does not create provider previews. If your hosting provider's Git app already builds every pushed branch, Coroid reads that deployment from the pull request as review evidence.
Choosing
Connect what you already run. Review evidence is about surfacing existing verification next to the code, not adopting new tools — and each additional artifact competes for reviewer attention. See Review evidence.