Pattern C. Headless Drupal Plus Dedicated MLM Platform.
Drupal as content via JSON:API. SaaS MLM owns operations entirely. Best for content-heavy MLMs at scale where the editorial team likes Drupal but operations need scale.
When headless fits
Three signals together. Network at $20M+ GMV with growth that has the SaaS MLM team comfortable with the operational scale. Strong Drupal editorial team that values the admin UX, content modeling, and workflow tools enough that switching to a different CMS would be a real loss. SaaS MLM platform's distributor portal can stand on its own without requiring Drupal-rendered pages mid-flow. If those three line up, headless is the cleanest pattern; if any is missing, Pattern B (Drupal Commerce front, SaaS back) is usually the better answer.
The stack
Drupal 10 with JSON:API enabled (core in D10, contrib for D9). Front-end built with Next.js, Nuxt, or SvelteKit consuming JSON:API for content reads. SaaS MLM platform (CloudMLM, Business MLM Software, or Epixel) for distributor and commission operations. Vercel, Netlify, or Cloudflare Pages for hosting the front-end. The Drupal site itself becomes a read-mostly content source that the editorial team works inside while the front-end consumes it.
Authentication
Distributors authenticate against the SaaS MLM platform; their session token is passed to JSON:API for content reads where the content is gated to authenticated distributors. Drupal becomes a read-mostly content source for the front-end, with anonymous access to public content and token-validated access to gated content.
JWT validation in JSON:API requires the JWT module (contrib) plus a small custom permission resolver that maps SaaS-issued tokens to Drupal user contexts. About 100 lines of contributed module code handles the integration.
Caveats worth knowing
Three. Image styles still useful in headless contexts; use the consumer_image_styles module to expose Drupal's image style transformations through JSON:API so the front-end gets pre-rendered responsive image variants. Search needs an external service; Algolia or Meilisearch indexed from JSON:API is the standard pattern. Drupal Search API loses much of its value in headless because the front-end doesn't render Drupal pages.
Editorial workflow stays in Drupal admin UI, which is the point of choosing headless Drupal over alternatives. Layout Builder and Paragraphs both work in headless contexts as long as the front-end is built to consume their structured output.
Why this pattern is rare
Headless Drupal MLM is the smallest segment of our directory engagements. Most networks at $20M+ GMV that consider it eventually realize that Drupal's editorial UX advantages, while real, are usually not worth the engineering complexity of headless. The teams that do choose this pattern have specific editorial needs (multilingual content, complex content workflows, strong governance requirements) that justify the additional complexity.
For most networks at that scale, the honest answer is Pattern B (Drupal Commerce front, SaaS back) or full migration off Drupal entirely. The headless pattern fills a narrow but real niche.
Vendor selection
CloudMLM Software fits the headless pattern cleanly because the JavaScript SDK is well-maintained for the Next.js or Nuxt front-ends that typically pair with headless Drupal. Business MLM Software fits when broader plan support outweighs SDK polish. Both are real choices; the demo should focus on whether the SaaS distributor portal can stand alone visually or whether the Drupal-rendered context matters more.