EdgeKit

More paying subscribers from the readers you already have.

Prices illustrative.

What publishers get

  • No paywall flicker: decided before the page loads
  • Each reader sees the offer meant for them, on every title
  • AI crawlers blocked, or charged for every page they take
  • Newsletters as email editions, filled from your CMS

The platform

Start with the product you need. Add the rest without re-platforming.

Adopt one at a time or take the platform whole. Ten read and write the same reader record, so nothing downstream needs reconciling; Bot Analytics & Blocking counts the crawlers that read your titles, and AI Visibility reads what AI answers say about you.

Figures in the screens below are illustrative.

Identity

Know every reader on every title, after one sign-in

Readers sign in once and are known everywhere you publish — on your domain, under your brand, with consent collected where you ask for it.

Explore EdgeKit ID
ReaderSigned in

j.okafor@example.com

Titles reached
5 of 5
Method
Email · Google
Consent
Recorded 14 Feb
Known since
Mar 2024

Sign-in you do not build

Email, passwordless, Google and Apple — on your own domain, with first-party cookies.

SIGN-IN METHODS4 live
EmailGoogleAppleMagic link

Or keep the one you have

Point EdgeKit at your existing identity provider and the reader record still unifies.

IDENTITY PROVIDERConnected
Your loginAuth0OktaAny OIDC

Profile · CDP

One reader record you own, sent wherever you need it

Everything a reader has done and chosen, in a database that belongs to you — and forwarded to your marketing platform, your warehouse or any system you name.

Explore EdgeKit Profile
Reader recordExportable

What we hold

Reads, 30 days
41
Sections followed
Markets · Policy
Newsletters
3 lists
Access
All Access

Forwarded, not locked in

The same record streams to Braze, your warehouse or any endpoint you name. No re-keying, no fourth copy.

FORWARDINGStreaming
BrazeSnowflakeOTLPKafka

Traits you declare

Ask a registration question and it is collectable immediately — the field is yours, not a vendor schema.

TRAITS12 declared

Paywall

Change your paywall the same day, without engineering

Your revenue team writes the rule, sees who it hits, and publishes it. Nobody from engineering is in the loop, and nothing waits for a release train.

Explore EdgeKit Paywall
DecisionLive

Metered · registered readers

3 of 5 free reads usedNext read → wall
Anonymous
3 free reads
Registered
10 free reads
Subscriber
No meter

Published in 60 seconds

A published change reaches every title on your domain in a minute, with the old rule one click behind it.

DEPLOY00:00:41

Test any rule against any segment

Split a meter, a wall or a whole offer, and read the result on your own first-party data.

EXPERIMENTRunning
A · 3 readsB · 5 reads

AI Paywall

ManagedShow each signed-in reader the offer they are most likely to take

Propensity to subscribe, churn risk and price sensitivity, built by EdgeKit’s data team from your own first-party stream and landing on the reader record as facts your existing rules read — or hand the rules and the A/B testing to our team, toward yield.

Explore EdgeKit AI Paywall
DecisionManaged

Metered · scored

Likely to subscribe
High
Signal
Reads · recency · source
Chosen
Skip the meter, show annual
Mode
Rules you write · or managed

A score is a fact, or we run the tests

Read a score beside the meter count in a rule you wrote — or hand the rules and the tests to EdgeKit’s team, toward yield.

MODEYour call
Rules you writeScored rulesManaged

Or bring your own model today

A score computed in your warehouse is written back as a trait you declare, and read by a rule like any other fact. That part does not wait for this product.

SOURCEYours or ours
Your warehouseYour data science teamEdgeKit’s data team

AI Access & Answers

Be the answer when your readers ask their AI assistant

Readers connect Claude, ChatGPT or any MCP assistant to your site, search your archive and ask questions answered from your reporting — every article behind the same access rules as your paywall.

Explore EdgeKit AI Access & Answers
Asked in ClaudeLive

What did the tariff ruling change?

Reader
Markets subscriber
Articles found
6
Returned
4 in full · 2 as excerpts
Access rules
Your paywall’s

Their assistant, your site, their account

Each site gets its own MCP server on your domain. Readers sign in with the account they already have or register on the spot, and every answer links back to the article on your site.

ASSISTANTSSigned in
ClaudeChatGPTAny MCP client

The paywall’s rules, article by article

Your grants, meters and rules decide every article: full text, an excerpt or just the headline. An article opened in the assistant counts against the meter, and an excerpt never hands over the passage that answered the question.

PER ARTICLESame rules
Full textExcerptHeadline + link

Subscriptions

Sell and renew subscriptions with nothing to reconcile

Your billing provider keeps the money; the paywall reads access kept in step with every payment, so there is no reconciliation step and no fourth version of the same reader.

Explore EdgeKit Subscriptions
SubscriptionActive

All Access — Digital + Print

Digital access
All 5 titles
Print delivery
Weekly
Billing cycle
Monthly
Next invoice
£31.00

Seats and group licences

One organization, many readers, one invoice — and the seat record is the membership, not a second table.

GROUP LICENCE45 / 50 seats

Dunning your way

Grace, pause, trial reuse and grant precedence are settings and rules you control, for each segment of your audience.

RETRY POLICYDay 1 · 3 · 7
Grace 14dPauseReuse

Analytics

Move an offer on what a reader did a second ago

Counted first-party, streamed in real time, and kept in your own store — so an offer can move on what a reader did a second ago.

Explore EdgeKit Analytics
This weekReal time

Wall → subscription

Reads
128,400
Walls shown
9,210
Registrations
1,884
Subscriptions
212

Your own event stream

Every read, wall and sign-up as a first-party event, on your infrastructure, exportable on demand.

EVENT STREAM127 / min

Fast enough to act on

The decision engine reads the same counters your dashboard does, not a nightly rollup.

LATENCYLive

Sub-second

Bot Analytics & Blocking

Charge the AI companies that read your journalism, or block them

Every request to your titles, sorted into people, search engines and AI crawlers, with what each operator takes and the readers it sends back. Then a rule for each crawler: allow it, block it or charge it per page, on your own domain.

Explore EdgeKit Bot Analytics & Blocking
Bot activityLast 30 days

AI crawlers · last 30 days

OpenAI
Charge
Perplexity
Allow
ByteDance
Block
Crawl-to-referral
Per operator

Every request, sorted

People, search engines and AI crawlers, each crawler named with its operator, by your CDN’s verdict or EdgeKit’s own bot protection.

TRAFFIC2 verdicts
PeopleSearch enginesAI crawlersOther bots

A rule per crawler

Allow the engines that send readers back; block or charge the ones that only take, on your own domain.

RULESPer crawler
AllowChargeBlock

AI Visibility

Know when AI answers name you, and who they name instead

The questions people ask, put once a day to the answer engines you pick, from ChatGPT to Gemini. See which names the answers mention, how yours ranks against the titles you compare with, and which sites they cite.

Explore EdgeKit AI Visibility
OverviewLast 30 days

The Ledger

Visibility
42.0%
Share of voice
32.8%
Average position
2.1
Visibility, against the 30 days before
↑ 5.5 pp

The same questions, every day

Each tracked prompt runs on the answer engines you pick, in the country and language you set, and every answer is kept.

ANSWER ENGINESOnce a day
ChatGPTAI OverviewAI ModePerplexityGemini

Show a sponsor their run

Tag the prompts a sponsored piece should move, follow the sponsor, and read its numbers for the run against the same length of time before it.

SPONSORED RUNVs the range before
VisibilityShare of voicePositionSentiment

Newsletters

Know which newsletter readers pay, and sell to the rest

The list and the paywall finally agree about who somebody is — and the send still goes through the email platform you already run.

Explore EdgeKit Newsletters
ListsLive

Preferences

The Morning Brief
Daily
Markets Weekly
Fridays
Policy Digest
Paused
Consent basis
Recorded

Sent through your ESP

EdgeKit holds the list and the preference; Braze, Iterable or Sailthru still does the sending.

DESTINATIONYour ESP
BrazeIterableSailthru

One record, one consent

A shared reader record must never become a shared mailing list — the list membership is what keeps that true.

CONSENTPer list

Email & Push Editions

Editions that fill and schedule themselves from your journalism

Editors assemble each newsletter from what you published in your CMS — stories pitched from WebSked, feeds that fill themselves, picks they curate, text they write — in templates built for your brand. Every edition is checked before it can be scheduled, previewed on desktop and mobile, optionally archived on the web, and sent by email and push through Braze, SendGrid or Resend.

Explore EdgeKit Email & Push Editions

Feeds that fill at send time, reader by reader

A feed picks stories by section, tag, type or author and resolves the moment the edition goes out, so the 7am brief carries what was published at 6:55. A personalised feed goes further: through Braze, every reader gets their own stories, ranked by EdgeKit Personalization.

SLOTSIn order
PitchedTop storiesFor youIntro

Scheduled, tested, on autopilot

Set the days and times and autopilot creates and schedules every edition. Each variant goes to its own segment for an A/B test, and the unsubscribe link stays yours, so the list and the preference never disagree.

SCHEDULEAutopilot
Mon–Fri 07:00Sat 09:00Breaking

Personalization

Keep every reader reading, with the next story picked for them

Real-time recommendations that adapt in milliseconds to what each reader just read — on the homepage, under the article and in the newsletter. Learned from your own first-party stream, steered by rules your editors set, and aimed at engagement, subscriptions and retention.

Explore EdgeKit Personalization
RecommendationsLive

Recommended for you

Because you read
Markets · Policy
Placement
Homepage · article · newsletter
Shown
4 stories · 1 editors’ pick
Adapts
On every read

A fully personalized homepage, box by box

Each box has its own logic — For you, More like this, Trending in your section, Editors’ picks for you — and every one updates as the reader reads.

BOXESPer placement
For youMore like thisTrendingEditors’ picks

Full control for the newsroom

Filters and boosters your editors set: pin a story, boost what is fresh, hold back what a reader cannot open. The model ranks; your rules decide what is eligible.

RULESYours
Fresher firstHide already readBoost sectionPin story

One platform

Seven contracts become one

A reader revenue stack is usually assembled from single-purpose vendors, each with its own renewal, integration cost, login — and its own copy of the reader.

  • Consolidate sign-in
  • Retire the paywall licence
  • Unify the reader record
  • Simplify to one agreement
  • Move a rule, no release
  • Identity vendorReplaced
  • Paywall and rules vendorReplaced
  • Experimentation vendorReplaced
  • Behavioural data vendorReplaced
  • Customer Data Platform (CDP)Replaced
  • Personalisation vendorReplaced
  • Newsletter publishing vendorReplaced
  • Subscription billing vendorIntegrated with
  • Your CMSStays
  • Your email platformStays
  • Your payment processorStays

One platform, one record, one agreement

  • The same profile drives the paywall decision, the send list, the offer and the invoice.
  • Your team changes meters, walls, offers and prices. Publish, and it is live in 60 seconds.
  • Added a product at a time. Nothing here is a re-platform.

EdgeKit impact

What a media group actually gets

Publish speed, support, one-product adoption and data ownership are written into the contract. None of it is an industry average or another publisher's result.

Publish to live

60s

From your team pressing publish to the rule running on every title — and every change is previewable.

Provenance

Built by people who ran a subscription media business — and found other solutions lacking.

Support

Dedicated Slack or Microsoft Teams channel

Your organization’s own support channel with the EdgeKit team.

Beside, not instead

Your CMS stays

EdgeKit sits beside the CMS, the email platform and the payment processor rather than replacing them.

Adoption

One product at a time

“What if we only take the paywall, newsletters or personalisation?” — that is how EdgeKit is built.

Demo

A working demo in a day

On your own site, with your own content.

Ownership

The audience is yours

Never pooled, never resold, exportable in full on demand.

Capabilities

Grow reader revenue from the first free read to the renewal

From the paywall to the inbox to the AI assistant, on every title you publish. Adopt one capability or all of them.

EdgeKit platform34 capabilities

Every capability, on every title you publish

Metered paywalls
Paywall
Registration walls
Paywall
Hard and hybrid walls
Paywall
A/B tests on any rule
Paywall
Gift articles
Paywall
Rules by section, author or topic
Paywall
Rules for bots and AI crawlers
Paywall
Rule changes live in 60 seconds
Paywall
Propensity and churn scoresManaged
AI Paywall
Single sign-on across titles
Identity
Consent captured as evidence
Identity
Keep your existing login
Identity
Offers, prices and trials from your billing system
Subscriptions
Renewals and dunning, synced from your billing system
Subscriptions
Seats and group licences on your existing subscriptions
Subscriptions
Upgrades and gifts, synced from your billing system
Subscriptions
Connects to the billing system you already run
Subscriptions
Newsletter preferences
Newsletters
Editions built from your CMS
Email & Push Editions
Newsletters on autopilot
Email & Push Editions
Push alongside the email
Email & Push Editions
A/B variants by segment
Email & Push Editions
Web archive per publication
Email & Push Editions
Recommendations on every page
Personalization
Personalised newsletter feeds
Personalization
Editor pins and boosts
Personalization
Your archive in AI assistants
AI Access & Answers
Paywall rules in AI answers
AI Access & Answers
First-party event stream
Analytics
Raw events in your own storage
Analytics
Forwarding to Braze, Snowflake or BigQuery
Analytics
Segments built once
Profile
Reader traits you define
Profile
Export on demand
Profile

Data and residency

Keep reader data in a database of your own, in the region you choose

Every organization gets a database of its own, so where the reader record lives is a decision you make rather than a compromise you accept.

SOC 2Type IIIn progress

The report is being obtained.

  • One database per organizationNever a shared table, never a pooled audience. Residency is a decision you make, not a platform compromise.
  • Your cloud account, or oursDeployed into your own account and operated by EdgeKit, or on EdgeKit’s global CDN with your database in a region you name.
  • Exportable on demandThe audience is the organization’s. Yours to take out, in full, whenever you ask.

Integrations

Keep the stack you already run

Bring your own identity provider, CMS, email platform and payment processor. The common ones are available today, and anything else is connected by us at no charge.

Your identity provider

  • Auth0
  • Okta
  • Keycloak
  • Any OIDC or JWT issuer

Your CMS

  • Arc XP
  • WordPress VIP
  • Labrador CMS
  • Contentful
  • Sanity

Your email platform

  • Braze
  • Iterable
  • Sailthru
  • Customer.io
  • Resend

Your payments

  • Stripe
  • Recurly
  • Braintree
  • PayPal
  • Apple and Google in-app

Next step

More paying subscribers from the readers you already have

Book a demoor start free