Skip to content
Widgetail
Get early access

Roadmap

Measure. Value. Monetize. Signal.

The whole product journey in four stages, and exactly how far along each one is.

  1. 01

    Measure

    Live today

    Real engagement analytics.

    See how much real attention each page earns: how many visits, how many distinct sessions, how far people get.

    Real engagement analytics

    Done

    • Pageviews, unique sessions and average scroll depth from one script tag
    • Traffic over time, top pages, and change against the previous period
    • Anonymous sessions: no IP addresses, no fingerprints

    Building now

    • Reading behavior: engaged time, bounce rate, pages per session and a scroll-depth funnel
    • Audience breakdowns: traffic sources, devices, browsers, countries and busiest hours. The script already sees these; the Console doesn't report them yet

    Planned

    • Tracking controls: honor Do Not Track, exclude paths, strip query strings
    • Data retention settings and CSV export
    • A privacy-safe way to see return visits, if one can be designed without identifying people
  2. 02

    Value

    In development

    Content value scoring.

    Turn engagement into a per-page content value score, so a small, deeply read page isn't buried by a big, skimmed one.

    Content value scoring

    1. DesignDone
    2. BuildNow
    3. Private betaNext
    4. General availabilityNext

    Done

    • A 0–100 score for every page, built from four signals: time spent reading, scroll depth, repeat views and interactions
    • Scores compared within pages of similar traffic, so a small, deeply read page isn't buried by a big, skimmed one
    • A low-sample flag when a page has too little traffic to trust its score
    • A Console view of every score and its signal breakdown, tested on synthetic data

    Building now

    • Validating scores against real site traffic
    • Adding the time and interaction signals the score draws on

    Planned

    • Score trends against the previous run
    • Safeguards against artificially inflated engagement
    • Cross-site content authority signals, built with strict privacy thresholds
  3. 03

    Monetize

    In development

    Value-based content access and payment.

    Connect content value to payment: machine access priced by value, an edge layer that enforces it, payouts to you, and a polite way for ad-free visitors to support content worth paying for.

    AI agents

    1. DesignDone
    2. BuildNow
    3. Private betaNext
    4. General availabilityNext

    Done

    • An edge prototype that recognizes declared AI crawlers and answers with an HTTP 402 payment challenge
    • Prices set from a page's value score, within a floor and a ceiling
    • A Console view of challenges and paid requests
    • The whole flow tested internally, with simulated payments

    Building now

    • A real payment facilitator, so a first real payment can settle

    Planned

    • Per-crawler, per-page and per-day revenue breakdowns
    • Editable pricing rules: floor, ceiling and payment window
    • Detection beyond declared crawlers, for agents that don't identify themselves

    Edge and DNS

    1. Local devDone
    2. Staging deployNow
    3. Private betaNext
    4. General availabilityNext

    Done

    • The Edge Worker, working in local development: it classifies requests and serves toll challenges
    • Fail-open behavior, so a problem at the edge never blocks your visitors

    Building now

    • A staging deployment

    Planned

    • DNS-only setup that works with any host, with rollback to your origin at any time
    • A live view that separates bots from humans
    • A private beta with invited sites

    Payouts

    1. DesignDone
    2. BuildNow
    3. Private betaNext
    4. General availabilityNext

    Done

    • Payout logic built on Stripe Connect
    • Revenue tracked as pending until payouts are connected

    Building now

    • Connecting payouts end to end. It has never run against a live Stripe account

    Planned

    • A weekly or monthly schedule with a minimum threshold
    • Statements and tax forms for every payout
    • Earn in USD, receive in your local currency
    • Email alerts when a payout is sent or fails

    Ad-free visitors

    1. DesignDone
    2. BuildNow
    3. Private betaNext
    4. General availabilityNext

    Done

    • Ad-blocker detection, recorded as an anonymous analytics event
    • A soft, dismissible prompt, prototyped to appear only on pages that clear a value threshold
    • It never nags: dismissing it hides it for a week, and it loads after your content in an isolated layer that can't disturb your layout

    Building now

    • A real payment path behind the prompt (today's button is a stand-in)

    Planned

    • Ask readers to allow your site with one click
    • Wording and design that match your site, with your own frequency limits
    • Measuring the impressions the prompt wins back
    • Card payments alongside crypto
  4. 04

    Signal

    In development

    A new content-value signal for the web ecosystem.

    Make aggregate, privacy-safe content-value signals available, so advertisers and others can rely on real engagement instead of shallow traffic proxies.

    Advertisers

    1. ResearchNow
    2. DesignNext
    3. Private betaNext
    4. General availabilityNext

    Done

    • The anonymous, aggregate engagement data such a signal would draw on is already collected
    • The privacy design: page-level aggregates only, gated by a minimum-traffic threshold

    Building now

    • Research with publishers into which signals advertisers actually trust

    Planned

    • A written signal specification
    • Brand-safe topic labels derived from content scores
    • Aggregated audience segments with no personal data
    • Publisher controls over exactly what is shared, and with whom
    • Reporting on each advertiser relationship
    • A curated marketplace later; a programmatic exchange is out of scope

How to read this page

Three columns, used strictly.

Done
Finished. Where it's only been tested internally, or uses a stand-in, we say so.
Building now
Work in progress. Details may change.
Planned
A direction we intend to pursue. No date is implied.

What we're not saying

No dates. No price. No promises we can't keep.

  • There is no launch date for value scoring or monetization. We won't announce one until we can keep it.
  • Pricing hasn't been decided.
  • Nothing in development is available to use yet, and none of it has paying customers to point to.

Want to know why each stage matters? Start with what content value means or the question behind machine access, AI agents and websites.

Follow the roadmap from the inside.

Join early access to hear as each stage ships, and to help decide what comes next.

Get early access