Softwr

APIs · head to head

Formance vs Memcached

Formance logo

Formance

APIs

Open source double-entry ledger and payment orchestration for money-moving software

From
Free
Rated
-
M

Memcached

Databases

Distributed memory object caching system

From
Free
Rated
-

The short version

  • Each has a real cost: Formance formance holds no money and provides no regulatory cover, so it must be paired with a payments provider or bank, and buyers occasionally mistake a ledger for a treasury system and discover the gap late.; Memcached no persistence at all: restart a node and its cache is gone, which every design must assume
  • They diverge on capability: Formance covers Double-entry ledger, Memcached covers In-memory key-value cache.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Formance and Memcached actually diverge.

Attributes where Formance and Memcached differ
AttributeFormanceMemcached
Pricing modelOpen source, no licence feeOpen source, no licence fee; managed cloud billed separately
PlatformsLinux, Docker, Kubernetes, Web, APILinux, macOS, Windows, Docker, Self-hosted
CategoryAPIsDatabases

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Formance

  • Double-entry ledger
  • Numscript transaction DSL
  • Multi-currency
  • Payments connectivity
  • Reconciliation
  • Self-hosted deployment
  • Cloud offering
  • API and SDKs

Only in Memcached

  • In-memory key-value cache
  • Multithreaded
  • Client-side sharding
  • Predictable memory use

What people use each for

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

Formance

  • A marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditablenot Memcached
  • A fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an auditnot Memcached
  • A payments team that wants one normalised model across several PSPs so reconciliation is not written separately for eachnot Memcached
  • A company that wants its ledger under a licence it can keep running even if the vendor disappearsnot Memcached

Memcached

  • Caching expensive database query results to cut loadnot Formance
  • Session storage where losing sessions on restart is acceptablenot Formance
  • Fronting an API whose responses are costly and change slowlynot Formance

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Formance

  • Formance holds no money and provides no regulatory cover, so it must be paired with a payments provider or bank, and buyers occasionally mistake a ledger for a treasury system and discover the gap late.
  • Numscript is a domain-specific language your team must learn, and while it makes complex splits expressible it also means transaction logic sits outside the languages your engineers already debug well.
  • Self-hosting a ledger that must never lose or duplicate a transaction is a serious operational commitment covering backups, upgrades and Postgres tuning, which is real cost the zero licence fee hides.
  • Enterprise pricing is not published, so the difference between the free path and the supported path cannot be evaluated without a sales conversation.
  • The company is much smaller than the incumbent alternatives, and while the MIT licence protects the code it does not protect the roadmap, so features on the hosted side may arrive slowly or change direction.

Memcached

  • No persistence at all: restart a node and its cache is gone, which every design must assume
  • No replication or failover, so losing a node loses that share of the cache
  • Only simple key-value, with none of the lists, sorted sets or streams Redis offers
  • Values are capped at 1MB by default, which surprises teams caching large documents

Pricing, plan by plan

Formance

Free
  • Open SourceFree
    • MIT licensed core ledger
    • Numscript transaction DSL
    • Multi-currency tracking
  • Enterprise$undefined/year
    • Managed or private deployment
    • Payments connectivity and reconciliation
    • Support with response commitments

Memcached

Free
  • MemcachedFree
    • Full functionality
    • Self-hosted
    • No usage limits

Which should you pick?

Choose Formance if

  • You need double-entry ledger.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Web, API.
  • You also want numscript transaction dsl.

Choose Memcached if

  • You need in-memory key-value cache.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker, Self-hosted.
  • You also want multithreaded.

Questions people ask

Is Formance or Memcached better?
Neither clearly leads. Formance starts at Free and Memcached at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Formance or Memcached?
Formance starts at Free and Memcached at Free.
Does Formance or Memcached run on more platforms?
Formance runs on Linux, Docker, Kubernetes, Web, API. Memcached runs on Linux, macOS, Windows, Docker, Self-hosted.
Can I use Formance for free?
Both have a free tier, so you can try either at no cost before committing.
What is Formance best used for?
Formance is most often used for a marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditable, a fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an audit, a payments team that wants one normalised model across several psps so reconciliation is not written separately for each, a company that wants its ledger under a licence it can keep running even if the vendor disappears. Of those, a marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditable and a fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an audit are not what Memcached is typically brought in for.
What can Formance do that Memcached cannot?
Formance covers Double-entry ledger, Numscript transaction DSL, Multi-currency, Payments connectivity. Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use.

Answered from the vendors’ own pages

Formance: Is Formance really open source?

Yes. The core ledger is MIT licensed with full source access and no deployment restrictions.

Memcached: Is Memcached free?

Yes, open source with no licence fee.

Formance: Does Formance move money?

No. It records and orchestrates movements; the actual payments happen at a PSP or bank you connect.

Memcached: Memcached or Redis?

Memcached is a pure cache: simpler, multithreaded and very predictable. Redis adds persistence, replication and rich data structures, which is why it is the default choice unless you specifically want a cache and nothing more.

Formance: What does the enterprise version cost?

Not published. It is an annual subscription quoted per customer.

Memcached: Does Memcached persist data?

No. Everything is in memory and lost on restart, by design.

Formance: Do I have to use Numscript?

Yes for anything beyond the simplest transfers. It is how multi-party transactions are expressed atomically.

Share

Related pages

Other head to heads