Halo

Open-source website building, honestly reviewed. Tested against what it actually is, not what its marketing implies.

TL;DR

• What it is: Open-source (GPL-3.0) website builder and CMS — think Ghost or WordPress, but with a plugin-first architecture, built-in Markdown/rich text editor, and a cleaner admin console [1][2].
• Who it’s for: Developers and technical founders who want a self-hosted blog, knowledge base, or company site without WordPress complexity. Primarily adopted in Chinese-speaking markets; English community resources are thin [2].
• Cost savings: No SaaS equivalent to replace directly — Halo competes with Ghost Pro ($9–$199/mo) or managed WordPress ($5–$50/mo). Self-hosted Halo runs on a $5–10/mo VPS at unlimited scale [2][3].
• Key strength: 38,138 GitHub stars, 2.5M+ Docker pulls, 200+ releases, and a genuinely clean admin UI. The plugin ecosystem (100+ themes, marketplace plugins) is mature relative to its age [1][2].
• Key weakness: The project is Chinese-first — documentation, community forums, and the entire plugin marketplace are in Chinese. If you don’t read Chinese, you’re building on a tool whose ecosystem you can’t fully navigate [2]. GPL-3.0 license also means you can’t embed it in commercial closed-source products without GPL compliance obligations [1].

---

What is Halo

Halo (pronounced [ˈheɪloʊ]) is a Java-based open-source CMS and website builder. You get an admin console to write posts, manage pages, configure themes, install plugins, and handle users — the full stack for a content-driven website, packaged as a single Docker image [1][2].

The project is maintained by Lingxia (Shenzhen) Software, a subsidiary of FIT2Cloud — a Chinese open-source software company that also builds JumpServer (open-source bastion host), 1Panel (Linux server management), DataEase (BI tooling), and MaxKB (enterprise AI agent platform) [2]. This is not a side project — it’s a funded, commercially-backed product with a real engineering team behind it. The README lists 100+ contributors, and the project has shipped 200+ versioned releases [1][2].

The website builder pitch covers four site types: personal blogs, knowledge bases, company marketing sites, and e-commerce stores. That last one is notable — Halo’s Commercial Edition (a paid tier on top of the open-source core) includes a full online store with WeChat Pay and Alipay integration, which tells you clearly who the primary market is [3].

What makes it technically interesting is the plugin architecture. Plugins aren’t bolt-on afterthoughts — they run as independent modules that can be enabled or disabled without restarting the server. Storage backends (local disk, S3-compatible object storage), search engines, authentication methods, and even the e-commerce module are all plugins [2]. The core stays lean; capability comes from the marketplace.

---

Why people choose it

Third-party English-language reviews of Halo are nearly nonexistent. The tool is overwhelmingly discussed in Chinese forums, Chinese developer communities, and the project’s own Chinese-language BBS at bbs.halo.run. This isn’t a knock on the software — it’s accurate context that any Western buyer should weigh carefully.

From what can be determined from primary sources, the appeal lands in three areas:

Versus WordPress. WordPress carries 15+ years of accumulated complexity, PHP plugin ecosystem sprawl, and a plugin market full of abandoned or security-risky code. Halo’s plugin model is younger, smaller, and more controlled. Developers who find WordPress’s architecture dated or its admin UI cluttered report Halo as a genuinely cleaner experience [2].

Versus Ghost. Ghost is the obvious direct competitor in the “modern CMS for writers” category. Ghost is excellent but expensive on managed hosting ($9–$199/mo) and, since Ghost 5.x, heavily optimized around the newsletter/membership monetization model. Halo doesn’t push you toward any particular monetization model — it’s a general-purpose site builder. Ghost self-hosted is also free (MIT-licensed, which is more permissive than GPL-3.0), so if license flexibility matters, Ghost has the edge [2].

Versus Strapi/Payload (headless CMS). Halo is not headless by default — it ships with front-end theming built in, which is a different product philosophy. Halo does expose a RESTful API, so technically headless use is possible, but that’s not what the ecosystem is built around [2].

The 38,138 GitHub stars and 2.5M Docker pulls suggest genuine adoption at scale, not just Chinese web traffic inflating the numbers. For context, Ghost sits around 47K stars and has been around 10+ years. Halo at 38K with a much younger trajectory is legitimately noteworthy [1].

---

Features

Based on the official website and README:

Content management:

• Built-in dual-mode editor: rich text (WYSIWYG) and Markdown, with support for embedded media [2]
• Custom pages and posts with tags, categories, and custom taxonomies
• Multiple content types (blog posts, standalone pages, knowledge base articles) [2]
• Full-text search built in; extensible to external search engines via plugins [2]

Site configuration:

• Structured configuration forms — not raw YAML or PHP config files [2]
• Theme system with live preview, multi-language support, and per-theme configuration options [2]
• 100+ free themes in the official marketplace [3]

Plugin system:

• Enable/disable plugins at runtime without server restart [2]
• Plugin marketplace with both free and paid plugins [2][3]
• Extensible: SEO optimization, paid content access, AI writing assistant, Q&A chatbot — all available as plugins [3]

Infrastructure:

• RESTful API for headless or integrated use cases [2]
• Multiple storage backends: local disk + S3-compatible object storage [2]
• Authentication plugins: supports multiple login methods [2]
• Backup and restore (data portability) [2]
• Site logs and monitoring dashboard [2]
• Data migration from other platforms [2]

AI features (via plugins):

• AI writing assistant for content generation [2][3]
• AI Q&A assistant that turns a knowledge base into an interactive chatbot [2][3]
• Support for multiple AI providers/models — switchable [2]
• Halo CLI with “Skills” for AI agent integration [2]

Community vs. Pro vs. Commercial tiers:

The GPL-3.0 community edition gives you the full core: editor, plugins, themes, API, storage, backup. What the paid tiers add [3]:

Pro Edition adds:

• Mobile app (iOS/Android) for content management on the go
• AI-powered site setup wizard
• Phone number verification login
• “Full private deployment” (exact scope unclear from available docs)
• Access to paid theme/plugin marketplace including: SEO plugin, paywall/paid content plugin, AI assistant plugin, and others

Commercial Edition adds (on top of Pro):

• Full e-commerce module: product management, order handling, payment processing
• WeChat Pay and Alipay integration
• Designed specifically for Chinese merchants operating brand site + CMS + storefront as one stack [3]

Pricing for Pro and Commercial is not publicly listed on the main website — a separate third-party site (lxware.cn/halo) is referenced for detailed tier comparison, and pricing appears to require direct contact [3].

---

Pricing: SaaS vs self-hosted math

Halo Community Edition:

• Software license: $0 (GPL-3.0) [1]
• Self-hosted VPS: $5–15/mo (any Docker-capable Linux server)
• Your time for setup and maintenance

Halo Pro / Commercial Edition:

• Pricing not publicly listed; contact required [3]

Ghost Pro for comparison:

• Starter: $9/mo (500 members)
• Creator: $25/mo (1,000 members)
• Team: $50/mo (1,000 members + staff accounts)
• Business: $199/mo (10,000 members)

WordPress.com for comparison:

• Personal: $4/mo (limited plugins)
• Business: $25/mo (full plugin access)
• Commerce: $45/mo

Concrete math for a straightforward blog or company site:

If you need a blog, knowledge base, or marketing site — no e-commerce, no newsletter paywall — Halo Community Edition self-hosted covers it completely for the cost of a VPS. Ghost self-hosted is also free and more permissive license-wise. The $0 software cost only matters if you were otherwise paying for Ghost Pro or managed WordPress — at which point the annual savings are real ($108–$600/yr depending on the tier you’d be replacing).

Where the math tips in Halo’s favor versus Ghost is when you want plugins beyond Ghost’s narrow newsletter focus. Where it tips against Halo is when you need English community support, English documentation, or a non-GPL license.

---

Deployment reality check

The quickstart is a single Docker command [1]:

docker run -d --name halo -p 8090:8090 -v ~/.halo2:/root/.halo2 halohub/halo:2.22

That gives you a running instance on port 8090. For production, the README recommends deploying through 1Panel (FIT2Cloud’s own open-source Linux management panel) which handles reverse proxy, SSL certificates, upgrades, and backups as first-class operations — a notable advantage if you’re already running 1Panel [1].

What you actually need for a production deployment:

• A Linux VPS with 1GB RAM minimum (2GB recommended for multiple plugins running concurrently)
• Docker and docker-compose
• A domain and reverse proxy (Caddy or nginx) for HTTPS
• An SMTP provider if you need email notifications

A live demo is publicly available: https://demo.halocms.site with admin at https://demo.halocms.site/console (username: demo, password: P@ssw0rd123..) — you can test the actual admin UI before committing to anything [1].

What can go sideways:

The biggest friction point for Western users is not technical — it’s navigational. The plugin marketplace, the community forum (bbs.halo.run), and most of the 100+ themes are presented entirely in Chinese. If you’re a non-Chinese-speaking founder and you run into a plugin compatibility issue or need a feature that isn’t in the core, your support path is a Chinese-language forum or opening a GitHub issue and hoping for English responses.

The GPL-3.0 license is also worth reading carefully if you plan to build a commercial product on top of Halo. GPL requires that derivative works also be GPL-licensed. If you want to embed Halo in a closed-source SaaS product, you’re either GPL-compliant (meaning you open your source too) or you’re out of license compliance. Ghost’s MIT license doesn’t have this constraint [1].

Realistic time estimate for a developer: 20–40 minutes to a running instance. For a non-technical founder following a guide: 2–4 hours including domain and HTTPS setup. The demo environment means you can evaluate seriously before spending any time on infrastructure.

---

Pros and cons

Pros

• Genuinely clean admin UI. The console is modern, well-organized, and doesn’t suffer from the decade of accumulated baggage that WordPress admin carries. [2]
• 38K stars, active maintenance. 200+ releases, 100+ contributors, and a parent company (FIT2Cloud) with real infrastructure products shipping. This isn’t an abandoned hobby project [1][2].
• 2.5M Docker pulls. Whatever the community distribution looks like, the deployment scale is real [1].
• Plugin-first architecture. Hot-enable/disable without restarts is a meaningful operational improvement over WordPress-style plugin management [2].
• Live demo available. You can poke the actual admin before deploying anything [1].
• S3 storage support. Media offloading to Cloudflare R2 or similar works out of the box — an important operational concern at scale [2].
• AI integrations. Not bolted-on marketing language — the Q&A assistant and writing tools are real plugin-delivered features [2][3].
• RESTful API. Headless or hybrid setups are possible if you need content outside the default theme layer [2].

Cons

• Chinese-first ecosystem. Documentation, community, plugins, themes — all primarily Chinese. English support is thin and informal. This is the single most important factor for non-Chinese buyers [2].
• GPL-3.0 license. More restrictive than MIT or Apache. Cannot embed in closed-source commercial software without license compliance implications [1].
• Pro/Commercial pricing is opaque. No public pricing table. If you eventually need the Pro features (mobile app, AI setup wizard, paid plugin marketplace access), you’re entering a vendor conversation without benchmarks [3].
• Smaller global plugin ecosystem. The marketplace is active within the Chinese development community, but a Western developer looking for integrations with HubSpot, Intercom, or US-specific SaaS tools will find much less than in the WordPress or Ghost ecosystems.
• Java-based. Heavier runtime than Ghost (Node.js) or WordPress (PHP). Minimum RAM footprint is higher. Fine on a $10 VPS, worth knowing if you’re resource-constrained [1].
• No Trustpilot, G2, or Capterra reviews to reference. Essentially zero English-language third-party review coverage. Evaluating community sentiment requires navigating Chinese forums.

---

Who should use this / who shouldn’t

Use Halo if:

• You’re a developer who reads Chinese, or you’re comfortable with a tool whose community you can’t fully participate in.
• You want a cleaner alternative to WordPress for a blog, documentation site, or company marketing site.
• You’re already running 1Panel for server management — the integration is native.
• You want to evaluate seriously before committing: the live demo (https://demo.halocms.site) makes this low-friction.
• You need S3-compatible media storage and a RESTful API for content, and don’t want Ghost’s newsletter-centric model.

Skip it (pick Ghost instead) if:

• You want the most mature open-source CMS alternative with active English community, themes, and integrations, and a more permissive MIT license.
• You’re building newsletter/membership monetization — Ghost’s first-party tooling for this is superior.

Skip it (pick WordPress instead) if:

• You need an integration with a specific plugin or service that only exists in the WordPress ecosystem — there are ~60,000 WordPress plugins versus a few hundred Halo plugins, and the US/EU coverage gap is wide.
• Your team isn’t technical and will need widely-available managed hosting with cPanel or similar.

Skip it (use Strapi or Payload) if:

• You need a proper headless CMS with a content-type builder and no front-end opinions. Halo’s API is secondary to its theming system; headless architectures should use tools built headless-first.

Skip it entirely if:

• You’re a non-technical founder without developer support. The Chinese-language ecosystem means troubleshooting will require either technical skills or help from someone who has them.

---

Alternatives worth considering

• Ghost — the clearest direct competitor. MIT license, English-first, excellent for blogs and newsletters, managed hosting available. Ghost self-hosted is free; Ghost Pro is $9–199/mo. Better for Western users, worse for Chinese market features [1].
• WordPress — the incumbent. Largest plugin ecosystem by far, vast hosting options, heavy and old but impossible to beat on raw availability of integrations and support.
• Strapi — headless CMS, content-type builder, REST and GraphQL APIs. Right tool if you’re building a custom front-end and need Halo’s “back-end only.” MIT licensed, strong English community.
• Payload CMS — newer headless CMS built in TypeScript/Next.js. Growing community, excellent developer experience for JS teams. MIT licensed.
• Directus — headless data platform wrapping any SQL database. More flexible than Halo for complex content models, less plug-and-play for standard site types. BSL license (convert-to-hosted restrictions after revenue thresholds).
• Kirby — flat-file CMS with exceptional UI and content structure flexibility. Paid license ($99/site), no self-hosting cost concerns, but no free tier.

For a non-technical founder who just wants a self-hosted blog that looks clean and works: Ghost self-hosted is the more accessible choice. The English documentation, active forums, and MIT license make it easier to get unstuck. Halo’s advantage is if you’re specifically targeting a Chinese-speaking audience, need e-commerce features in the Commercial tier, or are already inside FIT2Cloud’s tool ecosystem (1Panel, JumpServer, etc.).

---

Bottom line

Halo is a legitimately well-built open-source CMS with real traction (38K GitHub stars, 2.5M Docker pulls) and a plugin architecture that’s cleaner than WordPress’s accumulated technical debt. The admin UI is modern, the Docker deployment is genuinely simple, and FIT2Cloud’s backing means this isn’t a project that’ll go dark next year.

But Halo is a Chinese-market product that happens to be open source — not a global community project that happens to have Chinese users. If you’re a US or EU founder evaluating it, that distinction matters in ways that aren’t obvious from the GitHub star count: the support community, the plugin marketplace, and the documentation are all primarily in Chinese. That’s not a dealbreaker if you have technical help, but it’s a recurring friction point rather than a one-time setup cost.

GPL-3.0 limits commercial embedding, Pro pricing is opaque, and English third-party reviews essentially don’t exist — which means you’re evaluating based on primary sources and the live demo rather than community wisdom. The demo (https://demo.halocms.site) is worth 20 minutes of your time. If the admin UI suits you and you don’t need deep English community support, it’s a solid self-hosted option. If you’re building in the Western ecosystem and expect to need help, Ghost will serve you better.

If deploying either is the blocker — that’s exactly what upready.dev handles. One-time setup, you own the infrastructure, no recurring bill to the platform vendor.

---

Sources

Primary sources:

1. Halo GitHub Repository — https://github.com/halo-dev/halo (38,138 stars, GPL-3.0 license, 100+ contributors)
2. Halo Official Website — https://www.halo.run
3. Halo Version Comparison (Community / Pro / Commercial) — https://www.lxware.cn/halo
4. Halo Live Demo — https://demo.halocms.site (admin: https://demo.halocms.site/console)

Note: No substantive English-language third-party reviews of Halo (halo.run) were available at the time of writing. The review above is based entirely on primary sources.