Skip to content

Menu

Motion

NewWeb monitoring that shows its evidence

Know the moment a page changes.

Peekivo is a website change monitoring service. Describe in plain words what matters; it finds the page, shows you the rule and a past example, then watches it. Every alert arrives with before-and-after evidence.

Things you can watch

  • Price drops
  • Restocks
  • New job postings
  • Competitor pricing pages
  • Policy and terms updates
  • Council meeting minutes
  • Grant deadlines
  • Documentation releases
  • Ticket availability
  • Rental listings
  • Course openings
  • Visual changes on a landing page
  • Out-of-stock alerts
  • Changelog entries
  • Status page incidents
  • Menu and opening hours
  • Exam results pages
  • Scholarship calls
  • Apartment price changes
  • Public tender notices
  • App store listing changes
  • Product spec changes
  • Event line-ups
  • Research assistant openings
The workspace

Where every change lands, with its proof.

These are the real Peekivo screens, filled with a sample workspace: the inbox your team works through, the evidence behind each alert, the health of every watch, and Ask.

The inbox puts changes that need a decision first, then watches whose reads fail, then other changes. Opening a change shows its evidence beside the list.

Sample data

These are the app’s own screens, running in your browser. Nothing here is a live account.

The product

Website change monitoring, from a sentence to the proof.

You say what you care about. Peekivo proposes the source and the rule, you approve it, and every later read is kept with its evidence.

Sample data

Ask in plain words

Type what you want to know. Peekivo finds the page and checks it against a past example before anything becomes a watch.

SampleAn illustration of the plan you would approve. Peekivo has not read this page.
Tell me when the Nintendo Switch 2 is back in stock at Best Buy.
Source found
bestbuy.com/product/switch-2-system/J7GSL57TGH
Past example:"Add to Cart"
Notify when it's back in stock · every 6 hoursReview plan

Every read on the record

A failed attempt never hides as "no change". The last attempt and the last successful read stay two separate facts.

Acme AnalyticsTeam plan priceLast attempt blocked
  • Change

  • No change

  • Failed attempt

  • Scheduled

Last attempt
Today 09:14
Last successful read
Today 08:14

See exactly what changed

The old value, the new value, both timestamps and the rule that matched, side by side.

Team plan · per seat
$24$29Rule matched
Before
2 Sep 06:14
After
3 Sep 06:14

Any change to the Team plan price

Told where you already work

One change reaches every destination you set up. Each delivery is tracked on its own, so a failed one never hides.

Switch 2 is back in stockbestbuy.com
EmailDelivered
Shared inboxDelivered
Team chatDelivered
WebhookRetrying

Honest when a page fights back

Blocked, unreadable and unknown are said out loud, never shown as healthy.

City council minutesRead, no change
Ticket resale pageSource blocked the read
Grant deadlinesStatus unavailable

Visual changes, not only text

Watch a region of the page as pixels. A new banner or a moved button counts, even when the words stay the same.

Visual7.4% of the region changed
See it run

One watch, start to finish.

An illustration with sample data, not a live account.
Behind every watch

Many pages, one quiet signal.

Each source is read on its own schedule. Reads that find nothing new stay quiet. A real change lifts out, is checked against your rule and reaches you. A blocked read is kept as blocked, never counted as quiet.

Illustration
  • Read, no change
  • Change found
  • Checked against your rule
  • Alert sent
  • Read blocked

Illustration with sped-up timing. It shows no real sources, reads or results.

How it works

Describe it. Check it. Approve it. Get told.

Nothing is watched until you approve it, and nothing is sent until a rule you can read says so.

1

Describe it

Say what you want to be told about, in your own words. A page address works too.

2

Check the source

Peekivo proposes the page and the exact field, and shows a past example so you can see it read the right thing.

3

Approve the rule

Read the rule in plain words before anything is watched. Nothing starts without your approval.

4

Get told, with proof

When the rule matches, the alert shows what changed, with captures from both reads.

Use cases

Built for the pages people keep refreshing.

Real public pages, asked for in plain words. Pick one to see how Peekivo reads it, spots the change and brings you the proof.

You type

“Tell me when the Nintendo Switch 2 is back in stock at Best Buy.”

Popular items sell out between refreshes. Peekivo reads the product page on your schedule and tells you when the button changes.

bestbuy.com/…Sample data
WatchingLast read 09:14
Nintendo Switch 2 at Best Buybestbuy.com/…
Watching
Availability button
Checks
Every 6 hours
Rule

Notify when the button changes from Sold Out to Add to Cart.

These are public pages anyone can open. Peekivo is not affiliated with them, and every change shown here is a sample.

Destinations

Sent where your team already looks.

Choose where each watch reports. Every destination is set up by you and tested before the first alert, and nothing is sent to a place you did not configure. Each one gets the change in its own form, and every delivery is tracked on its own.

Peekivo alert
FDA warning letters1 new letterSample data
  • EmailRequires setup
  • Shared inbox
  • Team chatRequires setup
  • WebhooksRequires setup
  • Phone pushPlanned
  • API and MCPPlanned
Size your workload

Plans follow the checks you actually run.

Pick how many pages and how often. You see the monthly check count before choosing a plan, and nothing is charged here.

What each plan allows

Hypothesis
  • PersonalMobile app only
    10 pages · 1,500 checks a monthChecks as often as every 6 hours
  • Solo
    50 pages · 5,000 checks a monthChecks as often as every 15 minutes
  • Team
    200 pages · 15,000 checks a monthChecks as often as every 5 minutes
  • Agency
    750 pages · 40,000 checks a monthChecks as often as every 5 minutes

Illustrative pricing and capacity hypothesis — not approved pricing and no purchase or confirmed entitlement.

Capacity calculator

Sources
Check cadence

Estimated checks in 30 days

1,500

30 checks per source over the period

Advanced usage is not estimated yet.

Solo covers these source and check counts; advanced usage still needs an estimate.

Assumptions

  • Illustration period: Sep 12, 2026 – Oct 12, 2026 (30 days, UTC)
  • Every source uses the same cadence, all day, every day.
  • No retries are assumed (retry factor 1).
  • Browser time, proxy traffic and AI tokens are not metered by this planner.

The 30-day illustration differs from actual billing periods; mixed or imported schedules use the same shared calculation.

Questions

Questions before you start

Read limits, evidence and approval before you decide to continue.

  • Can every public page be read?

    No. When a source cannot be read, Peekivo should show that status and its next step instead of treating it as no change.

  • Does the example create a watch?

    No. This page's example is synthetic. A real watch requires an explicit approval in the connected setup flow.

  • What happens after a change?

    The evidence and rule outcome stay visible so a team can distinguish a matching change from an unreadable source.

  • Does compatibility mean the source was read?

    No. Compatibility describes the input shape. Live reads are separate, scheduled checks with their own outcomes.

    Review migration compatibility
Coming soon

Start with the one page you check every day.

Peekivo is preparing a bounded early release. Leave your email to hear when a place opens.

Email is the only requested field.

Your email is stored encrypted and used only to contact you about early access. Read the Privacy Policy to see how it is protected and how to have it removed.