Softwr

Developer Tools · head to head

Cloud Native Buildpacks vs Increase

Cloud Native Buildpacks logo

Cloud Native Buildpacks

Developer Tools

Specification and tooling that turns source code into OCI images without Dockerfiles

From
Free
Free plan
Yes
Increase logo

Increase

APIs

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

From
On request
Free plan
No

The short version

  • Cloud Native Buildpacks is a specification plus a lifecycle and the pack CLI.
  • Cloud Native Buildpacks is free; Increase prices on request.
  • Only Cloud Native Buildpacks lists detect and build lifecycle; only Increase lists ACH origination and receipt.
  • Prices and features on this page were last checked on 20 November 2026.

How do Cloud Native Buildpacks and Increase differ?

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

Attributes where Cloud Native Buildpacks and Increase differ
AttributeCloud Native BuildpacksIncrease
Starting priceFreeOn request
Pricing modelOpen source, no licence feeQuote
Free tierYesNo
PlatformsLinux, macOS, Windows, API, Self-hostedAPI, Web
CategoryDeveloper ToolsAPIs

Which features does each one have?

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

  • Detect and build lifecycle
  • Image rebasing
  • Reproducible layers
  • Builder images
  • Automatic SBOM output
  • pack CLI

Only in Increase

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

What is each one used for?

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

Cloud Native Buildpacks

  • Patching a base image once and rebasing hundreds of application images rather than rebuilding and redeploying eachnot Increase
  • Removing per-team Dockerfiles at an organisation where inconsistent base images have become an audit findingnot Increase
  • Giving application teams a supported path to a hardened image without teaching every team container securitynot Increase
  • Choosing a build system that a risk committee will accept because governance is vendor neutral rather than single vendornot Increase

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 Cloud Native Buildpacks
  • A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Cloud Native Buildpacks
  • A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Cloud Native Buildpacks
  • An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Cloud Native Buildpacks

Where do Cloud Native Buildpacks and Increase fall short?

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

Cloud Native Buildpacks

  • The operational cost is real: you own builder images, base image refresh cadence and migrations between specification versions, which currently sit at Buildpack API 0.10 and Platform API 0.12 with published migration guides, so breaking changes are a recurring chore
  • A cold build with no warm cache is noticeably slower than a well layered Dockerfile, and because the cache lives in a cache image or volume, ephemeral continuous integration runners pay full price on every run unless you deliberately warm them
  • Reproducibility depends on discipline rather than defaults, because buildpacks resolve runtime patch versions at build time unless you pin them and stability is only as good as the builder image tag you point at
  • The specification is neutral but the buildpacks are not, and in practice you depend on Paketo, Heroku or Google, whose roadmaps, support levels and update cadences differ; CNCF also records contributing organisations down 12 per cent year on year
  • Native dependencies, unusual monorepo layouts and non-standard project structures push you into writing custom buildpacks or extensions, which is a genuine engineering investment and not a configuration change

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

How much do Cloud Native Buildpacks and Increase cost?

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

Cloud Native Buildpacks

Free
  • Cloud Native BuildpacksFree
    • Apache-2.0, hosted by the CNCF
    • No commercial edition from the project itself
    • Commercial support only from vendors of specific buildpack distributions

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

Which should you pick?

Choose Cloud Native Buildpacks if

  • You need detect and build lifecycle.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, API, Self-hosted.
  • You also want image rebasing.

Choose Increase if

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

Questions people ask

Is Cloud Native Buildpacks or Increase better?
Neither clearly leads. Cloud Native Buildpacks starts at Free and Increase at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cloud Native Buildpacks or Increase?
Cloud Native Buildpacks has a free tier; the other does not. Paid plans start at Free for Cloud Native Buildpacks and On request for Increase.
Does Cloud Native Buildpacks or Increase run on more platforms?
Cloud Native Buildpacks runs on Linux, macOS, Windows, API, Self-hosted. Increase runs on API, Web.
Can I use Cloud Native Buildpacks for free?
Yes. Cloud Native Buildpacks has a free tier, so you can try it without paying. Increase starts at On request.
What is Cloud Native Buildpacks best used for?
Cloud Native Buildpacks is most often used for patching a base image once and rebasing hundreds of application images rather than rebuilding and redeploying each, removing per-team dockerfiles at an organisation where inconsistent base images have become an audit finding, giving application teams a supported path to a hardened image without teaching every team container security, choosing a build system that a risk committee will accept because governance is vendor neutral rather than single vendor. Of those, patching a base image once and rebasing hundreds of application images rather than rebuilding and redeploying each and removing per-team dockerfiles at an organisation where inconsistent base images have become an audit finding are not what Increase is typically brought in for.
What can Cloud Native Buildpacks do that Increase cannot?
Cloud Native Buildpacks covers Detect and build lifecycle, Image rebasing, Reproducible layers, Builder images. Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts.

Answered from the vendors’ own pages

Cloud Native Buildpacks: What does CNCF graduation actually change?

Nothing technically, but it signals audited governance, security review and multi-vendor maintenance, which is usually what a procurement or risk team needs before approving a build system.

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.

Cloud Native Buildpacks: How is this different from writing a Dockerfile?

Container build knowledge lives with the platform team in a builder image rather than in every repository, and rebasing lets you patch the runtime base of many images without rebuilding them.

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.

Cloud Native Buildpacks: Does it cost anything?

No. The specification and tooling are Apache-2.0 and free. You pay only if you buy commercial support for a specific buildpack distribution from Broadcom, Heroku or Google.

Increase: Is it international?

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

Cloud Native Buildpacks: Is it slower than a Dockerfile?

On a cold build with no cache, yes. Warm builds are competitive, but continuous integration runners that start empty every time will feel the difference.

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.

Share

Related pages

Other head to heads