Concrete CMS vs ProcessWire

Concrete CMS and ProcessWire both have free, self-hostable open-source cores, but Concrete CMS additionally sells paid hosted plans from $4.99/month (Starter)…

Best for Concrete CMS: Concrete CMS suits teams that want in-context, live-page WYSIWYG editing plus compliance-oriented hosting (stated SOC 2/HIPAA options) without managing their own infrastructure.
Best for ProcessWire: ProcessWire suits developers who want a minimal, API-driven CMS core with built-in multi-language support and a hierarchical page tree, self-hosted with no ongoing license fee.

At a Glance

 Concrete CMSProcessWire
Primary categoryCMSCMS
RatingNot documentedNot documented
Pricing modelFreemium (free open-source core, paid managed hosting)Free and open source (MPL 2.0 license); optional paid Pro modules and hosting-related add-ons
Starting priceFree (self-hosted); managed hosting from $4.99/monthFree
Free planYesYes
Free trialNot documentedNot documented
PlatformsWebNot documented
Team collaborationNot documentedNot documented
AI featuresNot documentedNot documented
Public APIYesYes

Key Differences

First-Party Hosted Plans

Concrete CMS: Concrete CMS sells paid hosted plans starting at $4.99/month (Starter: 1 editor, 10,000 monthly page views, 2GB storage), up to $19/month (Business) and a custom-quoted Custom SLA tier.

ProcessWire: ProcessWire's facts document no pricing plans at all — no first-party hosted product, meaning self-hosting is the primary deployment path.

Teams without in-house hosting expertise may prefer a vendor offering managed plans over configuring self-hosted infrastructure from scratch.

Editing Philosophy

Concrete CMS: Concrete CMS's flagship feature is in-context WYSIWYG editing directly on the live page.

ProcessWire: ProcessWire is explicitly API-driven, giving developers a simple, minimal-code API for accessing and manipulating content as its headline design principle rather than a live-page editing UI.

In-context editing suits non-technical content editors, while an API-first core suits developers building custom front ends.

Compliance-Oriented Hosting

Concrete CMS: Concrete CMS states its hosting can offer SOC 2 and HIPAA-compliant options and describes its security as ISO 27001 certified.

ProcessWire: ProcessWire's facts don't document any compliance certifications or hosted-plan compliance options.

Regulated industries (healthcare, finance) often require documented compliance certifications from their hosting vendor.

Permission Granularity

Concrete CMS: Concrete CMS offers role-based permissions down to individual content blocks.

ProcessWire: ProcessWire documents a granular role-based access control system controlling what editors and users can do.

Block-level permission granularity can matter for large sites with many contributors editing shared pages.

Project Maturity & Lineage

Concrete CMS: Concrete CMS traces back to 2003 (originally released as concrete5), giving it a longer track record.

ProcessWire: ProcessWire launched in 2010, with a smaller GitHub footprint (about 1.1k stars) than mainstream CMS competitors.

Project age can correlate with ecosystem maturity, though smaller projects can still be well-maintained and stable.

Feature-by-Feature

Editing & Content Model

FeatureConcrete CMSProcessWire
In-context/live-page WYSIWYG editingAvailableNot documented
API-driven content access as core designNot documentedAvailable
Hierarchical, unlimited-depth page treeNot documentedAvailable
Version history & change logsAvailableNot documented
Built-in multi-language supportNot documentedAvailable

Permissions & Compliance

FeatureConcrete CMSProcessWire
Role-based permissionsAvailableAvailable
Built-in approval workflowsAvailableNot documented
SOC 2 / HIPAA-compliant hosting optionsAvailableNot documented
ISO 27001 security certification claimAvailableNot documented

Cost & Hosting

FeatureConcrete CMSProcessWire
Free self-hosted coreAvailableAvailable
First-party paid hosted plansAvailableNot documented
Optional paid add-on modulesAvailableAvailable
Custom self-managed enterprise deployment (CI/CD)AvailableNot documented

Pricing Compared

Starting price reflects the lowest paid tier, not the full cost for every team size or usage level.

Concrete CMS

Open Source (Self-Hosted) — Free N/A
Starter Hosting — $4.99/month Monthly
Business Hosting — $19/month Monthly

ProcessWire

Core CMS/Framework — Free N/A
Pro Modules (optional) — Paid, per module One-time or per-module purchase

Pros & Cons

Concrete CMS

Pros

  • Free and open source under the permissive MIT license
  • Strong built-in permissions and page version history without extra plugins
  • In-context editing is approachable for non-technical content editors
  • Active marketplace and optional managed hosting for teams that want it

Cons

  • Smaller plugin, theme, and developer ecosystem than WordPress
  • Managed hosting adds recurring cost beyond the free open-source core
  • Sites still on the legacy 5.x (concrete5) branch require migration to stay supported
  • Fewer third-party integrations available compared to larger CMS platforms

ProcessWire

Pros

  • Completely free and open source with no recurring platform fee
  • Highly flexible, developer-friendly API well suited to custom-built websites
  • Native multi-language support built into the core
  • Lightweight core keeps sites fast and reduces bloat
  • Established, active developer community and module ecosystem

Cons

  • Requires PHP development knowledge; not designed for non-technical end users
  • Smaller ecosystem and talent pool compared to mainstream CMS platforms like WordPress
  • No official company, support contracts, or SLAs behind the project
  • Self-hosting means users are responsible for their own hosting, backups, and security updates
  • Fewer pre-built themes or templates compared to more mainstream CMS platforms

Use Cases

Choose Concrete CMS: Concrete CMS suits teams that want in-context, live-page WYSIWYG editing plus compliance-oriented hosting (stated SOC 2/HIPAA options) without managing their own infrastructure.
Choose ProcessWire: ProcessWire suits developers who want a minimal, API-driven CMS core with built-in multi-language support and a hierarchical page tree, self-hosted with no ongoing license fee.
Need both: There's no realistic scenario for running both on one site — a team would choose Concrete CMS if it wants managed, compliance-oriented hosting, or ProcessWire if it wants full self-hosted control over an API-driven core, but not both for the same project.

Concrete CMS

  • Government and Institutional Websites — Organizations needing granular, role-based editorial permissions use Concrete CMS's built-in access controls.
  • Small Business and Agency Sites — In-context editing lets non-technical staff update site content without training on a separate admin panel.

ProcessWire

  • Custom-built business websites — Agencies and freelancers building fully custom, non-templated websites where design and data structure need full flexibility.
  • Multi-language content sites — Organizations needing native multi-language content management without relying on a heavy third-party plugin.
  • Developer-controlled content APIs — Projects that need a lightweight, API-driven backend to power custom front ends or headless implementations.

Frequently Asked Questions

Are both free to self-host?

Yes. Concrete CMS's MIT-licensed core and ProcessWire's mainly MPL 2.0-licensed core can both be self-hosted for free.

Does either offer first-party managed hosting?

Concrete CMS sells hosted plans starting at $4.99/month (Starter). ProcessWire's facts document no first-party hosted plans, only self-hosting.

Which is more compliance-oriented out of the box?

Concrete CMS states SOC 2 and HIPAA-compliant hosting options and ISO 27001-certified security. ProcessWire's facts don't document comparable compliance certifications.

How do their editing philosophies differ?

Concrete CMS emphasizes in-context editing directly on the live page for non-technical editors. ProcessWire is built around a developer-facing API for minimal-code content access.

Which has been around longer?

Concrete CMS traces to 2003 (originally released as concrete5). ProcessWire was founded in 2010.

Does either include paid optional modules beyond the free core?

Yes for both. Concrete CMS layers compliance and scale into paid hosted plans, while ProcessWire sells specific Pro Shop modules like ProCache, Form Builder, and PAGEGRID Page Builder.

Read the full Concrete CMS review · Read the full ProcessWire review