Can Ghost Pro be vibe coded?
Managed Ghost hosting for blogs, newsletters, and paid memberships
Because Ghost is open source, the core publishing/newsletter/membership product can be self-hosted; the cost is ops, email setup, and maintenance.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Self-host Ghost, configure theme/domain/email, enable memberships/newsletters, and maintain backups/upgrades.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- managed hosting
- upgrades
- backups
- email delivery setup
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Why people still pay
They pay because publishing should not turn into server administration.
Reliability at the vendor's scale is an operations problem, not a prompt.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Ghost Pro
Context
**Ghost Pro** — Managed Ghost hosting for blogs, newsletters, and paid memberships. It currently costs $35/mo.
Because Ghost is open source, the core publishing/newsletter/membership product can be self-hosted; the cost is ops, email setup, and maintenance.
This brief describes a focused, single-operator replacement for the part of Ghost Pro that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Self-host Ghost, configure theme/domain/email, enable memberships/newsletters, and maintain backups/upgrades.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
VPS/Docker.
Domain/DNS.
Transactional/email provider.
Backups.
Theme/configuration.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build me a self-hosted Ghost site to replace Ghost Pro. Requirements:
Do not write a CMS. Deploy the open-source Ghost itself on my VPS with
Docker Compose: ghost and MySQL 8 containers, named volumes for content and
the database.
Caddy in front for HTTPS on my domain with automatic certificates; Ghost
bound to localhost so only Caddy is exposed.
Newsletter and transactional email via Mailgun, creds flowing from .env into
the compose file, plus a checklist of the SPF/DKIM/DMARC DNS records.
Memberships and paid subscriptions wired to Stripe keys in .env, test mode
first.
Nightly backup cron: mysqldump plus a tar of the content volume into
./backups/, keep 14, with a written restore procedure tested once for real.
An update.sh that pulls new images and restarts, with a note to read Ghost
release notes before major-version jumps.
My content on my server; no third-party analytics added.
Out of scope: building a custom theme from scratch (start from the default
theme) and any custom blog engine code.
README: DNS records, first-run admin setup, and the honest warning that
upgrades and email deliverability are now my job, that is the trade.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Managed hosting.
Upgrades.
Backups.
Email delivery setup.
Reliability at the vendor's scale is an operations problem, not a prompt.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Ghost](https://github.com/TryGhost/Ghost) — The product's own open-source publishing platform
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/ghost-pro
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Open-source prior art
Before you start
Can Ghost Pro be vibe coded?
Yes, for personal use. Because Ghost is open source, the core publishing/newsletter/membership product can be self-hosted; the cost is ops, email setup, and maintenance.
What can an AI coding agent reproduce from Ghost Pro?
Self-host Ghost, configure theme/domain/email, enable memberships/newsletters, and maintain backups/upgrades. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Ghost Pro replacement still be missing?
managed hosting; upgrades; backups; email delivery setup; Reliability at the vendor's scale is an operations problem, not a prompt.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Ghost Pro alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.