APIs · head to head
Formance vs Zeplo

Formance
APIs
Open source double-entry ledger and payment orchestration for money-moving software
- From
- Free
- Rated
- -

Zeplo
APIs
Message queue as a URL prefix, adding retries and delays to any HTTP request
- 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.; Zeplo zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
- They diverge on capability: Formance covers Double-entry ledger, Zeplo covers URL prefix interface.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Formance and Zeplo actually diverge.
Identical on both: starting price (Free), free tier (Yes), 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 Formance
- Double-entry ledger
- Numscript transaction DSL
- Multi-currency
- Payments connectivity
- Reconciliation
- Self-hosted deployment
- Cloud offering
- API and SDKs
Only in Zeplo
- URL prefix interface
- Retries with backoff
- Delayed delivery
- Cron scheduling
- Concurrency limits
- Deduplication keys
- Request logs
- Team workspaces
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 Zeplo
- A fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an auditnot Zeplo
- A payments team that wants one normalised model across several PSPs so reconciliation is not written separately for eachnot Zeplo
- A company that wants its ledger under a licence it can keep running even if the vendor disappearsnot Zeplo
Zeplo
- A Vercel or Cloudflare Workers application that needs retried background jobs without deploying a separate always-on workernot Formance
- A team that wants a webhook receiver protected by a concurrency limit so a burst does not overwhelm a downstream APInot Formance
- A small product needing cron jobs against HTTP endpoints without adding a scheduler to its infrastructurenot Formance
- A developer adding idempotent retries to an unreliable third-party API call with a one-line URL changenot 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.
Zeplo
- Zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
- The free Developer tier includes only 500 requests a month and one team member, so it is a demonstration allowance rather than a usable free plan for anything real.
- Overage on the Developer tier is 20 US dollars per 100,000 requests, two hundred times the marginal rate on the Company tier, so exceeding the free allowance without upgrading is expensive.
- Team members cost 15 US dollars each beyond the plan allowance, which is an odd charge on an infrastructure product billed by request volume.
- Log retention is 30 days on both published tiers, so anything requiring longer audit trails on job execution has to be logged separately.
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
Zeplo
Free- DeveloperFree
- 500 requests a month included
- $20 per additional 100,000 requests
- 1 team member
- Company$39/month
- 1,000,000 requests a month included
- $10 per additional million requests
- Up to 3 team members
- Enterprise$undefined/month
- Volume discounts
- Custom team size
- Support with SLA
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 Zeplo if
- You need url prefix interface.
- You want to start without paying.
- You work on Web, Cloud.
- You also want retries with backoff.
Questions people ask
- Is Formance or Zeplo better?
- Neither clearly leads. Formance starts at Free and Zeplo at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Formance or Zeplo?
- Formance starts at Free and Zeplo at Free.
- Does Formance or Zeplo run on more platforms?
- Formance runs on Linux, Docker, Kubernetes, Web, API. Zeplo runs on Web, Cloud.
- 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 Zeplo is typically brought in for.
- What can Formance do that Zeplo cannot?
- Formance covers Double-entry ledger, Numscript transaction DSL, Multi-currency, Payments connectivity. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.
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.
Zeplo: How does Zeplo work?
You prefix your endpoint URL with zeplo.to and add query parameters for retries, delay, cron or concurrency. No SDK or broker is needed.
Formance: Does Formance move money?
No. It records and orchestrates movements; the actual payments happen at a PSP or bank you connect.
Zeplo: What does it cost?
Free for 500 requests a month; 39 US dollars a month for a million requests, then 10 dollars per additional million.
Formance: What does the enterprise version cost?
Not published. It is an annual subscription quoted per customer.
Zeplo: Is it suitable for critical jobs?
It is a small vendor in your execution path with no published SLA below Enterprise, so weigh that against the convenience.
Formance: Do I have to use Numscript?
Yes for anything beyond the simplest transfers. It is how multi-party transactions are expressed atomically.
Zeplo: Does it work with serverless platforms?
Yes, that is its main use, covering Vercel, Cloudflare Workers, Netlify and similar environments that lack long-running workers.
Related pages
Other head to heads
- Formance vs Moov
- Formance vs Column
- Formance vs Convoy
- Formance vs Sila
- Formance vs Increase
- Formance vs Yapily
- Formance vs 10x Banking
- Formance vs Tribe Payments
- Formance vs Dwolla
- Formance vs Kong
- Formance vs Tyk
- Formance vs Volt
- Formance vs Enable Banking
- Formance vs Flybits
- Formance vs i2c
- Formance vs KeystoneJS
- Formance vs Liveblocks
- Formance vs Svix
- Formance vs AWS API Gateway
- Formance vs Tink
- Formance vs Pusher
- Formance vs Yodlee
- Formance vs Lithic
- Formance vs Swan
- Formance vs Unit
- Formance vs Basis Theory
- Formance vs Boomi API Management
- Formance vs Codat
- Formance vs curl
- Formance vs Fintech Farm
- Formance vs Fintecture
- Zeplo vs Moov
- Zeplo vs Column
- Zeplo vs Convoy
- Zeplo vs Sila
- Zeplo vs Increase
- Zeplo vs Yapily
- Zeplo vs 10x Banking
- Zeplo vs Tribe Payments
- Zeplo vs Dwolla
- Zeplo vs Kong
- Zeplo vs Tyk
- Zeplo vs Volt
- Zeplo vs Enable Banking
- Zeplo vs Flybits
- Zeplo vs i2c
- Zeplo vs KeystoneJS
- Zeplo vs Liveblocks
- Zeplo vs Svix
- Zeplo vs AWS API Gateway
- Zeplo vs Tink
- Zeplo vs Pusher
- Zeplo vs Yodlee
- Zeplo vs Lithic
- Zeplo vs Swan
- Zeplo vs Unit
- Zeplo vs Basis Theory
- Zeplo vs Boomi API Management
- Zeplo vs Codat
- Zeplo vs curl
- Zeplo vs Fintech Farm
- Zeplo vs Fintecture
