FlunesNot another dashboard
A Marker.io alternative for your own team's feedback
Marker.io is a visual-feedback widget you install on a website so external reviewers can mark it up. Flunes is for the other case: feedback from your own PMs, QA, and support about any product surface (a web app, a mobile build, a staging site, a live demo), described in a simple form with an optional screenshot and turned into a clean GitHub issue, with nothing for them to install.
Choose Marker.io when: All feedback happens on a web page you control. You want pinned visual annotations and technical metadata (browser, OS, console). Visual screenshot markup is central to your review flow.
Flunes vs Marker.io
- Yes, built in
- Partial, via add-ons
- No, not its job
Partial means it is possible through integrations or paid add-ons, not the core model.
What you get by moving to Flunes
Your team's feedback isn't limited to one website you can add a script to.
You want zero install and zero account for the teammate reporting.
Plain-text reports (not visual annotation) are enough.
You'd rather not pay per internal seat.
Your team's feedback rarely lives on one site
Real bug reports from your own people show up far from a single instrumented web page. A tester hits a crash in a TestFlight build, a PM spots a glitch while reviewing a staging link, support describes something a teammate flagged over a call, a designer points out a layout bug they saw on their phone. A widget bolted to one production website never sees any of that. As a Marker.io alternative, Flunes accepts a plain-text report from wherever the problem actually happened, with an optional screenshot attached, and routes it into the correct repo as a clean GitHub issue your team can act on.
The cost of skipping the widget
Dropping the on-page widget means giving up the metadata it captures automatically: browser version, OS, viewport, console logs. That is a real trade, and for some teams it matters. The payoff is that your teammate installs nothing and creates no account. A PM, a tester, or a designer opens a private link, writes what went wrong, and submits. Nothing to embed in your codebase, no script tag, no per-person login to provision. If you need that environment metadata more than you need frictionless reporting from your team, wherever they are, Marker.io is the closer fit.
What Flunes will not do
Being honest keeps this simple. Flunes does not draw pinned annotations on top of a live page, and it does not capture console output or network logs. It is not a public roadmap or a voting board, and it does not replace triage inside GitHub. What it does is narrow on purpose: take a non-technical teammate's plain-language description and produce a structured, labeled GitHub issue. If pixel-level markup on a website is the heart of your review process, that is Marker.io's job, not this one.
FAQ
No. Flunes captures plain-text reports (with optional screenshots), not pinned visual annotations or console capture. If visual markup on a website is central, Marker.io is the better fit.