| Does the paid text ever reach the reader’s browser?Favours EdgeKit | Three documented locking modes: hide the text with CSS, trim it in the browser, or take an event and write the enforcement yourself. In the first two it was delivered. | No. EdgeKit’s global CDN sits in front of your own site, decides server-side and withholds the gated body, so the paid text never leaves your origin. It asks one thing of your template: a CSS selector naming the article body. Half the paywalled sites we surveyed already declared one; the rest add it in a single deploy, and we verify it per title before you sign. |
|---|
| Can we run our own SQL against our reader data?Favours EdgeKit | Reader data sits in Poool’s platform. Flow, described as their data export solution, is the documented way to get a copy of it back out. | Your reader record is a database of your own. Ask for managed deployment and that database is a project in your own cloud account. |
|---|
| Can we get a price before we talk to anyone?Favours EdgeKit | No published price and no pricing page. The route to a number is a demo booking or a sales email; no figure appears on the site. | The whole rate card is on the site: eight meters, an included amount and a rate on each, and a $99 monthly floor. |
|---|
| Does the paywall learn on its own, or do we write every rule?Neither | An engagement score computed in their dashboard from recency, frequency and pages per session, 0 to 100, sorting readers into volatile, occasional, regular and fan, each with its own journey. It is a marketing formula rather than a model, the same shape EdgeKit computes; machine-learned propensity arrives through a partner, Sophi.io, whose score Poool takes in to pick the journey. | Rules you write, over scores EdgeKit already computes: Profile Streaming derives engagement, recency and frequency on the live event stream as it lands on the reader record, and a rule reads them in the same request — as it reads a score written back from a model you already run. What is not shipped is the model that learns the score: EdgeKit AI Paywall, scores an authored rule reads or the rules and the tests handed to the model to optimise for yield, is coming; ask us where it is. |
|---|
| How quickly can we be live?Neither | A hosted script and a dashboard. Their own published figure is integrated in under two days and live in a month, across 250+ publishers. | The same shape, if you want it: a browser script on the pages you already render, walls drawn client-side, nothing in front of your site and no traffic change. The CDN can come later. |
|---|
| Who changes the paywall, the developers or the revenue team?Neither | The revenue team. A journey builder, where a scenario is an ordered list of widgets the reader advances by completing the previous one, with scored reader groups behind it. | The revenue team. An ordered rule they write and deploy themselves, landing as one numbered entry naming who shipped it. |
|---|
| Can our data team reach the raw behavioural rows?Neither | Audit’s dashboards, plus Flow, their data export solution, for a copy of what sits underneath them. | Every event, unsampled, as Parquet in object storage you own, and the export is self-serve: CSV on demand from the console, or a scheduled export delivered to a bucket you name. |
|---|
| Can we keep the billing vendor we already run?Neither | Subscribe handles checkout and subscriptions, and their docs state Poool deliberately does not hold the identifiers for server-side Stripe payment, leaving those with you. | EdgeKit holds one billing model that every processor maps into — accounts, catalog, subscriptions and their items, schedules, invoices, payments, refunds and disputes — and every row records which system it came from. The paywall decision never branches on the provider, so connecting one EdgeKit has not connected before is a connector into a model that already exists, not a second billing model. Recurly and Stripe map into it today, each a full mirror kept current by webhook. Any other processor is wired by EdgeKit, at no charge, inside the migration rather than as a change order after it — and a group mid-cutover can run two at once. |
|---|
| We publish several titles. Is that one reader or several?Favours EdgeKit | Access and Subscribe are each started with an app id. Darwin CX, which agreed to acquire Poool in March 2026, brings a central subscriber database behind them. | Your choice, separate or combined: one reader record behind every title with one agreement and one set of counts, or a separate record per title. |
|---|
| Who splits the traffic for a test, and who reads the result?Neither | Poool. A test is a second scenario in the same context, with a slider setting the split between them, and it runs two versions at a time. Results are the two scenarios drawn against each other in the dashboard’s analysis view. | EdgeKit, or the experimentation vendor you already run. Either EdgeKit assigns the arm itself, or it reads the one your vendor assigned and decides on that — so the split and the statistics can stay in the tool your team already uses. |
|---|