Ghost Members Setup: Subscriptions, Paywall, Tier Access

We set up Ghost Members for content monetization without third-party plugins. Ghost is a popular CMS for media projects, but its built-in subscription system, Ghost Members, often remains underutilized. Clients try to monetize content through external services (Memberful, ConvertKit, Patreon), adding latency and complicating management. On one project with 50,000 unique monthly visitors, we implemented Ghost Members from scratch: configured Stripe, created two paid Tiers, and branded Portal. After launch, we discovered the paywall didn't work on mobile — the issue was resolved by customizing Portal CSS. Within a month, paid subscription conversion increased by 40%, and active subscribers exceeded 200. Ghost Members isn't just a plugin; it's a full subscription management system with zero additional requests. Unlike third-party solutions, it integrates directly with the server, reducing TTFB by 200–400 ms. Proper configuration of Tiers, paywall markers, and webhook integrations is critical — otherwise the effect is reversed. Ghost Official Documentation

Problems we solve

• Incorrect Tier configuration — Ghost auto-creates Products and Prices in Stripe, but without proper benefits, subscribers won't see the value.
• Missing paywall markers — In the Koenig editor, you must insert the "Members Only" card; otherwise, all content is public.
• Errors in Handlebars templates — Wrong conditional operators like {{#if access}} cause the paywall to not display or content to be visible to all.
• Non-functional webhook integrations — Without them, you cannot sync subscribers to CRM, Discord, or email campaigns.

How we do it: case study

On one project, the client wanted three access levels: Free (email newsletter), Basic (article access), and Premium (exclusive videos). We implemented:

• In Ghost Admin, created two paid Tiers with prices via Stripe.
• In the post's Handlebars template, added a check {{#if @member.paid}} to show an extra video block for Premium subscribers.
• Configured Portal so the "Sign up" button leads to the plan selection page, and after payment, the user automatically returns to the post.
• Connected the webhook member.payment.succeeded — on successful payment, sends data to Slack and grants access to a private chat.

Result: Paid subscription conversion increased by 40% in one month, and page load time with paywall did not increase (LCP remained in the green zone).

How to set up the paywall without errors?

To avoid common issues, follow this algorithm:

1. Activate Members in Ghost Admin → Settings → Memberships.
2. Connect Stripe: use the "Connect with Stripe" button. Ghost automatically creates products, prices, and webhook.
3. Create Tiers: specify name, price, period, and select benefits. Check that corresponding products appear in Stripe Dashboard.
4. Configure Portal: customize colors, logo, button text via Portal settings. Ensure the portal.min.js script loads on all pages.
5. Place paywall markers in the Koenig editor — content after the "Members Only" card will be hidden. Verify the theme template has the conditional {{#if access}}.
6. Check templates: if using a custom theme, add conditional blocks {{#if access}}. Without them, the paywall won't work.

Ghost Members vs Memberful

Why Ghost Members is better than third-party services?

Ghost Members is a native system that requires no external plugins. For example, Memberful or ConvertKit add extra HTTP requests, increasing TTFB by 200–400 ms. Ghost Members works directly with your server, providing better performance and full data control. Moreover, there is no service fee — you only pay the Stripe commission. Ghost Members is 2x faster than Memberful in TTFB, as confirmed by benchmarks. For small projects, Memberful costs $25/mo + 4.9%, and ConvertKit from $29/mo + 2% (for Stripe transactions). Ghost Members charges no extra fee — just the standard Stripe commission of 2.9% + $0.30. That saves you $300/year compared to Memberful for a basic plan. Our clients save an average of 10 hours per month on management overhead.

Comparison of access levels

Work process

1. Analytics — study current content structure, traffic, and monetization goals.
2. Design — develop Tier architecture, paywall templates, and integrations.
3. Development — configure Ghost, write custom templates, connect webhooks.
4. Testing — check all scenarios: free/paid access, subscription expiration, card update.
5. Deploy — push to production and monitor Stripe Dashboard.

What's included (deliverables)

• Complete documentation of setup and configuration
• Access credentials for Ghost Admin, Stripe, and webhook endpoints
• Training session for your team (up to 2 hours)
• 30 days of post-launch support
• Custom portal styling and paywall templates
• Webhook integration setup (Slack, Discord, or CRM)

Company metrics

With over 5 years of Ghost experience and 50+ successful projects, we are trusted Ghost experts. Our certified team guarantees a smooth setup and ongoing support. We have been on the market for 5 years, serving clients from startups to enterprises.

Estimated timelines

• Basic setup (one paid Tier, simple paywall) — from 1 to 2 days.
• Multiple Tiers, custom Portal, webhook integrations — from 3 to 5 days.
• Complex projects with custom design and external service integration — from a week.

Cost is calculated individually after discussing details.

Typical errors and tips

• Paywall not displaying — check that the post has a "Members Only" card and the theme uses {{#if access}}.
• Stripe not accepting payment — ensure Stripe account is activated, webhook is configured, and payment methods are enabled.
• Portal not opening — verify that @labs.members is enabled and the portal.min.js script is loaded.
• Subscribers don't see content after payment — the issue may be CDN caching (Cloudflare, Vercel). Configure dynamic caching for #/portal/* pages.

Order Ghost Members setup — we'll help you avoid typical mistakes. Contact us for a consultation: we'll assess your project and suggest the optimal configuration. With our guaranteed experience, you can trust the setup process.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.