Ghost Hosting

Ghost CLI - the official installation tool - supports Ubuntu 20.04, 22.04, and 24.04 LTS only. This is a Ghost requirement, not a Bitfoo restriction. Other Linux distributions (Debian, AlmaLinux, Rocky Linux, CentOS) are not supported by Ghost CLI and will produce errors during installation. When you order your VPS, select Ubuntu 22.04 or 24.04 LTS. If you order with a different distribution and want to switch, you can reinstall the OS from the Bitfoo client panel at no charge.

Ghost's official documentation lists 1GB RAM as the minimum. In practice, Ghost and MySQL together use 400-700MB at rest - which leaves limited headroom on a 1GB server when traffic spikes or newsletter sends trigger additional database and rendering activity. VPS-1 works for low-traffic blogs or testing environments. For a publication with a regular audience or an active member list, VPS-2's 2GB allocation gives you a noticeably more stable environment. If you're running multiple Ghost instances on one server, size up accordingly.

Ghost's newsletter and transactional email (welcome emails, member confirmations, password resets) require an external email provider. Ghost has native Mailgun integration - connect your Mailgun account in Ghost's admin settings under Email Newsletter, and Ghost routes all outbound email through Mailgun. SMTP credentials from other providers (Postmark, SendGrid, AWS SES) can also be used via Ghost's custom SMTP settings.

Yes. Ghost's paid membership and subscription features (paid tiers, member-only content, one-time payments) connect to Stripe through your Ghost admin settings. There is no hosting-level configuration required - you connect your Stripe account in the Ghost admin panel and Stripe handles payment processing directly. Self-hosted Ghost has access to the same membership features as Ghost(Pro). The only difference is that you manage your own infrastructure instead of paying Ghost to manage it for you.

Yes. Ghost provides a built-in export tool in the admin panel that exports your entire publication - posts, pages, members, tags, and settings - as a JSON file. On your new self-hosted instance, import that file through the Ghost admin panel's import tool. Member email addresses migrate with your content; existing paid subscribers would need to be reconnected to Stripe on the new instance. Ghost's official documentation covers the migration process in detail. DNS propagation is the main timing consideration - point your domain at your VPS after confirming the import is complete.

Yes. Ghost CLI supports multiple instances on a single server. Each publication runs on a separate internal port; Nginx routes traffic to the correct instance based on the domain name. Use ghost install for the first publication and ghost install --port [port] for subsequent ones. ghost ls shows all instances and their status. The practical limit is RAM - each Ghost instance plus a shared MySQL server adds to your total memory footprint. VPS-4 handles four to six Ghost instances comfortably depending on traffic levels.

VPS-1 is adequate for a low-traffic blog or a site you're setting up to test before migrating an existing publication. VPS-2 is the recommended starting point for most Ghost publications - it gives Ghost and MySQL enough combined RAM to handle regular traffic and newsletter sends without running close to limits. VPS-4 suits high-traffic publications, large member lists that generate significant database activity during sends, or servers running two to four Ghost instances. VPS-6 suits agencies or developers running many Ghost publications from one server. If you're migrating from Ghost(Pro) and unsure of your traffic profile, start with VPS-2 - you can upgrade without migrating your data.