Use case

A QA team you can call on whenever you need it

You do not always need a QA department. You need one the week before a launch, after a risky change, or when something feels off. Composal is a team of browser agents that learns your product and is there on demand.

Read the docs
New scan
What should the testers investigate?
Test the new billing flow. You may add seats and change plans; leave other accounts alone.
A team of browsers starts at onceStart Deep Scan

Where the time goes today

Hiring QA is a big step

A small team ships constantly and has no one whose job is to try to break it.

Outsourced QA needs briefing every time

Someone new has to learn the product again for every engagement, and the knowledge leaves with them.

The need comes in bursts

You want a lot of testing at launch and very little the week after, and neither staffing nor tooling flexes like that.

1

Ask for what you need

Describe the area and what the testers may change. Start a scan from the dashboard, the CLI or your coding agent.

Before a launch
After a risky change
When something feels off
2

A whole team starts at once

Browsers work in parallel, each with its own charter, and keep investigating after the first bug.

3

The team remembers

What it learned about your product stays, so the next call starts informed, and things you already know about do not come back as bugs.

What this team remembers
The empty state is not a bugKnown
Invoice rounds to the nearest centKnown
Seat count lags a refreshOpen bug

Capacity on demand

Use it hard before a launch and lightly afterwards.

No briefing, no ramp-up

It learns the product from the app and from your docs.

Knowledge you keep

What it learns lives in your project, not in someone’s head.

See every use case