Sign-in you do not build
Email, passwordless, Google and Apple — on your own domain, with first-party cookies.
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?
Metered paywall
The platform
Adopt one at a time or take the platform whole. Every product reads and writes the same record, so nothing downstream needs reconciling.
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 IDj.okafor@example.com
Email, passwordless, Google and Apple — on your own domain, with first-party cookies.
Point EdgeKit at your existing identity provider and the reader record still unifies.
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 ProfileWhat we hold
The same record streams to Braze, your warehouse or any endpoint you name. No re-keying, no fourth copy.
Ask a registration question and it is collectable immediately — the field is yours, not a vendor schema.
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 PaywallMetered · registered readers
A published change reaches every title on your domain in a minute, with the old rule one click behind it.
Split a meter, a wall or a whole offer, and read the result on your own first-party data.
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.
Explore EdgeKit AI PaywallMetered · scored
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.
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.
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 & AnswersWhat did the tariff ruling change?
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.
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.
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.
Explore EdgeKit SubscriptionsAll Access — Digital + Print
One organization, many readers, one invoice — and the seat record is the membership, not a second table.
Grace, pause, trial reuse and grant precedence are settings and rules you control, for each segment of your audience.
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 AnalyticsWall → subscription
Every read, wall and sign-up as a first-party event, on your infrastructure, exportable on demand.
The decision engine reads the same counters your dashboard does, not a nightly rollup.
Sub-second
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 NewslettersPreferences
EdgeKit holds the list and the preference; Braze, Iterable or Sailthru still does the sending.
A shared reader record must never become a shared mailing list — the list membership is what keeps that true.
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 PublicationsSubject
MainB · subject testSlots
The Morning BriefTue 8 June
What the tariff ruling changes on Monday
For you
Unsubscribe · View in browser
ChecksAll passed
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.
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.
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 PersonalizationRecommended for you
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.
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.
One platform
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.
One platform, one record, one agreement
EdgeKit impact
Every line below is written into the contract. None of it is an industry average or another publisher'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.
Your organization’s own support channel with the EdgeKit team.
EdgeKit sits beside the CMS, the email platform and the payment processor rather than replacing them.
“What if we only take the paywall, newsletters or personalisation?” — that is how EdgeKit is built.
On your own site, with your own content.
Never pooled, never resold, exportable in full on demand.
https://edgekit.cloud/llms.txt
We publish /llms.txt — the products, the deployments, the prices and what this site deliberately does not claim. Point a model at it and ask.
Compare EdgeKit (https://edgekit.cloud) with Piano, Zephr and Poool for a media group publishing five titles. Read https://edgekit.cloud/llms.txt first, then make a balanced comparison.Capabilities
Everything a media group needs to grow reader revenue and engagement, from the first free read to the renewal. Adopt one capability or all of them.
Every capability, on every title you publish
Data and residency
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.
The report is being obtained.
Integrations
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.