The trouble with comments living on Substack
Substack comments work fine inside Substack. The problem starts when you think about where they live. The discussion under your posts sits on Substack's platform, tied to Substack accounts, visible on Substack's terms. If you ever move your newsletter to your own domain or a different tool, the comments do not come with you the way your subscriber list might.
Substack also gates commenting in ways that suit its model, not always yours. Comments are often limited to subscribers or paid subscribers, and readers need a Substack account to take part. That is a reasonable design for a closed platform, but it is friction if your goal is an open discussion under content you own.
Owning the conversation on your own site
Many writers now run a real website alongside or instead of Substack, on Ghost, WordPress, Astro, or a static site. Once you have your own pages, you can attach comments that belong to you. Gabden adds a thread to any page with one script tag, keyed to the page's canonical URL.
<div id='gabden-conversations'></div>
<script async src='https://YOUR-SITE.gabden.com/conversations.js'
data-page='canonical'
data-theme='auto'></script>Copy your Gabden subdomain (the YOUR-SITE part of the URL) from the dashboard after you register. The thread renders under your post, and because it is keyed to the URL, it stays with the content even if you change platforms later.
What you gain over Substack comments
You own the data
This is the core of it. With Gabden you own the comment data and can export it as JSON or CSV whenever you want. The discussion is not a hostage to a platform decision.
No account required to read or reply
Readers do not need a Substack login, or any login. They can post anonymously, comment as a guest with a name and email, or sign in with Google or GitHub. Fewer barriers usually means more replies, especially from readers who arrive from search rather than from a subscription.
Privacy
Gabden uses no tracking cookies, no fingerprinting, and no cross-site tracking. Analytics are anonymous and aggregate. For a writer who talks about independence and reader trust, a comment tool that does not surveil the audience is consistent with the message.
You decide who can comment
You are not stuck with Substack's subscriber gates. If you want to keep discussion open to everyone, do that. If you want tighter control, use moderation modes: pre-moderate everything, auto-approve returning verified people, or moderate only anonymous users. A blocked-word filter and a spam queue handle the noise.
Keeping the newsletter and the discussion together
Leaving Substack for comments does not mean leaving email. Plenty of writers keep sending the newsletter from wherever they like and host the archive and its comments on their own site. The discussion lives under the web version of each post, and the newsletter drives readers there. If you want to grow the list from that discussion, see turn blog comments into email subscribers.
Cost and setup
Gabden is free up to 100,000 widget views per month per website, with a small "Powered by Gabden" mark on the free tier. Plus removes the mark and lifts the view cap for 5 dollars per month per website. Details are on the pricing page. Setup is the two lines above plus a key, and the embed is about 10KB, so it does not slow the page. If you write on Substack today and want to test owning your comments, start with one post on your own domain and see how the discussion carries over.
Join the discussion