What it sells
Swarms of agents acting like users to find bugs before release
Business model breakdown
Buyer: who owns the budget?
UnverifiedEngineering lead or CTO at a software team shipping heavily with coding agents.
Trigger: what makes them buy now?
Too many PRs to test by hand: tests are green but the team is unsure whether to ship, and is either clicking through the product manually or not checking at all.
Workflow: what inputs become what output?
Give Composal the product URL and connect repo, specs and sources (GitHub, Sentry, PostHog, Notion, Granola); launch a swarm of agents that use the product like real users across flows and edge cases in parallel; review video, logs and reproduction steps for each failure; pass the repro steps back to the coding agent to fix.
Economics: what it saves and how it charges
Flat workspace subscription with a shared pool of browser-agent minutes plus overage and add-on concurrency blocks; pitch is less manual QA and fewer bugs reaching users.
Distribution: how it reaches customers
Self-serve signup ("Try Composal", account register) plus a contact/Calendly demo request for teams.
Funding history and coverage
| Round date | Stage | Amount | Investors | Source |
|---|---|---|---|---|
| — | Y Combinator Fall 2026 | — | Y Combinator | ycombinator.com |
Profiles summarize public reporting and company websites. Business-model notes are MaxBC's reading of that material, not confirmed facts; unknowns are left blank rather than guessed. Updated 2026-10-12.