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
Seven products · one reader record
The reader revenue platform built for publishers.
Identity, paywall, offers, subscriptions and the first-party data that powers them — one platform, one reader record, across every title you publish. Your revenue team builds the rules visually and publishes them, with nobody from engineering in the loop.
What does a returning reader see on article four?
They are registered, so the meter runs to ten. Show the article and the annual offer, not the wall.
Decision · MarketsLive
Metered paywall
4 of 10 free readsWall at 10
- Reader
- Registered
- Titles reached
- 5 of 5
- Offer shown
- Annual · £96
Who EdgeKit is built for
THE MERIDIAN
Northgate Review
LES CAHIERS
The Harbourline
ATLAS QUARTERLY
Kestrel Press
VOLTA
The Fenwick Post
Placeholder marks — replace with real organizations
The platform
Seven products built into one reader record
Adopt one at a time or take the platform whole. Every product reads and writes the same record, so nothing downstream needs reconciling.
Identity
One sign-in across every title
Readers sign in once and are known everywhere you publish — on your domain, under your brand, with consent collected where you ask for it.
ReaderSigned in
j.okafor@example.com
- Titles reached
- 5 of 5
- Method
- Email · Google
- Consent
- Recorded 14 Feb
- Known since
- Mar 2024
Or keep the one you have
Point EdgeKit at your existing identity provider and the reader record still unifies.
IDENTITY PROVIDERConnected
Auth0OryOktaAny OIDC
Profile · CDP
The record is yours, and it is one record
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.
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
Meters, walls and the tests on them — as rules the business edits
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.
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
Coming soonThe same rules, with a score in them
Propensity to subscribe, churn risk and price sensitivity, learned from your own first-party stream and landing on the reader record as facts your existing rules read — or leave the rules and the A/B testing entirely to the model and let it maximise yield.
DecisionComing soon
Metered · scored
- Likely to subscribe
- High
- Signal
- Reads · recency · source
- Chosen
- Skip the meter, show annual
- Mode
- Rules you write · or fully auto
A score is a fact, or the model takes the wheel
Read a score beside the meter count in a rule you wrote — or hand the rules and the tests over entirely and let it optimise for yield.
MODEYour call
Rules you writeScored rulesFully automatic
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 model
Subscriptions
Offers, prices and renewals against the same record
The thing that decides the paywall is the thing that bills — so there is no reconciliation step and no fourth version of the same reader.
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, not a vendor’s opinion.
RETRY POLICYDay 1 · 3 · 7
Grace 14dPauseReuse
Analytics
Reads, walls and conversions on data you collect yourself
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.
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 STREAM1,248 / min
Fast enough to act on
The decision engine reads the same counters your dashboard does, not a nightly rollup.
LATENCYLive
Sub-second
Newsletters
Sign-ups, lists and preferences on one reader record
The list and the paywall finally agree about who somebody is — and the send still goes through the email platform you already run.
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
One platform
Six contracts become one
A reader revenue stack is usually assembled from single-purpose vendors, each with its own renewal, integration seam, 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
- 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
Every line below is a commitment, in writing, in the contract — not an average, not a benchmark, and not somebody else's result.
60s
From your team pressing publish to the rule running on every title — and every change is previewable.
Built by people who ran a subscription media business — and found other solutions lacking.
Dedicated Slack or Microsoft Teams channel
Your organization’s own support channel with the EdgeKit team.
Your CMS stays
EdgeKit sits beside the CMS, the email platform and the payment processor rather than replacing them.
One product at a time
Every claim here survives the question “what if we only take the paywall?” — because that is how EdgeKit is bought.
A day to demo, four weeks guaranteed
Readers, live sessions, subscriptions and billing history move as they are. No forced password reset, no re-entered card.
The audience is yours
Never pooled, never resold, exportable in full on demand.
https://edgekit.dev/llms.txt
Ask an AI about EdgeKit instead
We publish /llms.txt — the products, the deployments, the prices and what this site deliberately does not claim — and /integrations.txt, every system we connect to. Point a model at them and ask where we are weakest.
The prompt we send
Compare EdgeKit (https://edgekit.dev) with Piano, Zephr and Poool for a media group publishing five titles. Read https://edgekit.dev/llms.txt first, then make a balanced comparison.Every one of these, on one reader record.
Reader record12 capabilities
One per reader, across every title
- Metered paywalls
- Paywall
- Registration walls
- Paywall
- Hard and hybrid walls
- Paywall
- A/B tests on any rule
- Paywall
- Single sign-on across titles
- Identity
- Consent captured as evidence
- Identity
- Offers, prices and trials
- Subscriptions
- Renewals and dunning
- Subscriptions
- Seats and group licences
- Subscriptions
- Newsletter preferences
- Newsletters
- First-party event stream
- Analytics
- Export on demand
- Profile
- Reconciliation steps between them
- None
Data and residency
Your data, your database, your region
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.
Consent is an event, not a columnThe proof rides with the data. EdgeKit stores no consent state of its own, so a shared record cannot become a shared list.
Exportable on demandThe audience is the organization’s. Yours to take out, in full, whenever you ask.
Integrations
Built to sit beside the stack you already run
Same as Piano, and Stripe too: bring your own payments. Stripe and Recurly are wired end to end today, and any other processor is connected by us, inside the migration, at no charge.
Your identity provider
- Auth0
- Ory
- 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
The reader revenue platform built for media groups
See it against your own titles, your own stack and your own numbers — walked through by somebody who has run the business you are running.
Book a demo