Faylee and Marker.io both turn a bug on a web page into a report with the console, network requests and browser details, and both connect to coding agents over MCP. They differ in what a report holds, which plan you need for it, and who you pay for.
You want screen recordings with your voice, not only screenshots. Faylee records a tab, window or screen with your microphone. Marker.io has no built-in screen recording.
You want the console, network requests and page replay on every plan, Free included. On Marker.io they start at the Team plan, $149 a month billed yearly.
You want to save a bug that already happened on any site you open, with instant replay in the extension, without adding a script to that site first.
Your coding agent should get the whole recording: the screen at any moment (get_moment), a step-by-step brief for working it (get_guide), and a way to ask the reporter for a new recording (create_recording_link).
You want to pay only for people who record, with SAML SSO, Zendesk and Intercom on Team rather than a custom plan.
Your reporters use Firefox. Marker.io’s extension runs there; Faylee’s runs in Chrome, Edge, Brave and Arc, and its recording links open in desktop Firefox.
You file issues in Bitbucket or monday.com. Faylee connects Linear, Jira, GitHub, GitLab, ClickUp, Trello, Asana, Notion and Azure DevOps.
You also want scheduled accessibility and broken-element scans of your site. Marker.io sells Website Monitoring as an add-on.
Side by side
What each one records, what your coding agent can read, and which plan you need for it.
Feature
FayleeTeam from $12 per member a month
Marker.ioStarter from $39 a month for 3 members
Capture
Where it records
Chrome extension (also Edge, Brave, Arc), recording links and a site widget
A widget on your site, or the browser extension for Chrome, Firefox and Edge
Screen recording with voice
A tab, window or screen, with your microphone
No built-in screen recording; screenshots with annotations
What just happened
Instant replay of the last few minutes, on any site you open
Session replay of the last 2.5 minutes, on Team and up, on sites where its widget runs
Console and network
On every plan, with request and response bodies for fetch/XHR
Team and up; Starter gets environment details
Steps to reproduce
Copy as a list or a Playwright test
Shown in session replay, on Team and up
Page (DOM) replay
Native, in the same timeline as the video
Session replay, on Team and up
Coding agents
MCP server
On every plan, with an agent guide (get_guide)
On every plan
What the agent reads
The screen at any moment, what was said, console, network with bodies, steps
Marker.io details checked on marker.io and its help center (pricing, MCP, session replay, network requests and browser extensions) in October 2026.
Where they really differ
Both capture the console, network and browser details. These are the parts that change how a bug gets fixed.
Video and the page, not only a screenshot
Faylee records the screen with your voice, and a native DOM replay of the page plays next to it on one timeline, with network bodies and WebSocket messages. Instant replay saves the last few minutes after a bug already happened, from the extension, on any site.
Video · DOM replay · instant replay
What your agent gets
Faylee hands your agent the whole recording over MCP or the CLI: the screen at any moment, what was said, the console, the network with bodies and the steps. get_guide gives it a step-by-step brief, create_recording_link asks the reporter for a new recording when it needs one, and it comments back on the recording when it’s done.
get_moment · get_guide · add_comment
Who you pay for
Only members who record are billed, from the first one. Viewers, and people who send you recordings through a link or the site widget, are free, and the console, network and page replay come on every plan.
Viewers and reporters free
Switching from Marker.io
Every new workspace can try Team for 14 days, no card needed.
The extension isn’t available for Firefox or Safari. It runs in Chrome, Edge, Brave and Arc. Recording links open in desktop Chrome, Edge, Firefox and Safari, as screen recordings.
No. The extension captures any page you open in Chrome, Edge, Brave or Arc, with the console, network and page replay. The site widget is an optional script tag for people who don’t have the extension.
Yes. Over the MCP server or the CLI it reads the console, network requests, steps and device of a recording, in Claude Code, Codex, Cursor, VS Code and Claude.ai.
Anyone in your workspace who records, sends recordings to other tools or uses the AI. Viewers, who watch recordings and comment on them, are free on every plan. So are people who send you a recording through a link or the site widget, and anyone who opens a shared link.