Softwr

Developer Tools · head to head

Cloud Native Buildpacks vs Milestone XProtect

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
Milestone XProtect logo

Milestone XProtect

Cybersecurity

Open platform video management software with perpetual per-device licences

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • 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.; Milestone XProtect care Plus is presented as optional but is not in practice: without it, perpetual licences stop receiving version upgrades and eventually you cannot add a current camera because your frozen version does not support it.
  • They diverge on capability: Cloud Native Buildpacks covers Detect and build lifecycle, Milestone XProtect covers Open device support.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Cloud Native Buildpacks and Milestone XProtect differ
AttributeCloud Native BuildpacksMilestone XProtect
Pricing modelOpen source, no licence feeOne-time purchase per device licence, plus annual Care Plus
PlatformsLinux, macOS, Windows, CLI, Docker, KubernetesWindows, Web, iOS, Android
CategoryDeveloper ToolsCybersecurity

Identical on both: starting price (Free), free tier (Yes), 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 Milestone XProtect

  • Open device support
  • Perpetual device licences
  • Federated architecture
  • Failover recording
  • Evidence export
  • Smart Map
  • Integration platform
  • Video summarisation

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

Milestone XProtect

  • A city or transport operator running tens of thousands of cameras across federated sitesnot Cloud Native Buildpacks
  • An enterprise with mixed legacy camera brands that refuses to standardise on one manufacturernot Cloud Native Buildpacks
  • A critical infrastructure site needing failover recording servers and tamper-evident evidence exportnot Cloud Native Buildpacks
  • An integrator building a bespoke security application on top of an open VMS platformnot 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.

Milestone XProtect

  • Care Plus is presented as optional but is not in practice: without it, perpetual licences stop receiving version upgrades and eventually you cannot add a current camera because your frozen version does not support it.
  • Per-device licensing means multi-sensor and multi-imager cameras consume several licences each, so a headline camera count badly understates the true licence cost of a modern design.
  • It is Windows only for servers and needs a properly designed server and storage architecture, so the software price is a fraction of a project that also needs recording servers, storage and an integrator.
  • Complexity requires trained staff or a certified integrator; organisations that install it without either end up running a large deployment on default settings and never using the features they paid for.
  • Milestone retired Kite from its portfolio in favour of Arcules from January 2025, which stranded buyers who had standardised on Kite and is a reminder that the cloud side of the portfolio has changed direction more than once.

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

Milestone XProtect

Free
  • XProtect Essential+Free
    • Free for up to 8 cameras
    • No recording time limit
    • No vendor support included
  • XProtect Express+$109/one-time
    • Perpetual device licence, distributor list price
    • Single site, single server
    • Care Plus purchased separately per device per year
  • XProtect Professional+$177/one-time
    • Perpetual device licence, distributor list price
    • Multiple recording servers
    • Edge storage retrieval
  • XProtect Expert$282/one-time
    • Perpetual device licence, distributor list price
    • Failover recording servers
    • Advanced video wall and evidence handling

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 Milestone XProtect if

  • You need open device support.
  • You want to start without paying.
  • You work on Windows, Web, iOS, Android.
  • You also want perpetual device licences.
Milestone XProtect review

Questions people ask

Is Cloud Native Buildpacks or Milestone XProtect better?
Neither clearly leads. Cloud Native Buildpacks starts at Free and Milestone XProtect at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cloud Native Buildpacks or Milestone XProtect?
Cloud Native Buildpacks starts at Free and Milestone XProtect at Free.
Does Cloud Native Buildpacks or Milestone XProtect run on more platforms?
Cloud Native Buildpacks runs on Linux, macOS, Windows, CLI, Docker, Kubernetes. Milestone XProtect runs on Windows, Web, iOS, Android.
Can I use Cloud Native Buildpacks for free?
Both have a free tier, so you can try either at no cost before committing.
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 Milestone XProtect is typically brought in for.
What can Cloud Native Buildpacks do that Milestone XProtect cannot?
Cloud Native Buildpacks covers Detect and build lifecycle, Image rebasing, Reproducible layers, Builder images. Milestone XProtect covers Open device support, Perpetual device licences, Federated architecture, Failover recording.

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.

Milestone XProtect: Is XProtect really free for small sites?

Essential+ is free for up to eight cameras with no recording time limit, but it comes with no vendor support and no multi-server capability.

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.

Milestone XProtect: Are licences perpetual or annual?

Device licences are perpetual. The annual cost is Care Plus, the support and software update contract, which you need to stay on current versions.

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.

Milestone XProtect: What happens if I do not renew Care Plus?

The system keeps recording, but you stop getting version upgrades, and over a few years that blocks you from adding newer cameras.

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.

Milestone XProtect: Who owns Milestone?

Canon. The portfolio also includes BriefCam analytics and Arcules cloud video, with Arcules replacing Milestone Kite from January 2025.

Share

Related pages

More on Cloud Native Buildpacks

More on Milestone XProtect

Keep looking

Other head to heads