Screenery
Screenery is a developer tool and screenshot registry that publishes the screenshots already produced by a team's tests to stable URLs. Those URLs update when the default branch changes, keeping documentation, READMEs, websites, help centres, marketing pages and AI-agent context aligned with the product.
At a Glance
- Software teams that run Playwright or other screenshot-producing tests
- Open-source maintainers and teams embedding screenshots in GitHub READMEs
- Developer-documentation and technical-writing teams
- SaaS product-marketing, growth and sales teams
- +2 more
AI Tools by Screenery
(1)Screenery
Screenshot Registry for CI Docs
Discussions
No discussions yet
Be the first to start a discussion about Screenery
Latest News
screenery CLI 0.4.0 published on npm with push/promote, clips, eval publishing, demos, diffs, publishing receipts, login and MCP support
Screenery for coding agents repository launched for Claude Code, Codex and Cursor
screenery/push Action updated to CLI 0.4.0 and made the source repository for the GitHub Action
screenery/push synchronized to CLI 0.3.0 and added partial-push support
Products & Services
Stores screenshots, recordings and related build metadata and serves stable CDN URLs such as https://cdn.screenery.dev/{org}/{project}/{asset}@latest.png. Channels include @latest, pull-request channels, immutable versions, @clip and @eval.
The npm CLI for pushing and promoting screenshots, capturing live-page clips, publishing LLM UI evaluation reports and rendered demos, running optional pixel/findings diffs, generating galleries/README/PR-comment Markdown, verifying publishes, signing URLs, authenticating users and running the MCP server.
A composite GitHub Action that installs the screenery CLI and publishes screenshots from CI. GitHub OIDC can exchange for a short-lived publish credential, avoiding a stored repository secret.
An MIT-licensed plugin/repository for Claude Code, Codex and Cursor. It provides the hosted MCP server plus seven written skills for screenshot tests, docs embeds, Play Store listings, demo clips, uivet evaluations, Playwright goldens and baseline comparisons.
Market Position
Screenery positions itself between visual-regression systems and documentation-screenshot tools: unlike Percy and Applitools it does not render pages in a hosted browser grid, and unlike Chromatic it is not a Storybook platform. Its differentiator is publishing the screenshots a team's own tests already created to stable URLs that follow the default branch, while adding optional diff gating, PR review and agent/MCP workflows. The company's comparison page identifies Percy, Chromatic, Argos, Applitools, BackstopJS, Lost Pixel, LaunchBrightly, Promptless and Ferndesk as adjacent alternatives.
Leadership
Founders
John Farrell
Independent software builder behind Screenery and the johnf.build product stack. His LinkedIn profile describes years in business software, including engineering-management and senior software-engineer/team-lead roles at CloudRadial from 2019 through July 2026; his GitHub handle is jfreal. His personal Screenery page says he built the product after repeatedly needing current screenshots for his own products.
Executive Team
John Farrell
Founder and builder
Independent software developer and creator of Screenery. Previously held engineering-manager and senior software-engineer/team-lead roles at CloudRadial; he also builds Pheidi, Merge & Tell and other products in the same stack.
Founding Story
Farrell says docs, store listings, product pages and Merge & Tell posts depended on frozen PNGs that became stale. He built Screenery so CI could publish screenshots on every build and give each asset a URL that updates when a release ships; he describes the path from specification to published CLI as taking under two weeks.
Business Model
Revenue Model
Hosted SaaS/service for storing and delivering screenshots and related assets, with usage/plan limits and paid tiers implied by the public comparison page; the service also distributes a free npm CLI and open-source MIT-licensed GitHub integrations.
Pricing Tiers
A Free plan is listed publicly; the comparison page says its limits were not published yet.
Target Markets
- Software teams that run Playwright or other screenshot-producing tests
- Open-source maintainers and teams embedding screenshots in GitHub READMEs
- Developer-documentation and technical-writing teams
- SaaS product-marketing, growth and sales teams
- Teams publishing app-store/store listings and demo media
- Teams using Claude Code, Codex, Cursor or other coding-agent workflows
- Keeping screenshots in documentation, READMEs and help centres synchronized with product releases
- Keeping homepage, pricing/feature pages, sales materials, store listings and launch posts current
- Publishing Playwright visual-regression goldens while retaining them as public or controlled embeds
- Reviewing screenshot changes in pull requests and blocking accidental visual regressions
- Monitoring live marketing or documentation pages for visual drift
- Giving coding agents current visual context through MCP and stable screenshot URLs
- Pheidi, a running-plan product: its tests capture 15 screens on every merge and the homepage plus 13 documentation pages use @latest screenshots.
- Merge & Tell: Screenery reshoots its screens on each merge and public pages use Screenery shots by name.
- Auspex Fatalis: Screenery posts a screenshot gallery on pull requests and serves help-article images.
- John Farrell's johnf.build site: its live screenshots are served through Screenery rather than exported manually.