The program itself is free, but the plugins are charged by seat. How do you calculate this cost when selecting?
Open-source content management systems are free themselves, but plugins are charged per seat. How should this account be calculated when selecting? First, let's define the word 'free' clearly: it refers to the software authorization, and the hosting resources, key plugin seat licenses, and maintenance hours are not exempt. A selection guide for headless systems, such as the description of Strapi, is very typical: the core is free, but necessary plugins are charged for seat licenses, and deployment can be self-hosted or use the official cloud. When comparing, the four segments of cost should be priced separately, and then the total account should be calculated based on the number of team members and the number of sites.
Which part does 'free' refer to?
The open-source attribute of a content management system only indicates that the source code is available and no authorization fee is required for the program itself. This point is often listed separately in public comparisons: WordPress, Drupal, Joomla, Strapi, Payload, and Directus are classified as open source, while Contentful, Hygraph, Storyblok, DatoCMS, Squarespace, and Wix are classified as proprietary. When both are open-source solutions, self-hosting still requires the cost of hosting to be borne by oneself.In other words, classification solves the issue of 'can you get the source code, can you deploy it yourself', but does not solve 'how much will it take to run in total'.
At which stage will seat-based charging be blocked?
The seat fee usually goes with two things: the number of editors and the number of channels to be connected. The more people on the team, the easier it is to hit, because writing, auditing, operation, and outsourcing often occupy one seat each; some plugins are counted by sites, and when the number of sites increases in group building, the cost rises linearly. The actions to be taken at the selection stage are very specific: first, list the necessary plugin list, and confirm item by item whether the billing standard is monthly or annual, per person or per site, and which fields and processes will fail after removing the seats.
The two-way allocation of resources and working hours.
Hosting this section of the difference comes from runtime. Based on the GoLang and Iris, GORM technology stack system, memory usage can be reduced by about 80% compared to PHP class content systems, and more sites can be placed on the same server, and the host grade will naturally decline. This part of the working hours is more likely to be ignored: upgrades, backups, recovery exercises, and template changes all require personnel. Self-hosting should leave these two items, using Docker images or Baota panel and other deployment methods can standardize repeated actions and reduce the rework caused by errors.
A comparison table broken down by headcount and site number
| Cost items | Open source self-hosting | Exclusively hosted |
|---|---|---|
| Software license | Free, source code is available for self-extraction | Priced by subscription |
| Hosting resources | Priced by host slot, multi-site can be amortized | Generally, each site is billed separately |
| Plugins and extensions | Core is free, necessary plugins may be charged by seat | Most features are in the subscription tier |
| Operations labor | Upgrade, backup, and restore yourself | The platform takes on part of it |
| Multi-site management | One back-end manages multiple sites, resources are shared | Commonly, the number of sites is叠加 |
Common questions
Can the seat fee be purchased only during peak season?It depends on the license terms, most seats charged annually have limitations on discounts, and negotiation space is concentrated on the initial number of seats.
Will the content model be locked in the plugin?Need to be confirmed separately. When using custom fields to carry structured data, the field definition and data ownership must be able to be exported, otherwise replacing the plugin is equivalent to doing it all over again.
If there are many sites, should multi-site be used?There is obvious profit when websites need to share column structures, terminology, and backup strategies; it is better to deploy separately when each station operates independently.
How can a small team save the most?Calculate the total account for three years with the same口径: the host grade is determined according to the memory and concurrent requirements, the seats are determined according to the actual number of editors, the working hours are estimated according to the fixed maintenance hours per month, and then see which part can be undertaken by the platform.