# Composal vs Happo

Happo specializes in rendered-image comparisons and accessibility signals attached to UI captures.

## 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](https://composal.com/docs/verify)

## Happo

Visual regression and accessibility checks

Happo captures UI states from Storybook, Playwright, Cypress, or custom pages and compares them in supported desktop and mobile browsers. Its product materials also describe accessibility testing and pull-request review for visual changes. Teams can integrate it with existing UI fixtures and evaluate diffs before merging.

## What each tool does

| Workflow | Composal | Happo |
| --- | --- | --- |
| [Run browser journeys](https://composal.com/product/scenarios) | ✓ Yes: Run saved browser Scenarios and return recordings and reproducible Findings. | – With setup: Captures or compares rendered pages through a configured test or visual workflow; confirm the supported runner. |
| [Map application workflows](https://composal.com/product/discovery) | ✓ 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](https://composal.com/product/deep-scan) | ✓ 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](https://composal.com/product/scenarios) | ✓ 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](https://composal.com/product/cli) | ✓ Yes: Use the CLI to start and inspect verification runs and their Findings. | – Not confirmed: Check whether this product includes this workflow in your intended plan and setup. |
| Visual regression baselines | × No: Use a dedicated tool for this specialist workflow alongside Composal’s browser verification. | ✓ Yes: Happo captures UI states from Storybook, Playwright, Cypress, or custom pages and compares them in supported desktop and mobile browsers. Its product materials also describe accessibility testing and pull-request review for visual changes. Teams can integrate it with existing UI fixtures and evaluate diffs before merging. |

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

## Where each fits

Choose Happo when visual regressions across browser configurations and accessibility checks are important parts of your frontend workflow.

## Try this evaluation

Pick a page with a stable screenshot, one color-contrast requirement, and a submission action.

### 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?

## Related comparisons

- [Composal vs Lost Pixel](https://composal.com/compare/composal-vs-lost-pixel.md)
- [Composal vs Argos](https://composal.com/compare/composal-vs-argos.md)
- [Composal vs BackstopJS](https://composal.com/compare/composal-vs-backstopjs.md)

[All comparisons](https://composal.com/compare.md)