Approved baseline · Oct 20
Current · today 09:12
Changed areas are outlined on the new screenshot
Each new screenshot is compared with the baseline you approved. Changed areas get numbered boxes, the largest first.
The pages you choose, on desktop and mobile, as often as every 6 hours. When a button goes missing, an image breaks or checkout returns a 500, you get an alert with a link to the screenshot.
Plans start at €19 per month. Prices are provisional.
How it works
Rookflare reads your sitemap, lets you choose the pages to watch and takes the first screenshots for you to approve as the baseline. There is nothing to install on your site.
Website address
Step 1
Use the address your customers use. Rookflare finds the pages through your sitemap.
Step 2
Keep all of them, or only the ones that earn money, such as pricing and checkout.
Baseline saved. Next scan in 6 hours.
Step 3
Later scans are compared with it. You replace it only by approving a change. On Growth and Agency, uptime checks start on the homepage too.
Visual comparison
Drag the handle to compare the approved baseline with today's screenshot. Each changed area gets a number, largest first, and the list shows where it is on the page, its size and its changed pixels. Tiny changes stay folded away until you open them.
Websites Northwind Shop https://northwind-shop.example/
https://northwind-shop.example/ Needs review
Baseline Oct 20 → this scan today 09:12 · 9.9% of pixels changed
Demo · simulated change
Drag the handle, or focus it and use the arrow keys.
Changed areas (6)
Desktop · compared with baseline v14Changed areas (4)
Mobile · compared with baseline v14The baseline stays as it is until someone approves this scan.
Checks
Visual changes wait for someone to review them. Technical failures, such as a server error, open an issue straight away. Between scans, uptime checks watch whether your key pages answer.
All featuresApproved baseline · Oct 20
Current · today 09:12
Each new screenshot is compared with the baseline you approved. Changed areas get numbered boxes, the largest first.
1440 × 900
By default, pages are captured at 1440 and 390 pixels wide, so a layout that only breaks on phones is found too. Both captures count as one page.
Issue opened for https://northwind-shop.example/checkout/
Each request is logged with its status code and response time. A 4xx or 5xx response opens an issue at once, without waiting for a review.
✕ Uncaught TypeError: Cannot read properties
of undefined (reading 'total')
Failed to load resource: the server
responded with a status of 500
Errors thrown while a page loads are recorded with their message, so a broken checkout script shows up on the next scan.
https://northwind-shop.example/tents/: tent-ridgeline.webp returned 404
When an image returns an error, the page and the image address are listed.
Key URLs are requested every minute on Agency and every 5 minutes on Growth. A page counts as down only after 3 failed checks in a row, about a minute apart, and a confirmation check.
Rookflare APP 09:12 · #ops-alerts
Critical: Page returns HTTP 500
View issue
Rookflare APP 09:40 · #ops-alerts
Resolved: Page returns HTTP 500
You get one message when an issue opens and a separate one when it is resolved. If the same failure is found again, the issue is updated and no new alert is sent unless it gets worse.
Selected element
Link · “Shop tents”
Found on desktop and mobile
Watch this elementOpen a screenshot of your page and click the order button, the contact form or the cart. Rookflare finds a stable way to recognize each one and opens a critical issue when it disappears or is hidden, on desktop or on mobile. No code needed.
A visual change is never accepted on its own. Someone on your team approves it as the new baseline or marks it as expected.
title: Tents & shelters · Northwind Shop
robots: index, follow
robots: noindex
canonical: https://northwind-shop.example/tents/
A noindex robots tag and a missing title are flagged, and a changed title or canonical address is compared with the previous scan.
Integrations
Start a scan from your deploy pipeline, get alerts where your team already looks and send clients a monthly report under your own logo.
All integrations and setup guidesDemo: someone copies the GitHub Actions step, the next deploy calls the deploy hook and Rookflare starts a scan of the website right away.
Scan after deploy
Your CI or host calls one URL with a secret token after each deploy. Repeated calls for the same deploy start only one scan.
Add the token as the ROOKFLARE_DEPLOY_TOKEN repository secret, then add this step after your deploy step.
Sample endpoint and placeholder token
Alert channels
For agencies
Add each client as a website, invite your team and filter the list to the sites that need someone today. Each month, send every client a report with uptime and scan results under your own logo.
Pricing
Every plan includes every check, desktop and mobile capture. Plans differ in how many websites and pages you monitor, how often, uptime checks, alert channels, team and client features, and how long history is kept.
Prices and limits are provisional until billing launches. You will see the final price before you pay.
Rookflare scans the pages you choose on a fixed schedule. It captures desktop and mobile screenshots, compares them with the baseline you approved, and checks HTTP status, broken images, JavaScript errors and basic SEO signals. On Growth and Agency it also checks that your key URLs respond, as often as every minute.
No. A visual difference is marked as a change that needs your review, never as a confirmed failure. You decide whether it was expected: approve the new screenshot as the baseline, mark the change as expected, or fix the page.
No. Rookflare visits your pages from the outside, the way a visitor would. You add a website, verify that you control the domain, and choose the pages to monitor.
Starter scans once a day, Growth every 12 hours and Agency every 6 hours. Scan frequency is fixed per plan; you can choose a longer interval, but not a shorter one.
Rookflare requests each uptime URL on a schedule: every 5 minutes on Growth and every minute on Agency. A page counts as down only after 3 failed checks in a row and a failed confirmation check, so one slow response does not wake anyone. After a failed check, the next checks follow about a minute apart, so an outage is confirmed about 2 minutes after the first failed check on both plans. You get one email or Slack alert when it goes down and another when it is back up, with how long it was down.
Growth and Agency. Growth checks up to 3 URLs per website every 5 minutes, Agency up to 10 URLs per website every minute. Starter has no uptime checks, but its pages are still scanned once a day. When a website starts being monitored, its homepage becomes its first uptime URL.
One URL is one monitored page, even though we capture it at both desktop and mobile sizes. Limits apply across your whole organization.
Yes. The Agency plan covers up to 20 websites and 500 monitored pages, lets you invite team members, and keeps 180 days of history.
Not yet. Prices and limits on this site are provisional until billing launches and may change. Anything you sign up for will show its price before you pay.
Screenshots are stored in a private bucket and are shown in the dashboard only to signed-in members of your organization, through links that expire after a few minutes. They are never attached to alert emails or Slack messages. On the Agency plan, a client report you share includes the screenshots of the changes it lists.
Yes, on the paid Growth and Agency plans (the free trial does not include them). Each person verifies their own mobile number with a code sent by text message, then a phone channel can send a text message for critical problems and place a short automatic call when a site goes down. The recovery comes as a text only. Growth includes 50 phone alerts a month and Agency 200, texts and calls counted together. When they are used up, email and Slack alerts keep going and the owners get one email.
Yes, on Growth and Agency. Create a deploy hook in the website settings and call its URL with the secret token when a deploy finishes. The dashboard gives ready snippets for GitHub Actions, Vercel, Netlify, WordPress and cURL. Rookflare then scans the website straight away instead of waiting for the next scheduled scan, and repeated calls for the same deploy start only one scan.
Scheduled scans, uptime checks and alerts stop. Your websites, settings, approved baseline screenshots and issues stay in your account until you delete it; as on any account without a plan, scan history and screenshots older than 30 days are removed. Monitoring continues where it stopped as soon as you choose a plan.
No, it's one free trial per person. If you already used a free trial in an organization you own, a new organization starts with a plan instead. A website that was monitored on a free trial can't be monitored on another free trial for a year, so a new account doesn't restart the trial for the same site. For this check we keep only a one-way hash of the website's domain, never who used it. If you need more time to decide, contact us.
Add your address, pick the pages and approve the first scan as your baseline.
Plans start at €19 per month. Prices are provisional.