sluglistComparison
sluglist vs Marker.io
Both put a feedback button on a website and capture annotated screenshots with technical context. The difference is the shape of the product: Marker.io is a hosted service with a triage workflow and native project-management integrations; sluglist is an open-source widget that produces files and hands them to storage you own.
What Marker.io is
Marker.io is a commercial, hosted website-feedback service: reporters annotate a screenshot in the browser, and reports flow into a web dashboard and two-way integrations with trackers such as Jira, Trello, Asana, GitHub or ClickUp. It targets agencies and product teams that want feedback triaged inside their existing PM tool, and is priced as a subscription per team.
Written in good faith from public information, August 2026. Marker.io is a trademark of its owner and is not affiliated with sluglist — check their site for current features and pricing.
Side by side
| sluglist | Marker.io | |
|---|---|---|
| License & hosting | MIT open source. No hosted service, no accounts — artifacts go to storage you own via connectors. | Proprietary SaaS — reports and screenshots are stored on Marker.io's servers and viewed in their dashboard. |
| Pricing | Free. Your only cost is your own storage/endpoint. | Subscription, per team/seats, with a free trial. |
| Tracker integrations | Via your connector: parse the documented artifact format and create issues anywhere (~50 lines for a thin endpoint). | Native two-way integrations (Jira, Trello, Asana, GitHub, ClickUp and more) with status sync — its core strength. |
| Coding agents | First-class: artifacts are markdown/YAML files an agent reads; four bundled Claude Code skills generate the checklist, walk it in a browser, fix what failed and re-test. | Reports live in the hosted dashboard/tracker; not designed as local files for an agent loop. |
| Autonomous QA loop | A QA agent records evidence-backed verdicts (no fail without a screenshot, no pass without performing the check); npx sluglist status reads the artifacts and says whether another fix→re-test round is worth running, so the loop ends on green — or stops honestly on a stall. | Not offered: a human triages the report and a human fixes it. There is no machine-readable verdict for a fix pass to answer. |
| Triage workflow | None by design — one-way capture with a stable artifact format you pipe into your own tracker. | Built-in: statuses, assignments, comment threads with reporters, and status sync back from the tracker. |
| Data flow & privacy | Zero phone-home (test-enforced). Input masking, PII text scrubbing, screenshot consent under the production preset. | Data is processed and stored by the service; capabilities depend on plan and their policies. |
| Acceptance checklists | Built in: pre-seed a checklist, get a pass/fail/unchecked coverage map in session.yaml — or generate the list from a branch diff. | Not the product's model; feedback is free-form reports. |
Pick Marker.io when…
- You want feedback triaged inside Jira/Asana/ClickUp with two-way status sync, out of the box.
- You need reporter-facing replies and status notifications handled for you.
- You'd rather pay a subscription than run a ~50-line endpoint.
Pick sluglist when…
- You want an open-source (MIT) widget with no per-seat pricing and no vendor account.
- Screenshots and reports must stay on infrastructure you own.
- You want the QA loop itself: an agent tests, fixes and re-tests until green, and sluglist status decides when to stop.
- You want structured acceptance checklists with a coverage map, not just free-form reports.
The part a hosted dashboard has no answer for
Every tool in this category ends at a good report. sluglist keeps going: a QA agent walks an acceptance checklist in a real browser and records verdicts with evidence — no fail without a screenshot, no pass without performing the check — a fix agent answers them in fixes.yaml, and npx sluglist status reads the artifacts to decide whether another round is worth running. The loop ends on green, or stops and says which item has failed twice and needs a human.
Frequently asked questions
Is sluglist a drop-in replacement for Marker.io?
For capture, yes: annotated screenshots, console errors, environment metadata and a feedback button. It deliberately does not replace Marker.io's hosted dashboard, statuses and two-way tracker sync — you pipe artifacts into your own tracker instead.
Can sluglist send reports to Jira or GitHub like Marker.io does?
Yes, through a connector you write against the documented artifact format — typically a thin endpoint that creates the issue and attaches the screenshot. It is a small amount of code you own, rather than a built-in toggle.
Which is better for client feedback on agency projects?
If the agency lives in a PM tool and wants zero code, Marker.io's integrations are the shorter path. If you want the client walking a release checklist on staging with a coverage map, and reports stored on your side, sluglist's checklist mode is built for exactly that.