Patreon, wired in

You already have patrons. They pay every month, they are used to the tiers you set, and Patreon handles the cards, the taxes and the dunning. What Patreon does not give you is somewhere good to put the work — its post feed is a timeline, not a library, and anything you published four months ago is effectively gone.

So this connects the two. Patreon keeps the money and the identity. Your library lives here, and your patrons' tiers open it. A reader signs in with Patreon, we check the pledge on your campaign, and the sections you mapped to that tier unlock — in seconds, and without you touching a list of names.

Connect once, in about five minutes

You register an app on Patreon, paste two redirect URLs into it, and paste the client id and secret back here. From then on it is your app: your patrons see your name on the consent screen, not ours, and your API rate limit is yours alone. If you ever leave, the app leaves with you.

Your tiers arrive automatically. You will not retype them.

Map a tier to a section

A grant reads the way you would say it out loud: the $20 tier opens the archive, or anyone over $5 gets the field notes. Both kinds work, and the amount version is the one that survives you renaming or rebuilding a tier later — which most creators do, and which quietly breaks integrations that only understand tier names.

Grants stack. A section can be open to a tier, an amount, a role, and the public all at once, and any one of them is enough to get in.

It keeps itself honest

When a pledge starts, changes or stops, Patreon tells us within seconds and access follows. An hourly reconcile re-reads your whole patron roll as a backstop, because a webhook that never arrives is not a rare event, and a cancelled patron who keeps their access is not a small problem.

A declined card does not silently keep paying out. Patreon keeps a declined patron visible while it retries; by default we treat that as unpaid and close access, and you can extend a grace period if you would rather give people the benefit of the doubt.

Posting to Patreon: what is actually possible

Here is a limit worth stating plainly, because some tools imply otherwise: Patreon's API cannot create posts. There is no endpoint for it, for us or for anyone. Any product promising fully automatic posting to Patreon is either using your password or overstating what it does.

What we do instead: compose the post for you from any article — a real excerpt, cut cleanly, with the link back — you paste it into Patreon, and we watch for it going live and match it back to the article automatically. One paste. Everything either side of it is handled, and the tracker only ever says a post is live once it has actually seen it.

Your patrons stay your patrons

A patron signing in gets a reading account and nothing else — they never reach the workspace, and they never appear as a seat on your plan. Their pledge data belongs to your organisation alone: another creator on this platform cannot see your patron roll, your tiers, or your grants, and a patron of theirs gets nothing of yours.