It is a bug tracker, and clients do not file bugs
Marker.io turns a report into a ticket with console logs, network activity and full technical context, then syncs it into Jira or Linear. That is the right shape for a QA engineer and the wrong shape for a client who wants to say the logo should be bigger and then approve the page.
There is no client-facing approval state, no branded review portal on your own domain, and no sense of a version being signed off. The workflow ends at a ticket rather than at a decision.

