The economics of Substack versus Ghost and WordPress

The economic gap between Substack and open-source publishing makes the choice clear for teams managing creator-monetized newsletters. If you manage 100 paid subscribers paying $10 each per month, Substack takes $1,992 in annual fees. This amount combines Substack’s 10% platform cut with Stripe’s 2.9% plus 30 cents and 0.7% for recurring billing. You also pay a $50 one-time fee to use a custom domain. I find the $1,400 annual difference between Substack and a WordPress setup using Bluehost for $2.99 per month and MemberPress for $199.50 per year to be a massive motivator for switching.

The cost of scaling a newsletter

Substack functions as a Patreon alternative for newsletters, but it lacks the functionality of a full content management system. It provides a minimalist editor, basic website, and podcast hosting, yet it restricts your creative freedom. You cannot use custom fonts, change designs, or access many different email marketing services. If you want to send newsletters to your audience, you must use Substack’s own tools. In contrast, WordPress allows you to connect to platforms like Brevo, Drip, Kit, or Mailchimp. You can also create multiple subscription levels with MemberPress, unlike Substack which allows only one subscription plan for all users. I find the inability to customize formatting or designs to be a significant drawback for professional creators.

The math for scaling a high-revenue newsletter becomes punishing as your audience grows. If you charge $10 per subscriber, the combined Substack and Stripe fee totals $1.66 per transaction. This prevents you from keeping the full profit of your work. Because Substack only provides one subscription plan, you cannot create different tiers of access for your readers. This lack of flexibility makes it difficult to build a complex business model.

Ghost(Pro) features and tiers

Professional teams often move to Ghost(Pro) to gain more control over their infrastructure and branding. Ghost(Pro) allows you to run sites on a root domain or a subdomain using a standard CNAME record. If you choose to run your publication on a subdirectory instead of a root domain, Ghost(Pro) requires a $50 monthly addon for the Business plan to support a self-hosted reverse proxy with custom configurations. This setup accommodates teams comfortable with complex technical infrastructure.

The Business plan accommodates 10,000 members and eliminates transaction fees. All plans include advanced SEO tools, RSS feeds, and member tagging. The Business plan also contains advanced native analytics. You can use email templates to match your brand, and the signup attribution tool helps you understand where new members come from. Every plan allows you to manage members through membership and subscriptions features, which include roles like Author, Editor, Administrator, and Owner. For those needing more power, the Custom plan allows for unlimited staff users and unlimited members.

Infrastructure and AI crawler control

The decision to leave mass-market hosts also concerns the AI-crawl posture of your website. A June 11, 2026, audit of 736 companies found that 90% of measurable providers express no AI-crawler policy. Among 573 companies with readable files, only 58 show any signal for the AI era. Mass-market hosting giants like Bluehost, Wix, and WordPress.com show no AI-specific rules of any kind. I find the silence from these large providers to be a significant risk for content protection.

Only 25 companies out of 573 declare a Content-Signal to manage how AI reads or trains on content. Only 8 companies reference an llms.txt file to provide machine-readable summaries. Most of the companies that declare a policy, such as Render or Vercel, say ai-train=no to prevent training. In the crawler league, 81% of the 48 files that name any AI crawler mention GPTBot. One name, Bytespider, appears in 21 files, but every inspection shows the treatment is exclusion. Do you think your content is safe on a platform that maintains no AI-specific rules?