Softwr

APIs · head to head

Increase vs Nix

Increase logo

Increase

APIs

Direct banking API for ACH, wires, real-time payments, accounts and cards

From
On request
Free plan
No
Nix logo

Nix

Developer Tools

Purely functional package manager and the NixOS distribution built on it, for byte-reproducible environments

From
Free
Free plan
Yes

The short version

  • Nix is free; Increase prices on request.
  • Only Increase lists ACH origination and receipt; only Nix lists content-addressed store.
  • Prices and features on this page were last checked on 20 November 2026.

How do Increase and Nix differ?

Increase and Nix differ on starting price (On request against Free), pricing model and free tier (No against Yes). Only the attributes on which Increase and Nix actually diverge.

Attributes where Increase and Nix differ
AttributeIncreaseNix
Starting priceOn requestFree
Pricing modelQuoteOpen source, no licence fee
Free tierNoYes
PlatformsAPI, WebLinux, macOS, Windows
CategoryAPIsDeveloper Tools

Not yet recorded: founded for Increase.

Which features does each one have?

They share no listed features; 8 appear only for Increase and 8 only for Nix. 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 Increase

  • ACH origination and receipt
  • Domestic wires
  • Real-time payments
  • Bank accounts
  • Cards
  • Cheques
  • Sandbox and simulations
  • Audit and reconciliation data

Only in Nix

  • Content-addressed store
  • Declarative system configuration
  • Atomic upgrades and rollback
  • nix develop shells
  • Flakes
  • Nixpkgs
  • Binary caches
  • Home Manager

What is each one used for?

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

Increase

  • A payroll or treasury product that needs to originate same-day ACH and wires under its own control rather than through a payment processornot Nix
  • A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Nix
  • A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Nix
  • An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Nix

Nix

  • A team that wants every developer and CI runner to use byte-identical toolchains without shipping a container for local worknot Increase
  • Reproducing a research computation or a build years later from a pinned commit rather than a written recipenot Increase
  • Managing a fleet of Linux servers declaratively with atomic rollback if a deployment breaks a servicenot Increase
  • Building minimal container images from precise dependency closures instead of a base image plus a package managernot Increase

Where do Increase and Nix fall short?

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

Increase

  • The published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately
  • Free allowances are deliberately small at ten account numbers and five physical cards, so any programme issuing accounts or cards at volume moves to quoted pricing almost immediately
  • Banking is provided through partner banks, so programme approval, compliance obligations and the ability to launch at all depend on a bank relationship you do not control, and post-Synapse bank risk appetite has tightened considerably
  • The API deliberately exposes payment rail mechanics rather than smoothing them, which is correct engineering but means a team without payments expertise will build reconciliation and return handling wrongly and only discover it when funds go astray
  • Coverage is United States only, so a company with international payout needs runs a second provider and reconciles two ledgers, and the single API argument disappears at the first cross border customer

Nix

  • The Nix language is lazy, dynamically typed and poorly documented, and its error messages frequently point at the wrong expression, so debugging a failing build is a skill that takes months rather than days to acquire
  • Flakes are the way essentially everyone uses Nix in 2026 and are still formally an experimental feature behind a flag, meaning tutorials, official documentation and real practice disagree with each other constantly
  • Anything that expects a conventional Linux filesystem layout breaks: prebuilt binaries, language package managers that download their own toolchains, and proprietary vendor installers all need patching or an FHS-compatible wrapper
  • Project governance has been publicly fractious, producing the Lix fork and the separately funded Determinate Systems distribution, so a new adopter now has to choose which Nix before they can start
  • The /nix/store grows without bound until you garbage collect, and on a developer laptop with several pinned nixpkgs revisions it routinely reaches tens of gigabytes

How much do Increase and Nix cost?

Increase is priced on request; Nix is free to use. Plan by plan below, from each vendor's own pricing page.

Increase

On request
  • Increase PlatformOn request
    • Monthly fee quoted by use case and not published
    • Next-day ACH origination listed at 0.50 US dollars per transaction
    • Same-day ACH origination listed at 2.00 per transaction

Nix

Free
  • Nix and NixOSFree
    • LGPL-2.1 licensed, no commercial tier
    • Public binary cache at cache.nixos.org
    • Community support via forum, Matrix and GitHub

Which should you pick?

Choose Increase if

  • You need ach origination and receipt.
  • You work on API, Web.
  • You also want domestic wires.

Choose Nix if

  • You need content-addressed store.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want declarative system configuration.

Questions people ask

Is Increase or Nix better?
Neither clearly leads. Increase starts at On request and Nix at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Increase or Nix?
Nix has a free tier; the other does not. Paid plans start at On request for Increase and Free for Nix.
Does Increase or Nix run on more platforms?
Increase runs on API, Web. Nix runs on Linux, macOS, Windows.
Can I use Nix for free?
Yes. Nix has a free tier, so you can try it without paying. Increase starts at On request.
What is Increase best used for?
Increase is most often used for a payroll or treasury product that needs to originate same-day ach and wires under its own control rather than through a payment processor, a marketplace that must hold seller balances in ledgered accounts with real account and routing numbers, a fintech that wants fednow and rtp payouts so recipients are paid outside banking hours, an engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logic. Of those, a payroll or treasury product that needs to originate same-day ach and wires under its own control rather than through a payment processor and a marketplace that must hold seller balances in ledgered accounts with real account and routing numbers are not what Nix is typically brought in for.
What can Increase do that Nix cannot?
Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts. Nix covers Content-addressed store, Declarative system configuration, Atomic upgrades and rollback, nix develop shells.

Answered from the vendors’ own pages

Increase: Does Increase publish its pricing?

Partly. Per transaction fees for ACH, wires, RTP, FedNow and cards are listed publicly. The monthly platform fee is not, and it is described only as varying by use case.

Nix: Do I have to run NixOS to use Nix?

No. The package manager runs fine on any Linux distribution and on macOS, and most teams start there with development shells rather than converting their servers.

Increase: Who holds the deposits?

Partner banks, not Increase itself. That relationship determines your programme approval, your compliance obligations and your risk if the bank changes appetite.

Nix: Is Nix a replacement for Docker?

It solves an adjacent problem. Nix reproduces the contents of an environment exactly; Docker distributes an image. Many teams use Nix to build the image.

Increase: Is it international?

No. Increase covers United States rails only, so cross border payouts require a second provider.

Nix: Are flakes safe to use in production?

They are used in production widely and are stable in practice, but they remain officially experimental, which means the interface can still change and documentation is split.

Increase: How is it different from a middleware BaaS platform?

It exposes the rails rather than abstracting them, showing real return codes and settlement timing. That suits teams who understand payments and punishes teams who do not.

Nix: What is Lix and should I care?

Lix is a community fork of the Nix implementation created after governance disputes. It is largely compatible; the practical impact is that you must decide which implementation your team standardises on.

Share

Related pages

Other head to heads