Softwr

Developer Tools · head to head

Distroless vs Highnote

Distroless logo

Distroless

Developer Tools

Minimal container base images from Google that hold only an app and its runtime

From
Free
Free plan
Yes
Highnote logo

Highnote

APIs

Card issuing, acquiring and ledger on one platform for embedded payments

From
On request
Free plan
No

The short version

  • Distroless is free; Highnote prices on request.
  • Only Distroless lists debian 13 based images; only Highnote lists card issuing.
  • Where Distroless falls short: no shell or package manager, so installing packages or debugging inside the image is harder.
  • Prices and features on this page were last checked on 20 November 2026.

How do Distroless and Highnote differ?

Distroless and Highnote differ on starting price (Free against On request), pricing model (Open-source against Quote) and free tier (Yes against No). Only the attributes on which Distroless and Highnote actually diverge.

Attributes where Distroless and Highnote differ
AttributeDistrolessHighnote
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsLinuxWeb, API
CategoryDeveloper ToolsAPIs

Which features does each one have?

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

  • No package manager or shell in runtime images
  • Debian 13 based images
  • Static, base and cc images for compiled apps
  • Java, Node.js and Python 3 runtime images
  • Nonroot and debug tag variants
  • Cosign keyless image signing
  • Multi architecture builds including amd64, arm64 and s390x
  • Bazel based build tooling

Only in Highnote

  • Card issuing
  • Merchant acquiring
  • Unified ledger
  • Spend controls
  • GraphQL API
  • Programme management
  • Dispute handling
  • Real time authorisation webhooks

What is each one used for?

Distroless is most often brought in for production base images for Go or Rust binaries. The jobs each tool is most often brought in to do.

Distroless

  • Production base images for Go or Rust binariesnot Highnote
  • Reducing vulnerability scanner findingsnot Highnote
  • Smaller Java and Node.js container imagesnot Highnote
  • Running containers as a non root usernot Highnote
  • Verifying image provenance with cosignnot Highnote

Highnote

  • A marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledgernot Distroless
  • A vertical software company embedding card acceptance and card issuing for the same customer basenot Distroless
  • A fintech launching a commercial charge card programme with custom authorisation logicnot Distroless
  • A platform replacing separate issuing and acquiring vendors to remove cross system reconciliationnot Distroless

Where do Distroless and Highnote fall short?

Distroless's most cited limit: no shell or package manager, so installing packages or debugging inside the image is harder. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Distroless

  • No shell or package manager, so installing packages or debugging inside the image is harder
  • Language images cover only Java, Node.js and Python 3, with other runtimes built by the user
  • Architecture support differs by image, and python3 lists only amd64, arm64 and riscv64
  • Tags without a distro suffix may change which Debian release they resolve to

Highnote

  • Card issuing requires a sponsor bank, and that bank sets programme approval, compliance obligations and often minimum volumes, so a small programme can be rejected regardless of technical fit
  • Pricing is entirely quoted, including platform fees, per active card charges and monthly minimums that do not appear on the website, so the true cost per card is only visible late in a sales process
  • Interchange sharing is the real revenue model for most customers, and the split is negotiated, capped for regulated debit under the Durbin amendment and sensitive to your spend mix, so revenue projections built on headline interchange rates overstate income
  • Running issuing and acquiring with one provider concentrates risk: an outage or a compliance action affects both money in and money out at the same time
  • Highnote is a younger company than the established issuer processors, so long term programme continuity, network certifications in new geographies and international coverage are thinner than the incumbent alternatives

How much do Distroless and Highnote cost?

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

Distroless

Free

No published plan breakdown. See the Distroless review.

Highnote

On request
  • Highnote platformOn request
    • Quoted per programme with no public rate card
    • Requires a sponsor bank relationship for card issuing
    • Interchange sharing terms negotiated per programme

Which should you pick?

Choose Distroless if

  • You need no package manager or shell in runtime images.
  • You want to start without paying.
  • You work on Linux.
  • You also want debian 13 based images.

Choose Highnote if

  • You need card issuing.
  • You work on Web, API.
  • You also want merchant acquiring.

Questions people ask

Is Distroless or Highnote better?
Neither clearly leads. Distroless starts at Free and Highnote at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Distroless or Highnote?
Distroless has a free tier; the other does not. Paid plans start at Free for Distroless and On request for Highnote.
Does Distroless or Highnote run on more platforms?
Distroless runs on Linux. Highnote runs on Web, API.
Can I use Distroless for free?
Yes. Distroless has a free tier, so you can try it without paying. Highnote starts at On request.
What is Distroless best used for?
Distroless is most often used for production base images for go or rust binaries, reducing vulnerability scanner findings, smaller java and node.js container images, running containers as a non root user. Of those, production base images for go or rust binaries and reducing vulnerability scanner findings are not what Highnote is typically brought in for.
What can Distroless do that Highnote cannot?
Distroless covers No package manager or shell in runtime images, Debian 13 based images, Static, base and cc images for compiled apps, Java, Node.js and Python 3 runtime images. Highnote covers Card issuing, Merchant acquiring, Unified ledger, Spend controls.

Answered from the vendors’ own pages

Distroless: What is in a distroless image?

According to the project, an image holds only your application and its runtime dependencies. Package managers, shells and other standard Linux distribution programs are omitted.

Source
Highnote: Do I need a sponsor bank?

Yes for card issuing in the United States. Highnote is a processor and programme platform, not a bank, and the sponsor bank sets approval and compliance terms.

Distroless: How can I debug a distroless container?

The project publishes debug and debug-nonroot tags that add a BusyBox shell. The standard tags have no shell.

Source
Highnote: How do customers make money on a card programme?

Mostly interchange sharing. Negotiate the split explicitly and model it against your actual spend mix, since regulated debit interchange is capped.

Distroless: Are distroless images signed?

Yes. Images are signed with cosign keyless signing, and the project provides a cosign verify command that checks the certificate issuer and identity.

Source
Highnote: Can Highnote handle both accepting and issuing payments?

Yes since its 2025 acquiring launch, on the same ledger, which is its main structural differentiator.

Distroless: Which licence does Distroless use?

GitHub's repository data lists the Apache 2.0 licence. The images are free to use.

Source
Share

Related pages

Other head to heads