Softwr

Developer Tools · head to head

Cloud Native Buildpacks vs ThetaRay

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
Full reviewWebsite
ThetaRay logo

ThetaRay

Cybersecurity

Unsupervised AI transaction monitoring for cross-border and correspondent banking

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Cloud Native Buildpacks has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; ThetaRay unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • They diverge on capability: Cloud Native Buildpacks covers Detect and build lifecycle, ThetaRay covers Unsupervised detection.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Cloud Native Buildpacks and ThetaRay actually diverge.

Attributes where Cloud Native Buildpacks and ThetaRay differ
AttributeCloud Native BuildpacksThetaRay
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, Windows, CLI, Docker, KubernetesWeb
CategoryDeveloper ToolsCybersecurity

Identical on both: user rating (Not yet rated).

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 Cloud Native Buildpacks

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

Only in ThetaRay

  • Unsupervised detection
  • Cross-border focus
  • Sanctions screening
  • Alert triage
  • Customer risk scoring
  • Cloud native

What people use each 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 ThetaRay
  • Removing per-team Dockerfiles at an organisation where inconsistent base images have become an audit findingnot ThetaRay
  • Giving application teams a supported path to a hardened image without teaching every team container securitynot ThetaRay
  • Choosing a build system that a risk committee will accept because governance is vendor neutral rather than single vendornot ThetaRay

ThetaRay

  • A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot Cloud Native Buildpacks
  • A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot Cloud Native Buildpacks
  • A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot Cloud Native Buildpacks
  • A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot Cloud Native Buildpacks

Where each one falls 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.

ThetaRay

  • Unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • The alert reduction claim depends heavily on your data, so a parallel run is essential and adds months and cost before you can decommission the incumbent.
  • Coverage is strongest in cross-border and correspondent flows; institutions whose risk is domestic retail fraud will find the fit weaker than a general-purpose monitoring platform.
  • It is a smaller vendor than the incumbents, so integration connectors into legacy core banking systems are often bespoke work rather than a supported adapter.
  • Model retraining and tuning are vendor-led, which means changing detection behaviour is a support conversation rather than something your own analysts can do that afternoon.

Pricing, plan by plan

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

ThetaRay

On request
  • ThetaRay Sonar$undefined/year
    • Priced by monitored transaction volume and number of monitored entities
    • SaaS on Azure with regional data residency options
    • Parallel run and model tuning included in onboarding

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, CLI, Docker, Kubernetes.
  • You also want image rebasing.
Cloud Native Buildpacks review

Choose ThetaRay if

  • You need unsupervised detection.
  • You also want cross-border focus.
ThetaRay review

Questions people ask

Is Cloud Native Buildpacks or ThetaRay better?
Neither clearly leads. Cloud Native Buildpacks starts at Free and ThetaRay 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 ThetaRay?
Cloud Native Buildpacks has a free tier; the other does not. Paid plans start at Free for Cloud Native Buildpacks and On request for ThetaRay.
Does Cloud Native Buildpacks or ThetaRay run on more platforms?
Cloud Native Buildpacks runs on Linux, macOS, Windows, CLI, Docker, Kubernetes. ThetaRay runs on Web.
Can I use Cloud Native Buildpacks for free?
Yes. Cloud Native Buildpacks has a free tier, so you can try it without paying. ThetaRay 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 ThetaRay is typically brought in for.
What can Cloud Native Buildpacks do that ThetaRay cannot?
Cloud Native Buildpacks covers Detect and build lifecycle, Image rebasing, Reproducible layers, Builder images. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.

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.

ThetaRay: Does it replace a rules engine entirely?

Rarely on day one. Most institutions run it alongside existing rules during a parallel period, and some keep specific regulator-mandated rules permanently.

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.

ThetaRay: Where is the data processed?

SaaS runs on Microsoft Azure with regional deployment options, which is the mechanism for meeting data residency conditions in regulated markets.

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.

ThetaRay: Is sanctions screening included?

Screening is available on the same platform but licensed as part of the commercial package rather than bundled by default. Confirm it is in your quote.

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.

Share

Related pages

More on Cloud Native Buildpacks

More on ThetaRay

Keep looking

Other head to heads