Formance is an open source, modular developer platform written in Go for building and operating complex money flows of any size and shape, aimed at fintech engineers and platform teams who need to record internal financial transactions and move money without assembling that infrastructure from scratch.

What it is

Formance describes itself as Open Source Infrastructure for the Financial Internet. The project ships several components that can be used together as the Formance Stack or separately as standalone micro-services and libraries. Formance Ledger is a programmable double-entry, immutable source of truth for recording internal financial transactions and money movements. Formance Payments is a unified API and data layer for payments processing. Formance Numscript is a domain-specific language and virtual machine for monetary computations and transaction modeling. The repository is transitioning to a unified, public-facing monorepo that imports versioned services submodules and provides a common infrastructure layer, and it is backed by Y Combinator, with community discussion hosted in GitHub Discussions.

The concrete problem it solves is the internal financial ledger and money-movement layer that every product handling balances eventually has to build. Rather than hand-rolling double-entry accounting tables inside an application database, writing bespoke abstractions over payment providers, and improvising scripts to compute monetary amounts, a team can run Formance components as services that record transactions immutably and express monetary logic in Numscript. It lives in the Go and cloud-native ecosystem, packaged as binaries and Docker images and configured through command-line options and environment variables. The reference deployment stack is built on PostgreSQL as the main storage backend, Kafka or NATS for cross-services async communication, and Traefik as the main HTTP gateway.

Key capabilities

• Formance Ledger provides a programmable double-entry ledger acting as an immutable source of truth for internal financial transactions and money movements.
• Formance Payments provides a unified API and data layer for payments processing.
• Formance Numscript provides a DSL and virtual machine for monetary computations and transaction modeling.
• Components deploy either as the whole Formance Stack or as standalone micro-services and libraries.
• The fctl CLI covers login, stack creation, ledger transaction submission, and opening the control dashboard with fctl ui.
• Official Helm charts at helm.formance.com are the recommended, standard way to deploy the service collection to a Kubernetes cluster.
• Asynchronous cross-service communication runs over Kafka or NATS, with PostgreSQL used as the primary storage backend.

Who uses it and how

• Product and platform teams building complex money flows who want a ledger rather than an application-side balance table.
• Developers evaluating the platform through the Formance Cloud Sandbox, which is explicitly intended for testing and not for production usage.
• Kubernetes operators who deploy the stack through the official Formance Helm charts.
• Self-hosters running the services as binaries or Docker images, configured by command-line options and environment variables.
• Teams that adopt only one component, such as Ledger as a standalone micro-service or Payments as a unified API layer over payment processing.

Getting started

The documented entry point is the Formance Cloud Sandbox: install the CLI with brew tap formancehq/tap followed by brew install fctl, then run fctl login, fctl stack create foobar, and fctl ledger send world foo 100 EUR/2 --ledger=demo. Full documentation lives at docs.formance.com, and the sandbox is made available for testing rather than production.

How it compares

No alternatives or paid products are named anywhere in the facts provided, so this page cannot draw a comparison on licence, hosting model, data ownership, or cost. On the available evidence, Formance stands alone in this registry.

When to use it — and when not to

A self-hoster takes on operating PostgreSQL, Kafka or NATS, Traefik, and the service collection itself, so this suits teams already comfortable running cloud-native infrastructure on Kubernetes. The licence is listed as NOASSERTION for the stack even though the Ledger sub-repository carries an MIT badge, so anyone with strict licensing requirements should verify terms before adopting. The project shows 524 stars, 67 forks, and one open issue, with no topics declared on the repository, so teams wanting a large, well-populated community footprint should weigh that against the scope of what the platform offers.

# macOS
brew tap formancehq/tap
brew install fctl

# login to formance cloud
fctl login

# create a sandbox stack deployment
# please note: sandbox are made available for testing and not made for production usage
# read more in the docs [1]
fctl stack create foobar

# commit your first ledger transaction
fctl ledger send world foo 100 EUR/2 --ledger=demo

# checkout the control dashboard
fctl ui