Softwr

APIs · head to head

Payload CMS vs Unit

Payload CMS logo

Payload CMS

APIs

Modern TypeScript-first headless CMS with REST and GraphQL APIs

From
Free
Rated
-
Unit logo

Unit

APIs

Banking as a service platform for embedding deposit accounts, cards and payments, with a sponsor bank behind it

From
On request
Rated
-

The short version

  • Only Payload CMS has a free tier, so it costs nothing to try first.
  • Each has a real cost: Payload CMS payload is a Next.js fullstack framework and installs into a Next.js app, so it is not framework-agnostic; Unit your product depends on a sponsor bank you do not contract with directly, and 2024 showed what that means: Thread Bank received an FDIC enforcement action naming its banking as a service programmes and Blue Ridge Bank went under an OCC consent order and offboarded fintech partners.
  • They diverge on capability: Payload CMS covers REST API, Unit covers Deposit accounts.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Payload CMS and Unit actually diverge.

Attributes where Payload CMS and Unit differ
AttributePayload CMSUnit
Starting priceFreeOn request
Pricing modelopen-sourcequote
Free tierYesNo
PlatformsNode.js, Self-hostedWeb, iOS, Android
Founded2020Unknown

Identical on both: user rating (Not yet rated), category (APIs).

What each one covers

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 Unit

  • Deposit accounts
  • Card issuing
  • Payments
  • White label components
  • Compliance operations
  • Lending
  • Programme reporting
  • Sandbox

What people use each for

The jobs each tool is most often brought in to do.

Payload CMS

  • Running a headless, TypeScript-configured CMS you self-hostnot Unit
  • Generating an admin panel plus REST and GraphQL APIs from a code confignot Unit
  • Digital asset management and headless e-commerce back endsnot Unit

Unit

  • A vertical SaaS platform for contractors that wants to hold customer funds and issue expense cards without pursuing a charternot Payload CMS
  • A payroll or benefits platform embedding accounts so employees can be paid ahead of schedulenot Payload CMS
  • A marketplace that wants seller balances to sit in real accounts under its own brand rather than as ledger entries at a processornot Payload CMS
  • A company that needs interchange revenue from a card programme to make the unit economics of its core product worknot Payload CMS

Where each one falls short

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

Unit

  • Your product depends on a sponsor bank you do not contract with directly, and 2024 showed what that means: Thread Bank received an FDIC enforcement action naming its banking as a service programmes and Blue Ridge Bank went under an OCC consent order and offboarded fintech partners.
  • Programme approval by the bank is a separate gate from signing with Unit, and it can add months and impose product restrictions that were not visible during the commercial conversation.
  • Compliance obligations are shared but the operational load lands on you, and platforms consistently underestimate the staffing needed for disputes, escalations and the bank ongoing oversight requests.
  • Pricing is unpublished and blends platform fees, per-account and per-transaction charges and interchange sharing, which makes it hard to model unit economics before you have volume and easy to be surprised by the minimum.
  • Migrating a live deposit programme to a different provider or bank is extremely disruptive because it involves moving customer accounts and card credentials, so switching costs are far higher than for ordinary software.

Pricing, plan by plan

Payload CMS

Free
  • Open SourceFree
    • Full PayloadCMS
    • Self-hosted
    • Community support

Unit

On request
  • Unit Banking as a Service$undefined/year
    • Platform fee plus per-account and per-transaction charges, quoted
    • Interchange sharing arrangements negotiated per programme
    • Minimum commitment typical

Which should you pick?

Choose Payload CMS if

  • You need rest api.
  • You want to start without paying.
  • You work on Node.js, Self-hosted.
  • You also want graphql api.

Choose Unit if

  • You need deposit accounts.
  • You work on Web, iOS, Android.
  • You also want card issuing.

Questions people ask

Is Payload CMS or Unit better?
Neither clearly leads. Payload CMS starts at Free and Unit at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Payload CMS or Unit?
Payload CMS has a free tier; the other does not. Paid plans start at Free for Payload CMS and On request for Unit.
Does Payload CMS or Unit run on more platforms?
Payload CMS runs on Node.js, Self-hosted. Unit runs on Web, iOS, Android.
Can I use Payload CMS for free?
Yes. Payload CMS has a free tier, so you can try it without paying. Unit 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 Unit is typically brought in for.
What can Payload CMS do that Unit cannot?
Payload CMS covers REST API, GraphQL API, Versioning, TypeScript. Unit covers Deposit accounts, Card issuing, Payments, White label components.

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.

Source
Unit: Who actually holds the money?

A chartered partner bank, not Unit. Deposits sit at the sponsor bank and FDIC insurance flows from that bank, so its condition is your condition.

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.

Source
Unit: What happened with Unit sponsor banks in 2024?

Thread Bank received an FDIC enforcement action that explicitly named its banking as a service and lending as a service programmes, and Blue Ridge Bank was under an OCC consent order from January 2024 and offboarded fintech partners. Blue Ridge exited the order in late 2025.

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.

Source
Unit: What does Unit cost?

Not published. Expect a platform fee, per-account and per-transaction charges, an interchange share and a minimum commitment.

Unit: Do we need our own compliance team?

Yes. Unit supplies tooling and the bank sets the rules, but disputes, escalations and evidence for bank oversight require named people on your side.

Share

Related pages

Other head to heads