What's new
Everything shipped and a few things we decided not to build. Looking ahead? See the roadmap.
August 2026
v0.34
Writing in from the dashboard now gives you a subject line of your own, a reference you can quote, and a status that moves on its own as we work on it. You can also change the address we reply to, which used to look like a choice and quietly was not.
August 2026
v0.32
This page and the bell in the dashboard were two lists typed into the source code, unaware of each other. Every announcement was written twice, in two voices that drifted, and shipping one meant releasing the whole application. The unread dot had the same problem in miniature: it meant "the list is not empty", which is always true, so after the first look it told nobody anything. Both read one table now. A line is published by saving it, and the dot means what it says. Each item in the bell links to its own entry down this page instead of dropping you at the top of forty-five of them.
August 2026
v0.31
Until today this site was one application that drew itself in your browser after the fact. That works for a dashboard behind a login. It is a poor answer for a page somebody found through a search: what a search engine received was the same empty file for eighteen different addresses, with the same title and the same seventy-eight words, and whatever it made of that came later, if at all. The changelog you are reading was the clearest case, months of entries that were invisible to anybody who did not run JavaScript. Every marketing page is now built to finished HTML: the landing page went from nothing to just under three thousand words, this page to over four and a half thousand. The dashboard is untouched, it stays the application it should be.
August 2026
v0.30
Until this release, starting your own copy of PayGlue began with creating an account at a hosted identity service. Not as a recommendation: the dashboard threw an error at startup without it, so the software would not boot at all. That is a strange thing to ask of somebody who wanted twenty minutes to decide whether the tool was worth their time. An installation can now keep its accounts in its own database, and a setup wizard walks through the first account instead of showing a sign-in page you have no key for. A hosted provider stays fully supported and still brings what only it can, magic links, sign-in with Google or GitHub, and authenticator apps. Where those do not exist, the screens for them are left out rather than shown and broken. Then we followed our own setup guide on a clean laptop, and it broke on step one. Both bugs it found are fixed here.
August 2026
v0.29
PayGlue is source-available, and anyone can run it themselves. Until this release, an install that did so was quietly tied to ours. The snippet you copied out of your own dashboard carried our address, so your readers' browsers talked to our server instead of yours. The check that tells you whether the paywall is installed compared your site against our hostname, so it said no matter how correctly you had set it up. Your checkout could not finish, because the list of allowed return addresses was ours. And the welcome mail going to your customers was signed with our name. None of that was a decision, it was what happens when a product and its open-source build grow out of the same code without anybody checking which one a value belongs to. It is fixed, and this is the release where running PayGlue yourself actually means running it yourself.
August 2026
v0.28
A product without a mapping takes the payment, gets accepted, and grants nobody anything. That is the intended behaviour, and until now three separate parts of the dashboard reported it as fine: the editor saved without complaint, the badge saying it was unmapped sat in grey, and the event log marked it processed in green. Somebody paid, nothing happened, and there was no red anywhere. Each of the three now says what it means, and the event can be run again once the mapping exists.
August 2026
v0.27
Running the blog on a Ghost site at blog.payglue.io was the obvious choice, since we sell to Ghost publishers. It also meant every article we wrote was building a subdomain instead of the domain people actually buy from. A search engine treats those as two different places, so the work was landing in the wrong account. The blog now sits at payglue.io/blog, which is where it should have been from the start. And the Ghost site does not get switched off, it gets a better job: it is the live demo, running the real paywall, buttons and pricing table against a real provider.
July 2026
v0.26
Most of the people who find PayGlue were told about it by somebody else. There was never a way for that somebody to get anything out of it. There is now, and the page shows you what a handful of referrals is actually worth instead of asking you to take a number on faith.
July 2026
v0.25
Support looked like a wall: one narrow form, and a support PIN sitting above it as though everybody needed one. Most questions are answered in the docs faster than we can reply, and almost nobody needs the PIN, so the page now says both of those things out loud.
July 2026
v0.24
Handing over a publication or closing an account used to bounce you out of the dashboard and make you sign in again, which is a strange thing to ask of somebody who is already signed in. A confirmation window now opens where you are: your authenticator app if you have one set up, otherwise a code by email.
July 2026
v0.23
Removing a teammate was a change only the person clicking the button ever saw. That is fine when it is routine and bad when it is not, so the same email now goes to everybody with a reason to know about it.
July 2026
Collecting addresses and letting them wait made sense while there was nothing to hand people. There is now, so the waitlist and the third-party tool behind it are both retired. You can sign up and connect a provider today.
July 2026
If you have ever had to answer a GDPR question about a tool you use, you know the drill: hunt for the data processing agreement, then try to find out which sub-processors are actually involved. Both are now one click away, and they stay that way.
July 2026
v0.22
Handing a publication to a teammate only ever emailed one person: the current owner, asking them to confirm. The person being handed the publication was never told, and nobody found out how it ended. Fixed.
July 2026
v0.21
You no longer have to wait for a real sale to find out whether a provider connection actually works. Each mapping now has a "Send test" button that runs a real event through the full pipeline against a test email you control, and tells you straight away whether the member was granted in Ghost, or exactly what went wrong.
July 2026
v0.20
Patreon joins our supported providers. Connect your Patreon campaign and an active pledge automatically grants the Ghost access you mapped it to. A cancelled pledge revokes it, no manual CSV exports or Zapier workflows to maintain.
July 2026
We looked closely at adding Mollie, a popular European provider several of you asked for. After working through their API, we've decided to hold off for now. Mollie is built primarily for one-off e-commerce payments. Its recurring model asks each creator to build and run their own subscription integration, which doesn't fit PayGlue's "share a link, we handle the rest" approach. Only one-time payments would map cleanly today, and for that narrow slice the effort isn't justified yet. It's back on the backlog, not off the table. If enough of you need Mollie for one-time sales, we'll revisit.
July 2026
v0.19
Changing your mind about a plan shouldn't mean losing access overnight. Downgrading to a lower plan or canceling your subscription now comes with a clear grace period before anything actually changes, with a few reminder emails along the way so nothing catches you off guard.
July 2026
v0.17
By popular request, you can now sign in with your Google or GitHub account instead of (or alongside) a magic link email. Both can be connected from your account settings at any time.
July 2026
v0.14
Every account now gets its own unique, randomly generated secret embedded in its webhook URL. Not every payment provider reliably signs its webhook payloads, so we'd rather not rely on that alone. A per-tenant secret keeps each account's webhook delivery isolated regardless of what a given provider does or doesn't verify on their end.
July 2026
v0.13
Paddle joins Polar, Lemon Squeezy, PayPal, and Gumroad as a fully supported payment provider. Connect it, sync member access on completed transactions and subscription changes, and pull your product list straight into the Buy Button dashboard.
July 2026
v0.12
Gumroad joins Polar, Lemon Squeezy, and PayPal as a fully supported payment provider. Connect it, sync member access on sales, and pull your product list straight into the Buy Button dashboard. Alongside that, our infrastructure status is now public and monitored in real time.
July 2026
v0.11
Added automated dependency security scanning (Dependabot) and a CI pipeline with test coverage across both the open-source and production codebase.
June 2026
v0.10
After months of building in closed beta, we made the full codebase public. This was not a planned milestone from day one. It became the obvious next step once the closed beta validated that the product works and people genuinely need it. Open sourcing is how we earn trust beyond what any privacy page can say.
June 2026
v0.10
PayPal is now a fully supported payment provider. Subscribers who purchase through a PayPal subscription plan automatically receive Ghost membership access via the same mapping system used for Polar and Lemon Squeezy.
June 2026
v0.9
Lemon Squeezy is now a fully supported payment provider. Purchases made through Lemon Squeezy automatically create Ghost members, assign labels, and send welcome emails via the same mapping system used for Polar.
June 2026
v0.9
The Analytics section is restructured. Webhook Events and Product Mapping are now separate pages accessible from an expandable sidebar section, making it easier to monitor activity and review your configuration at a glance.
June 2026
v0.8
Ghost cannot mix a free tier, a one-time payment, and a subscription into a single coherent pricing table. This embed does exactly that. Paste one script tag into a Ghost HTML card and a fully styled table appears.
June 2026
v0.6
Ghost blogs without a Stripe connection can now gate content using a lightweight JavaScript snippet. PayGlue checks member access on every page load and shows a fully customizable overlay to non-paying visitors.
June 2026
v0.5
The first full payment-to-membership flow is live. A Polar purchase now reliably creates a Ghost member with the correct plan, labels, and a welcome email, without any manual steps.
June 2026
v0.5
Based on beta tester feedback, we launched public documentation. Every core workflow now has a dedicated article.
June 2026
v0.4
Early users asked the same question: "What exactly does PayGlue see from my customers?" We decided the right answer was not a FAQ bullet. It was a dedicated page with verifiable claims, backed by the actual source code.
June 2026
v0.4
We proactively reached out to the Ghost Foundation to clarify trademark policy before a wider launch. Their guidelines do not permit using "Ghost" in third-party product names. We rebranded to PayGlue and moved to payglue.io. The product, the team, and the mission stay exactly the same.
June 2026
v0.3
We initially planned to give every organization its own database schema for hard data isolation. After reviewing our actual threat model and operational complexity, we decided against it.
June 2026
v0.3
All API traffic now runs through our own domain. Django backend live on Railway with a real database and encrypted credential storage.
June 2026
v0.3
Integrations page fully redesigned, onboarding flow polished end-to-end, and auth session issues resolved.
May 2026
v0.2
PayGlue is live in closed beta. Founding Members purchase a spot and get auto-provisioned access to the full webhook relay pipeline.
May 2026
v0.2
The first public version of payglue.io goes live. Visitors can join the waitlist and lock in their Founding Member rate.
April 2026
v0.2
The core dashboard is built. Users can create organizations, manage their Ghost connection, and view payment mappings and event logs.
March 2026
v0.1
The core engine receives payment provider webhooks and translates them into Ghost membership actions.
January 2026
v0.1
PayGlue starts as a personal project. Ghost CMS only supports Stripe natively, but many creators use Polar, PayPal, or other providers.
Won't build
We looked at injecting PayGlue logic directly into Ghost themes via custom code injection. It would have created tight coupling between a user's theme and our infrastructure, making upgrades fragile and debugging nearly impossible. Webhooks are the clean boundary. We stay on our side of it.
Reconsidered
We explored offering a free tier to lower the entry barrier. We decided against it: free tiers require monetizing at scale through ads, data, or aggressive upsells. PayGlue is built to last as a small, focused tool. A 30-day trial at public launch will be the entry point instead.