Softwr

Developer Tools · head to head

Cloud Native Buildpacks vs March Networks

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
March Networks logo

March Networks

Cybersecurity

Banking and retail video with transaction overlay, sold by a Canadian firm that changed from Chinese to Taiwanese ownership

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.; March Networks the ownership history is a live compliance question: Chinese-owned via Infinova from 2011, with a PRC government entity as controlling shareholder by January 2020, before the December 2021 sale to Delta Electronics of Taiwan, and any US federal or contractor buyer should expect to document that chain during a procurement review.
  • They diverge on capability: Cloud Native Buildpacks covers Detect and build lifecycle, March Networks covers Command Enterprise.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Cloud Native Buildpacks and March Networks differ
AttributeCloud Native BuildpacksMarch Networks
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, Windows, CLI, Docker, KubernetesWindows, Web, iOS, Android
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 March Networks

  • Command Enterprise
  • Searchlight
  • Hybrid recording
  • X-Series hybrid NVRs
  • Health monitoring
  • ATM and teller integration
  • Retail loss prevention analytics
  • Evidence export

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

March Networks

  • A bank investigating a disputed ATM withdrawal who needs the clip for that transaction, not two hours of timelinenot Cloud Native Buildpacks
  • A credit union refreshing 200 branches in phases where analogue and IP cameras must coexist on one recordernot Cloud Native Buildpacks
  • A restaurant chain overlaying till exceptions on video across hundreds of locationsnot Cloud Native Buildpacks
  • A transit operator needing video retrieval from vehicles and stations without shipping terabytes over the networknot 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.

March Networks

  • The ownership history is a live compliance question: Chinese-owned via Infinova from 2011, with a PRC government entity as controlling shareholder by January 2020, before the December 2021 sale to Delta Electronics of Taiwan, and any US federal or contractor buyer should expect to document that chain during a procurement review.
  • NDAA compliance is stated at the product level and rests on American system-on-chip processors in the majority of cameras and in specific recorder lines, which means it must be confirmed per model rather than assumed across the catalogue.
  • The platform is engineered around banking and retail workflows, so buyers outside those verticals pay for transaction integration they will never use and get a less developed general security experience than from a Genetec or Milestone.
  • No pricing is published and everything is quoted through integrators, so a multi-hundred-site estate cannot be budgeted without a design exercise and there is no benchmark against which to test a quote.
  • Hybrid recording means a recorder in every branch, which is hardware to install, monitor, service and eventually replace at every location, and that refresh cycle is a recurring capital event that cloud rivals avoid entirely.

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

March Networks

On request
  • Command Enterprise and Searchlight$undefined/year
    • Per-recorder and per-channel licensing quoted through integrators
    • Searchlight business intelligence licensed separately
    • X-Series hybrid recorders purchased per site

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 March Networks if

  • You need command enterprise.
  • You work on Windows, Web, iOS, Android.
  • You also want searchlight.
March Networks review

Questions people ask

Is Cloud Native Buildpacks or March Networks better?
Neither clearly leads. Cloud Native Buildpacks starts at Free and March Networks 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 March Networks?
Cloud Native Buildpacks has a free tier; the other does not. Paid plans start at Free for Cloud Native Buildpacks and On request for March Networks.
Does Cloud Native Buildpacks or March Networks run on more platforms?
Cloud Native Buildpacks runs on Linux, macOS, Windows, CLI, Docker, Kubernetes. March Networks runs on Windows, Web, iOS, Android.
Can I use Cloud Native Buildpacks for free?
Yes. Cloud Native Buildpacks has a free tier, so you can try it without paying. March Networks 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 March Networks is typically brought in for.
What can Cloud Native Buildpacks do that March Networks cannot?
Cloud Native Buildpacks covers Detect and build lifecycle, Image rebasing, Reproducible layers, Builder images. March Networks covers Command Enterprise, Searchlight, Hybrid recording, X-Series hybrid NVRs.

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.

March Networks: Who owns March Networks?

Delta Electronics of Taiwan, which acquired it in December 2021 for 114 million US dollars. Before that it was owned by Chinese manufacturer Infinova, which by January 2020 had a PRC government entity as controlling shareholder.

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.

March Networks: Is March Networks NDAA compliant?

The company states it is, citing American system-on-chip processors in the majority of its cameras and in its Command Recording Server bundles and X-Series hybrid NVRs. Verify per model, and expect the ownership history to be raised in a federal procurement review.

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.

March Networks: What is Searchlight?

The layer that overlays ATM, teller and point of sale transaction data on video so investigators search by transaction rather than by time.

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.

March Networks: Is video stored in the cloud?

No, it is hybrid. Video is recorded on a recorder at each site and only required clips move centrally, which is why it suits large branch estates on modest connections.

Share

Related pages

More on Cloud Native Buildpacks

More on March Networks

Keep looking

Other head to heads