Ghostmain is a lightweight serverless runtime designed to host Ghost publications and admin panels without managing infrastructure. It streamlines deployment, scaling, and security, making it popular for solo publishers and editorial teams.
By combining container-based isolation with edge-optimized routing, Ghostmain reduces cold starts and keeps editorial workflows smooth. The following sections detail its architecture, integration options, and operations best practices.
| Runtime | Cold Start Time | Max Memory | Deployment Model |
|---|---|---|---|
| Ghostmain | 100–300 ms | 1024 MB | Serverless edge |
| Traditional VM | 2000–5000 ms | Custom | Self-managed |
| Container Service | 500–1000 ms | 8192 MB | Orchestrated |
| Static Site Generator | <50 ms | Limited dynamic | CDN only |
Compatibility with Ghost Editor Workflows
Publishing Pipeline Integration
Ghostmain aligns with Ghost’s editor pipeline, enabling preview deployments from local Ghost CLI. Content authors experience near-zero context switching, while editors retain full access to labs features and themes.
API Consistency
It exposes the same Content and Admin APIs as Ghost’s upstream engine, ensuring integrations built for self-hosted Ghost continue to function. Webhooks, scheduled publications, and member events remain reliably synchronized.
Operational Reliability and Monitoring
Observability Options
Built-in metrics expose invocation latency, error rates, and concurrency per publication. Teams can route logs to Datadog, New Relic, or Ghost’s native analytics without custom agents.
Failover Behavior
Ghostmain spins up redundant instances across availability zones. Health checks automatically route traffic away from unhealthy containers, maintaining publication uptime during regional disruptions.
Security and Access Controls
Sandboxed Execution
Each request runs in an isolated execution context, limiting filesystem and network exposure. Admins can define network egress rules to restrict outbound calls from publications.
Identity Federation
Single sign-on with Google, GitHub, and SAML integrates cleanly with Ghost’s membership system. Role-based access ensures only authorized contributors reach the admin panel even when runtime is public facing.
Getting Started with Ghostmain
- Connect your Ghost account via OAuth in the provider console
- Select a region close to your primary audience for lowest latency
- Enable preview deployments from Ghost CLI for safe content testing
- Configure custom domains and automatic HTTPS for each publication
- Set budget alerts and concurrency caps to control costs
FAQ
Reader questions
How does Ghostmain affect existing Ghost theme upgrades?
Themes upgrade seamlessly because the runtime mirrors the upstream engine version. You can test major releases in a dedicated preview publication before promoting them to production.
Can I use custom domains with Ghostmain without DNS changes?
Yes, you can map CNAME and A records through the provider console. Propagation typically completes within seconds, and ACM certificates are provisioned automatically for HTTPS.
What happens to draft posts during a runtime update?
Draft state persists in the managed datastore, so updates never interrupt editorial work. Editors can continue writing while background tasks handle database migrations with zero downtime.
How are billing alerts surfaced for Ghostmain services?
Consumption-based billing triggers email and in-app alerts at configurable thresholds. Teams receive early warnings before a publication reaches its monthly compute limit.