Strapi, Payload or Directus: Choosing a Headless CMS
Three open-source headless CMS options compared as a business owner: content editing, three-year cost, CRM and store integrations and the limits of each.
Short answer: for business you pick not “the best CMS” but the one that is cheapest to live with: Strapi — when a familiar admin panel for the marketer and a big community matter (a contractor is easier to find); Payload — when the site and the logic live in one TypeScript codebase and version control of everything, fields included, is valued; Directus — when your data already sits in SQL (warehouse, CRM, price list) and you need a CMS “over the database”, not “instead of it”. All three are open source: no license fee, no vendor lock-in; the choice is about architecture and people.
Headless CMS for an owner, without jargon
A regular site = the shop window and the warehouse in one room. Headless = the “warehouse” (the content base: texts, products, images) separate, the “window” (what the client sees) separate, connected by a data pipe. Benefits: the window loads fast, marketers edit content, one warehouse feeds the site, the app and the chatbot. Cost: you need an engineer to assemble the pair — once.
Why business looks at headless at all
Three typical pains WordPress and builders stop helping with:
- Speed as money. A statically/SSR-rendered storefront loads several times faster than a “monolith” with a pile of plugins — and every extra second costs conversion (how site speed affects revenue).
- Content edited in the wrong place. Marketers need comfortable fields, previews, versions — not “safe mode” and the fear of breaking the site.
- One content, many channels. Site, mobile app, chatbot, marketplace export: headless serves data through an API to all at once.
Three systems: characters, not feature lists
| Criterion | Strapi | Payload | Directus |
|---|---|---|---|
| License / price | open source (MIT), cloud paid | open source (MIT), cloud paid | open source (GPL/BSL), cloud paid |
| What the marketer sees | classic “content library” admin | admin out of the box, lives in the same project | “data as tables” + entities over SQL |
| Strengths | plugins, community, easy contractor search | one TypeScript codebase: site + data model + roles | sits on your existing SQL base, API out of the box |
| Typical scenario | corporate site, blog, catalogue | product/SaaS where frontend and backend are one team | ERP/warehouse integrations, data already in a DB |
| Weak spot | careless customisation → a settings zoo | needs a strong TypeScript developer | needs SQL culture: uncomfortable without database understanding |
| Hiring market (Ukraine/outsource) | largest | growing (close to the React market) | medium, closer to data specialists |
Selection criteria from an owner, not a programmer
1. Who edits content and how often. Five landing blocks once a week — any of the three works; a daily catalogue with prices and stock — count the ergonomics of bulk edits and import (Directus feels at home here).
2. What you already have with data. A price list in 1C, stock in SQL — that is an argument for Directus: it “puts on” an admin and API over the existing database instead of ferrying data into a new one. Lots of content, no database — Strapi/Payload.
3. Who maintains it. Headless is a sober choice when you have (or hire) a technician on retainer. The mistake is “do headless and forget”. In practice: 2–6 support hours a month plus development.
4. Staffing risk. Open source means no vendor lock-in but stack lock-in. Strapi is easier to hand to a new contractor — more materials and specialists. Payload wins when one team builds site and CMS in one repository: changing a field = code change with review; nothing can be “broken by an administrator”.
5. Ecosystem for store and leads. Check concrete things: how payment connects, how leads reach the CRM (site + CRM + 1C integration), multi-language, editor roles. All three can do it through the data model — the difference is only the cost of effort.
How not to be sold a choice
A good contractor answers “which CMS?” not with a name but with three questions: who edits content, where your data lives, who supports it in a year. If the answer is immediately “we build everything on X” — that choice is for their convenience, not for you. At DEXA we cost both Strapi and Payload variants by default and show the difference in a three-year estimate — same approach as for store platforms.
Cost of ownership: where the savings are
Common to all three: no license fee, hosting from ~$100–300/year for a small site (plus the database), security updates as a quarterly sprint.
The differences that matter:
- Strapi/Directus: changes often go through settings and plugins — cheaper, until deep customisation catches up with code costs.
- Payload: everything is code — any “harmless field tweak” = developer work. More expensive on small things, cheaper on serious logic (roles, funnels, product states).
Three-year ranges (our SME project experience): a headless stack costs 20–40% less than a maintained WordPress with paid plugins — provided editors change content themselves and do not call the programmer for every promotion. The line-by-line WordPress comparison: headless vs WordPress: costs over 3 years.
Checklist before the final decision
List the 10 actions your marketer performs on the site weekly — verify them by hand in each CMS’s demo admin, not on screenshots.
Ask your contractor for a “three-year project” estimate for two candidates (development + support + hosting + updates).
Check what migration looks like in reverse: can you export all content (JSON/CSV) in one evening — that is your insurance against a second “moving story”.
Ask: who supports this in a year if the current developer disappears? The answer should be about the labour market, not “we are the only ones who understand this”.
Only then sign the development contract.
FAQ
Can we just take the cloud version and stop thinking about servers?
You can: Strapi and Payload have cloud, Directus has managed. Honestly: for small business that is usually more expensive than your own VPS (from ~$99/month versus $20–40), and your data lives with the vendor. Acceptable for a start; for a site that earns, compute self-hosting.
Is headless only for big sites?
No. Headless is justified on a landing page already if you plan growth (blog, catalogue, a second country). It is not justified for a five-page brochure that will never change — a static build without a CMS is enough there.
What about SEO: do search engines “see” a site without a regular backend?
Yes — with server-side/static rendering the front receives ready HTML, indexing is no different from a regular site. SEO breaks only on “pure SPA without SSR”. Speed adds as a ranking bonus.
What it looks like in use
Strapi, Payload and Directus are three strong open-source tools; the choice between them is a choice between “an admin for the marketer”, “code for the product” and “an API over your database”. There is only one way to get it wrong: choosing by fashion instead of by your data and your people. Want a comparison for a specific project — send us your current site structure and a list of weekly content edits: in two days you get a recommendation with three-year numbers. Read also: headless CMS for business: what it is and when you need it and how to write a website brief.
corporate · Lite from $1,325 (₴55,000) · corporate · Standard from $2,145 (₴89,000) · corporate · Premium from $3,494 (₴145,000)
Need the same solution for your business?
A company website with bespoke design and motion: services, cases, team, languages and an admin panel. We build the structure around what your clients search for on Google.
- From 5 pages: services, cases, team, prices
- Lite — a custom layout without complex motion
- Standard — bespoke design, GSAP, two languages, an admin panel
Get a free website audit in 48 hours
Speed, SEO, conversion — a 12-page report with a prioritized fix plan. No obligation, no spam: we show what to improve even if you never hire us.