Code review

Composal vs Gitea pull requests

Gitea provides the source review surface and merge controls. Composal checks user journeys in a running browser environment and returns recordings, Findings, and concrete reproduction steps.

See where each fits ↓

Two workflows, side by side

Composal

Composal sends AI browser agents to use your running web app and check the outcomes you care about. Define journeys as plain-English Scenarios, map existing flows with Discovery, or explore for bugs with Deep Scan. Runs keep recordings and reproduction steps so your team or coding agent can investigate a Finding.

Verify documentation →

Gitea pull requests

Self-hosted Git collaboration and code review

Gitea includes pull requests, reviewer assignment, comments, approvals, and protected branch rules. It is a self-hosted Git collaboration option.

What each tool does

“With setup” means you supply code or configuration. “Not confirmed” means support for this workflow needs checking with the vendor.

Composal and Gitea pull requests workflow capabilities
Workflow	Composal	Gitea pull requests
Run browser journeys	Yes Run saved browser Scenarios and return recordings and reproducible Findings.	No The documented product reviews or analyzes source changes; it does not execute browser journeys.
Map application workflows	Yes Discovery maps key application areas and user journeys.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Explore for unexpected issues	Yes Deep Scan explores the running application and reports reproducible issues.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Describe checks in plain English	Yes Author Scenarios around the intended user outcome, then review the steps and expected results.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Run or inspect from a terminal	Yes Use the CLI to start and inspect verification runs and their Findings.	With setup Connect its specialist checks to your development workflow using supported integrations.
Source code review and analysis	No Use a dedicated tool for this specialist workflow alongside Composal’s browser verification.	Yes Gitea includes pull requests, reviewer assignment, comments, approvals, and protected branch rules. It is a self-hosted Git collaboration option.

Where each fits

Choose Gitea when self-hosted Git hosting and review are the priority. Choose Composal for independent web QA on preview or release builds. They can be used together in a self-hosted development workflow.

Try this evaluation

Open a Gitea pull request that changes onboarding, then exercise its preview with Composal. Compare reviewer comments and branch protections with observed outcomes for new users and returning users.

Coverage: Which user outcomes must this release prove, and which specialist checks must stay in your existing stack?
Setup: Who prepares accounts, test data, permissions and access to the deployment being tested?
Evidence: Can the engineer reproduce a reported failure from the recording and steps, without asking the tester to investigate again?
Ownership: Who updates the checks when the product changes, and can the team review what a passing result actually proves?