APIs · head to head
Payload CMS vs Split

Payload CMS
APIs
Modern TypeScript-first headless CMS with REST and GraphQL APIs
- From
- Free
- Free plan
- Yes

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- Payload CMS is a modern, type-safe headless CMS.
- Payload CMS is free; Split prices on request.
- Only Payload CMS lists REST API; only Split lists feature flags with targeting.
- Where Payload CMS falls short: payload is a Next.js fullstack framework and installs into a Next.js app, so it is not framework-agnostic.
- Prices and features on this page were last checked on 20 November 2026.
How do Payload CMS and Split differ?
Payload CMS and Split differ on starting price (Free against On request), pricing model (Open-source against Quote) and free tier (Yes against No). Only the attributes on which Payload CMS and Split actually diverge.
| Attribute | Payload CMS | Split |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | Open-source | Quote |
| Free tier | Yes | No |
| Platforms | API, Self-hosted | Web, API, iOS, Android, Windows |
| Category | APIs | Testing |
Not yet recorded: founded for Split.
Which features does each one have?
They share no listed features; 9 appear only for Payload CMS and 8 only for Split. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Payload CMS
- REST API
- GraphQL API
- Versioning
- TypeScript
- Node.js
- Databases
- Custom plugins
- Node.js support
Only in Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform integration
What is each one used for?
Payload CMS is most often brought in for running a headless, TypeScript-configured CMS you self-host. The jobs each tool is most often brought in to do.
Payload CMS
- Running a headless, TypeScript-configured CMS you self-hostnot Split
- Generating an admin panel plus REST and GraphQL APIs from a code confignot Split
- Digital asset management and headless e-commerce back endsnot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Payload CMS
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Payload CMS
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Payload CMS
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Payload CMS
Where do Payload CMS and Split fall short?
Payload CMS's most cited limit: payload is a Next.js fullstack framework and installs into a Next.js app, so it is not framework-agnostic. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Payload CMS
- Payload is a Next.js fullstack framework and installs into a Next.js app, so it is not framework-agnostic
- Database support is limited to MongoDB and Postgres
- SSO is an Enterprise-only feature
- Publishing workflows, the visual editor, static A/B testing and AI auto-embedding are listed as Enterprise features
- Enterprise is sold through a Schedule a Demo form with no published price
- Free support is through a Discord community rather than a vendor support channel
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do Payload CMS and Split cost?
Payload CMS is free to use; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
Payload CMS
Free- Open SourceFree
- Full PayloadCMS
- Self-hosted
- Community support
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
Which should you pick?
Choose Payload CMS if
- You need rest api.
- You want to start without paying.
- You work on API, Self-hosted.
- You also want graphql api.
Choose Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is Payload CMS or Split better?
- Neither clearly leads. Payload CMS starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Payload CMS or Split?
- Payload CMS has a free tier; the other does not. Paid plans start at Free for Payload CMS and On request for Split.
- Does Payload CMS or Split run on more platforms?
- Payload CMS runs on API, Self-hosted. Split runs on Web, API, iOS, Android, Windows.
- Can I use Payload CMS for free?
- Yes. Payload CMS has a free tier, so you can try it without paying. Split starts at On request.
- What is Payload CMS best used for?
- Payload CMS is most often used for running a headless, typescript-configured cms you self-host, generating an admin panel plus rest and graphql apis from a code config, digital asset management and headless e-commerce back ends. Of those, running a headless, typescript-configured cms you self-host and generating an admin panel plus rest and graphql apis from a code config are not what Split is typically brought in for.
- What can Payload CMS do that Split cannot?
- Payload CMS covers REST API, GraphQL API, Versioning, TypeScript. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
Answered from the vendors’ own pages
Payload CMS: How much does Payload CMS cost?
Payload CMS does not publish detailed pricing information on its main website. The site indicates a divide between self-hosted open-source development solutions and premium features, but specific costs and billing periods are not listed.
SourceSplit: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
Payload CMS: Does Payload CMS offer an open-source option?
Yes, Payload offers an open-source option for self-hosted development solutions, with additional enterprise features available.
SourceSplit: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
Payload CMS: How do I learn about Payload CMS pricing?
Users can visit the /get-started page for pricing details or schedule a demo through the website to discuss pricing and enterprise options.
SourceSplit: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
Split: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
More on Payload CMS
Other head to heads
- Payload CMS vs Strapi
- Payload CMS vs Sanity
- Payload CMS vs KeystoneJS
- Payload CMS vs Directus
- Payload CMS vs PocketBase
- Payload CMS vs Prisma
- Payload CMS vs Parse Server
- Payload CMS vs GraphQL Apollo
- Payload CMS vs 10x Banking
- Payload CMS vs Gravitee
- Payload CMS vs Thunder Client
- Payload CMS vs Formance
- Payload CMS vs Marqeta
- Payload CMS vs Apidog
- Payload CMS vs Microsoft Azure API Management
- Payload CMS vs Column
- Payload CMS vs Hoppscotch
- Payload CMS vs Salt Edge
- Payload CMS vs GrowthBook
- Payload CMS vs Kameleoon
- Payload CMS vs Eppo
- Payload CMS vs Katalon
- Payload CMS vs Selenium
- Payload CMS vs Sauce Labs
- Payload CMS vs TestRail
- Payload CMS vs Applitools
- Payload CMS vs CloudBees Smart Tests
- Payload CMS vs QA Wolf
- Payload CMS vs CircleCI
- Payload CMS vs BrowserStack
- Payload CMS vs BugHerd
- Payload CMS vs SoapUI
- Payload CMS vs Playwright
- Payload CMS vs GitHub Actions
- Payload CMS vs Cypress
- Payload CMS vs Appium
- Split vs Strapi
- Split vs Sanity
- Split vs KeystoneJS
- Split vs Directus
- Split vs PocketBase
- Split vs Prisma
- Split vs Parse Server
- Split vs GraphQL Apollo
- Split vs 10x Banking
- Split vs Gravitee
- Split vs Thunder Client
- Split vs Formance
- Split vs Marqeta
- Split vs Apidog
- Split vs Microsoft Azure API Management
- Split vs Column
- Split vs Hoppscotch
- Split vs Salt Edge
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
