Flamio Scout

Flamio Scout is in beta. Scout opens your site in a real browser and walks it like a visitor: it opens pages, clicks, scrolls and, when you allow it, fills forms and signs in. In minutes you get a report of the problems a visitor meets, with screenshots and a suggested fix for each — without recruiting testers or waiting for traffic.

What you get

• An audit of the whole site, or of one area or one task you name.
• A report on the run page: an overall score and risk, a short list of what to fix first, findings with screenshots, technical errors for developers, and notes on how the design reads.
• A map of how Scout explored the site, with the problems found on each page.
• A recording of what Scout did in the browser.
• Checks of your board tasks from Jira, GitHub or Trello, with the verdict posted on each task.
• A check of every new release of your site, compared with your last audit.
• Ways to act on findings: confirm them and send them to your tracker, or share chosen findings on a public page.

How it works at a glance

1. You enter the site address, pick the screen size and set a research budget — the most the run may spend.
2. Scout walks the site in a real browser. The run page shows its progress live.
3. Scout checks what it found and writes the report on the same page.
4. You review the findings, send them to your tracker or share them, and run Scout again after a fix.

A run belongs to the project selected in the sidebar project switcher, and is billed to your organization's token balance.

Limitations

• Flamio does not run Scout on a timed schedule (nightly, weekly) — instead, turn on Check every new release automatically under Release checks, and Scout checks the site once for each new version real visitors reach. Any other audit starts when you click Launch Scout.
• Flamio does not audit a site on localhost, an internal network or behind a VPN — the launch is refused with "Target resolves to an internal/loopback/metadata host and cannot be audited." Instead, put the build on a publicly reachable staging address; if it needs a login, give Scout a test account on an Interactive run.
• Scout does not solve CAPTCHAs or get past bot protection — it treats one as the edge of the audit. The run shows Blocked by the site, says whose protection stopped it, and nothing is tested or charged. Instead, point the run at an environment without the wall, or allow Scout through on your side, and launch again.
• Scout does not open a site a browser would refuse — an invalid HTTPS certificate, a name that does not resolve, a server that refuses or never answers. The run shows Site unreachable with the reason, and nothing is tested or charged. Instead, fix the address or the certificate and launch again.
• Scout does not test native iOS or Android apps — it drives websites only. Instead, select Phone (or Both) under Screen to audit your site at phone size.
• Flamio does not delete Scout runs — older runs drop off Recent runs on their own.
• Flamio does not export a Scout report as a PDF — the report lives on its run page and everyone in your organization can read it. Instead, click Share to send chosen findings on a public page, or Export approved to create issues in GitHub, Trello or Jira.

Next steps