I am evaluating a Ghost architecture and would like to confirm whether this setup is technically sound and whether it introduces any limitations, especially around analytics and member tracking.
The plan is to run Ghost behind a reverse proxy and use it primarily as a headless CMS, membership backend, and newsletter system, while all public rendering is handled by a custom frontend.
Ghost would remain responsible for memberships, subscriptions, Stripe billing, newsletters, email delivery, redirect management, and editorial workflows. The custom frontend would render all pages and posts using the Content API.
Here is an ongoing list of routes that need to be proxied to ghost
-
/ghost/*ghost dashboard, admin api -
/members/api/*membership functions -
/r/*redirects -
/.ghost/analytics/*analytics -
portal.jsis included in the custom frontend to support membership flows and can be replaced later -
/webmention/*W3C Webmentions -
/
content/*Media assets
The motivation for this setup is to allow server-side integration of additional data streams and services, like custom post data and custom page types and to provide full control over how content blocks produced by the Ghost editor are transformed and rendered. The frontend will combine Ghost content with external data sources and apply custom rendering logic to editor output.
I would love to hear your thoughts!