blogc vs Poole
A side-by-side comparison of two self-hosted blogging platforms options — licensing, setup difficulty, resource needs, and what each one replaces.
| Feature | blogc | Poole |
|---|---|---|
| Deploy effort | Read-the-docs project | Read-the-docs project |
| Health score | 6 · At risk | 0 · At risk |
| Status | Actively maintained | Archived |
| Category | Blogging Platforms | Blogging Platforms |
| License | BSD-3-Clause | MIT |
| Language | C | Python |
| Setup difficulty | Medium | Medium |
| Min. RAM | 32 MB | 64 MB |
| Deployment | bare-metal, source | source, bare-metal |
| GitHub stars | ★ 192 | ★ 31 |
| First released | 2015 | 2009 |
| Replaces | Jekyll, Hugo | Jekyll |
What are blogc and Poole?
blogc
blogc is a blog compiler written in C that builds static websites from template and source files. It is paired with blogc-make to handle building entire blogs with feeds and pagination.
- Fast static site compiler in C
- Atom feed and pagination support
- Minimal dependencies
- Template-based rendering
Poole
Poole is a markup-agnostic, single-file static website generator written in Python that keeps the build process deliberately tiny. It is suited for small personal sites and blogs where minimalism is preferred.
- Single-file generator
- Markup-agnostic
- Embedded Python in pages
- Tiny footprint
blogc vs Poole: key differences
The biggest difference is maintenance: Poole's repository is archived and no longer developed, while blogc is actively maintained. Blogc is written in C, while Poole is built with Python. Licensing differs — BSD-3-Clause for blogc versus MIT for Poole. Blogc is the lighter option, starting around 32 MB of RAM against 64 MB for Poole. Poole is the more established project (first released 2009), while blogc arrived in 2015. Blogc has the considerably larger community, at 192 GitHub stars versus 31.
Why pick each one
Choose blogc if…
- Released under the BSD-3-Clause license
- Written in C
- Tiny footprint — runs in 32 MB RAM
Choose Poole if…
- Released under the MIT license
- Written in Python
- Tiny footprint — runs in 64 MB RAM
Frequently asked questions
Is blogc or Poole better?
Neither is universally better. blogc has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are blogc and Poole free and open-source?
Yes. blogc is licensed under BSD-3-Clause and Poole under MIT. Both can be self-hosted at no software cost.
Can I run blogc and Poole with Docker?
blogc: check the project docs for container support. Poole: check the project docs for container support.
Which is lighter on resources, blogc or Poole?
blogc has the smaller minimum footprint at 32 MB of RAM, compared to about 64 MB for Poole. Real-world usage depends on library size, user count, and enabled features.