SiteLens Platform

Verify real workflows—not just individual pages.

SiteLens Platform is a developer-first browser QA stack for authenticated applications and multi-step user journeys: SiteLens Local runs real Chromium on your machine with saved auth profiles and shared browser sessions (free—no API key); SiteLens Cloud/API hosts runs, persistence, and CI workflows; SiteLens Studio visualizes templates, flows, and run inspection. SiteLens MCP is the IDE integration layer for Local—not a separate product headline.

Download for macOS SiteLens Local Local vs Cloud/API Cloud dashboard Contact us

SiteLens Platform — three focused surfaces on one QA engine (plus Theme for design intelligence).

SiteLens Local

Free local browser QA on your machine—localhost, staging, and private URLs.

SiteLens Cloud/API

Hosted browser QA, persisted runs, API-triggered execution, and CI workflows.

SiteLens Studio

Inspect runs, screenshots, templates, and structured findings—not the whole platform.

SiteLens Local

Free local execution

SiteLens Local is free local execution on your machine—not a limited SaaS tier. Chromium runs against localhost, staging, and private URLs you can reach from your workstation. No API key required; reuse Playwright-style auth state where supported. Prefer a native macOS app? Download SiteLens Desktop for macOS (version 0.1.0).

Real browser execution

Bundled Chromium with screenshots and step reports—cloud features are separate; local execution stays free.

Localhost & private URLs

QA apps before they are public: dev servers, VPN staging, and LAN hosts your browser can open.

MCP & editor workflows

Run from terminal, scripts, or SiteLens MCP in Cursor—same Local engine from your IDE.

IDE setup: SiteLens MCP (Local integration) · comparison: Local vs Cloud/API on QA.

SiteLens Local vs SiteLens Cloud/API

Two execution modes

Same browser QA semantics—different runtime. SiteLens Local is free on your machine; SiteLens Cloud/API is for hosted runs, persistence, and operational workflows.

SiteLens Local

Free local execution
  • Runs on your developer machine
  • localhost, staging, and private URLs
  • No API key required
  • Real bundled Chromium automation
  • Artifacts under your local artifact directory
  • Ideal for dev loops, pre-push checks, and IDE/MCP workflows
Local setup (MCP)

SiteLens Cloud/API

API key
  • Hosted Chromium against public reachable URLs
  • Monitoring, scheduled scans, and alerts (as you adopt them)
  • Persisted runs, screenshots, and team-visible history
  • REST API, dashboard, and QA Studio cloud executions
  • CI/CD and operational workflows
  • Workspace API keys tie usage to your account
Cloud dashboard

Scenario Runner chains reusable flows in a shared browser session via SiteLens Local and MCP—saved auth profiles, parameterized flows, and multi-step workflow verification for authenticated apps.

Page Intelligence & AI Agent Verification

Shipped

Two capabilities that extend SiteLens beyond smoke tests: structured page understanding for agents and IDE-native verification gates that run real browser flows before you ship.

Page Intelligence

Render a page once and get ranked primaryActions, secondaryActions, navigationActions, and inferred workflowStages—confidence-scored summaries agents can plan against without scraping raw DOM.

REST POST /analyze/page · pairs with Theme for design + intent · feeds agent verification planning.

Page Intelligence details

AI Agent Verification

Keep Cursor (and other MCP hosts) honest: run repo-local flows via sitelens_run_local_flow, compare screenshots, and use prompt-library gates so agents verify in Chromium—not by claiming “looks good.”

Free local execution · project flows under .sitelens/flows · optional Cloud/API when you add a key.

AI Agent Verification

Flagship QA templates

Live in SiteLens Studio

Start from proven flow templates—not blank scripts. Each run produces structured pass/fail summaries, dedicated result panels, and named screenshots you can share with teammates or wire into CI.

Internal Link Health

Check internal links without writing a crawler.

Exercise a bounded set of same-site links after deploys or nav changes—see which pages load, capture lightweight screenshots, and get a clear broken-link rollup in QA Studio.

Mobile Navigation Validation

Verify your mobile menu opens and exposes navigation.

On a phone-sized viewport, find a likely menu control, open it, and confirm nav content appears—with before/after screenshots and plain-language failures when the toggle or drawer is missing.

Deployment Verification

Confirm a deploy loads on desktop and mobile.

Post-deploy smoke on desktop and mobile viewports: page load, visible body, heading or main landmark, stable screenshot slugs, and CI-friendly pass/fail—without clicking through your whole app.

Pick a template in QA Studio, run against your URL, and review structured results above the step timeline. For multi-step authenticated journeys, see Workflow Verification below. Details on the QA page.

Workflow Verification

Scenario Runner

Most browser QA tools stop at a page. Real applications require setup. SiteLens can reuse saved browser profiles, initialize application state, run setup flows, and verify the workflow your users actually follow.

Scenario Runner

Chain reusable flows together using one browser session.

1
Login

Reuse a saved auth profile or run a login setup flow.

2
Initialize state

Select test data, toggle features, or seed application state.

3
Open workflow

Navigate to the route or feature under test.

4
Perform actions

Click, fill, and interact across multi-step journeys.

5
Verify outcome

Assert UI state, capture screenshots, and export artifacts.

Parameterized Flows

Pass IDs, URLs, environment values, and test data into reusable scenarios without rewriting flows. Scenario JSON under .sitelens/scenarios/ accepts params and {{placeholders}} that flow into each chained step.

Shared Browser Sessions

Cookies, local storage, session state, and authentication persist across the workflow. Login once, run setup flows, then verify—without restarting the browser between steps.

Built for Real Applications

  • Authenticated dashboards and SaaS applications
  • Admin interfaces and internal business applications
  • Multi-step workflows and role changes
  • Feature toggles, setup flows, and onboarding paths
  • Post-deployment verification beyond page-load smoke

Run scenarios via SiteLens MCP (sitelens_run_local_scenario) or the CLI. See the Scenario Runner guide and QA Studio scenarios.

SiteLens Desktop macOS download · v0.1.0 Local-first · Capture Runs → SiteLens QA Browser QA engine Local + Cloud/API → QA Studio Run inspection & templates Findings · screenshots → SiteLens MCP SiteLens Local from your IDE Cursor · Local integration → SiteLens Theme Design intelligence Tokens from live pages →

Proof from real work

Documented investigations and QA stories from shipping SiteLens—screenshots, before/after diffs, and agent verification loops. No hype; evidence you can reproduce locally.

Hall of Investigations

Timeline

Regressions and workflow bugs we found with Compare, flows, and local QA—problem, evidence, outcome.

View investigations

Real QA Stories

Cards

Developer and Cursor workflows: migrations, auth, deploy checks, scenarios, and screenshot comparison.

Read QA stories

Explore SiteLens Platform

One platform, four surfaces—QA engine (Local + Cloud/API), Studio for inspection, Theme for design intelligence, and MCP as the Local integration layer for your editor.

SiteLens QA

Live

The QA engine behind SiteLens Local and SiteLens Cloud/API—real Chromium, workflow verification, and structured evidence.

  • Workflow verification with Scenario Runner and shared sessions
  • Flagship templates: links, mobile nav, deploy checks
  • Saved auth profiles, parameterized flows, and step timelines
QA details

QA Studio

Live

Template runs, screenshot review, structured findings, and flow inspection on the shared QA engine (not a separate runtime).

  • Internal Link Health, Mobile Navigation, Deployment Verification
  • Structured pass/fail summaries above the step timeline
Open QA Studio

SiteLens Theme

Live

Typography, colors, and confidence-scored tokens from rendered pages—for embeds and match-my-site flows.

  • Formlyx and adapter-friendly JSON
  • REST /analyze/theme
Theme details

SiteLens MCP

Live

Integration layer for SiteLens Local in Cursor — install @sitelensapi/mcp from npm; optional Cloud/API tools when you add SITELENS_API_KEY.

  • Local browser QA workflows from your IDE
  • Optional Cloud/API run memory via MCP resources
MCP details

Recent QA runs

Live samples from SiteLens Cloud/API when the API persists runs (SiteLens Local runs stay on your machine). Select a row for screenshots and step detail.

Want the full QA picture? See SiteLens QA or open the dashboard.

Contact SiteLens

Tell us what you are building or what you want SiteLens to validate — localhost apps, staging URLs, deployment checks, MCP workflows, Theme API usage, or Cloud/API runs.

SiteLens Local SiteLens Cloud/API MCP (Local) setup