Cogny Cloud · Ghost

Members + revenue, in one weekly digest.

Cogny reads Ghost + Stripe through MCPs, finds churn risks and post-tier shifts, and creates a ticket per action. Approve in tickets — Cogny ships the structural updates through the Ghost MCP.

❯ book a Cloud demo see how it replaces the manual flow →

❯

cogny --replaces

FLOW

Same outcome. Two very different processes.

How you do it today

Ghost dashboard tells you opens. Stripe tells you revenue.
Free-to-paid conversion measured manually, occasionally.
Churn investigations only after revenue dips.
Post tag / visibility tweaks done by hand in Ghost.

How Cogny Cloud does it

Cogny connects to Ghost + Stripe via MCP — one-time.
Pulls member + post + revenue reports on a schedule.
Finds insights: churn risks, post-tier shifts, decaying tiers.
Creates a ticket per proposed action.
You approve in tickets.
Cogny ships the approved structural change through the Ghost Admin API — tags, scheduling, visibility, member tier moves.
Watches whether the action saved subscribers — learns over time.

❯

cogny --tickets

read + write

Cogny creates tickets AND executes the approved ones through the MCP. Each insight becomes one ticket — here are the kinds Cogny creates from Ghost:

Churn-risk ticketPaid members who stopped engaging — outreach + suggested tier move.

Post-tag ticketUpdate tags, scheduling or visibility on a post or tier.

Cohort-shift ticketWhen a cohort's retention drops vs your historical curve.

ExecutionCogny can update tags, scheduling, post visibility and member tier moves through the Ghost Admin API after approval. Theme/code changes flow through Cogny Code as PRs. Cogny does not write or rewrite post content.

LearnsCogny tracks whether tier-move or outreach tickets actually saved subscribers and adapts which signals it surfaces — irrelevant ones drop, the high-signal ones become defaults.

❯

cogny --reads

DATA

The reports Cogny pulls on schedule for Ghost insights

GhostMembers, Posts, Tags, Tiers

StripeMRR, churn

Site analyticsGA4 / Plausible

EmailWeekly publisher digest

❯

cogny --book

DEMO

Tell us your use case. Then book a 15-min Cloud demo.

❯

cogny --faq

ASK

The questions we usually get on the demo call

Does Cogny replace Ghost?

No. Cogny connects to Ghost and adds an AI analyst on top — you keep using Ghost for everything you do today.

Does Cogny make changes automatically?

No — Cogny creates a ticket for every proposed action, you approve in tickets, then Cogny executes the approved ticket through the Ghost MCP. Nothing ships without you signing off.

Does Cogny write copy or creative?

No. Cogny does not write ad copy, email bodies, post content, image creative or rewrite existing copy. Cogny’s execution is limited to structural changes — segments, tags, metadata, internal links, redirects, scheduling assets you’ve already drafted, status changes (pause/resume/archive), and code-level PRs via Cogny Code.

Does Cogny actually get smarter over time?

Yes. Every approval and rejection is a signal. Cogny tracks the outcome of each executed ticket (did the deal close, did the ranking recover, did the segment lift revenue) and tunes its proposals to your business — so noisy or irrelevant tickets fall off and the high-signal ones become the default.

❯