ProcessWire

Custom fields on every template Each template declares its own field set, so a directory listing, a product page, and an event calendar each store exactly the data they need instead of squeezing into posts with metadata workarounds. Because fields are defined per template, editors see only the inputs a content type needs.[1][2]

Fluent pages API with selectors Server-side code using the pages API with chained selectors reads almost like jQuery, keeping template logic short and reviewable for PHP developers. Selectors combine conditions, sorting, and limits in one expression, which keeps custom listings inside the API rather than in raw SQL.[1]

Page-tree content model All content is a page in one hierarchy, which maps cleanly onto navigation, sections, and archives without a separate menu layer for ordinary sites. One hierarchy keeps small and mid-size sites navigable without extra information architecture.[1]

Built-in multi-language fields Language variants are managed per field in the core workflow rather than through a translation plugin, which suits agencies shipping multilingual client sites. Field-level variants keep translations attached to the same page instead of duplicated across separate trees.[1]

Role-based access control Granular roles govern who can view, edit, and publish, so editors get a constrained workspace while developers keep full access. Administrators shape editorial permissions around their publishing workflow through the documented access system.[1]

Modules and hooks A public module directory plus a hook system extends fields, inputs, and behavior; first-party commercial Pro modules add forms, caching, and developer tooling on top of the free core. Hooks let developers intercept core events to customize behavior without patching core files.[1][2]

ProCache static delivery The optional ProCache module bypasses PHP and MySQL to serve pages at static-HTML speed, giving high-traffic pages a release valve without leaving the CMS. Because it is a paid Pro module, static delivery is an optional upgrade rather than core behavior.[1]

Self-hosted installs four ways ZIP download, GitHub checkout, Composer, and Softaculous one-click installs cover manual, version-controlled, and shared-hosting setups on ordinary PHP hosting. Softaculous covers shared hosting without shell access, while Composer fits version-controlled deployments.[1]

Agencies shipping original designs Template files render exactly the markup the designer specified, so there is no theme layer to fight when the layout is bespoke.[1]

Developers who think in APIs The selectors-based PHP API covers fetching, filtering, and relating content with little boilerplate, which keeps custom builds compact.[1]

Budget-conscious owners with technical help The core is free under MPL 2.0, hosting is commodity PHP and MySQL, and paid Pro modules are optional rather than required to run a site.[1][2]

Non-technical site owners ProcessWire's own comparison says WordPress fits people who want to put something up from a theme with no web development; ProcessWire targets the opposite workflow.[1]

Teams without PHP capacity Templates, hooks, and modules are PHP work, and the API advantage only materializes if someone on the team writes server-side code.[1][2]

Buyers wanting official SaaS There is no vendor-hosted plan; every install needs arranged hosting, updates, and backups handled by the owner or their provider.[1]