Softwr

Developer Tools · head to head

Nixpacks vs Rhombus Systems

Nixpacks logo

Nixpacks

Developer Tools

Build system that turns a source directory into an OCI image, now in maintenance mode

From
Free
Free plan
Yes
Full reviewWebsite
Rhombus Systems logo

Rhombus Systems

Cybersecurity

Cloud-managed cameras, sensors and access control with a per-camera annual licence

From
$149/year
Free plan
No
Full reviewWebsite

The short version

  • Only Nixpacks has a free tier, so it costs nothing to try first.
  • Each has a real cost: Nixpacks the project is in maintenance mode with no commits on the default branch since May 2026 and no release since October 2025, so support for new language versions arrives only if someone forks it.; Rhombus Systems the per-camera annual licence never ends and a camera without an active licence stops working, so the total cost over a ten-year hardware life is several times the hardware price.
  • They diverge on capability: Nixpacks covers Automatic language detection, Rhombus Systems covers On-camera storage.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Nixpacks and Rhombus Systems actually diverge.

Attributes where Nixpacks and Rhombus Systems differ
AttributeNixpacksRhombus Systems
Starting priceFree$149/year
Pricing modelOpen source, no licence feePer camera per year licence plus hardware
Free tierYesNo
PlatformsLinux, macOS, CLI, DockerWeb, 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 Nixpacks

  • Automatic language detection
  • No Dockerfile required
  • Nix toolchains
  • Configuration escape hatches
  • Docker layer caching

Only in Rhombus Systems

  • On-camera storage
  • No NVR or server
  • AI search
  • Access control
  • Environmental sensors
  • Unlimited users
  • Ten year hardware warranty
  • Optional cloud archiving

What people use each for

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

Nixpacks

  • Understanding the build behaviour of a platform that adopted Nixpacks before it was frozennot Rhombus Systems
  • Producing container images from a polyglot monorepo where nobody wants to own several Dockerfilesnot Rhombus Systems
  • Reproducing an existing Railway build locally while planning a migration to Railpacknot Rhombus Systems
  • Comparing what a Nix based builder does differently from a buildpack before choosing a successornot Rhombus Systems

Rhombus Systems

  • A school district running video across dozens of buildings with no local IT at each sitenot Nixpacks
  • A clinic group needing door access and cameras in one console under a single audit trailnot Nixpacks
  • A logistics operator that wants to search for a specific vehicle across sites without scrubbing footagenot Nixpacks
  • An office estate replacing ageing NVRs where nobody remains who knows how to maintain themnot Nixpacks

Where each one falls short

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

Nixpacks

  • The project is in maintenance mode with no commits on the default branch since May 2026 and no release since October 2025, so support for new language versions arrives only if someone forks it.
  • Build determinism is softer than it appears, because providers pin a nixpkgs archive commit and bumping that archive silently moves compiler and runtime versions underneath a build that looks unchanged.
  • Caching is limited to Docker layers rather than a content addressed graph, so a small change early in the build invalidates everything after it, which is exactly the limitation Railpack was rewritten to fix.
  • Images carry Nix store layers and come out larger than an equivalent tuned Dockerfile or buildpack output, which costs registry storage and slows cold pulls on scale-out.
  • There is no specification, no vendor neutral governance and no third party provider ecosystem, so a single company was able to redirect strategy and leave every downstream user with a frozen build tool.

Rhombus Systems

  • The per-camera annual licence never ends and a camera without an active licence stops working, so the total cost over a ten-year hardware life is several times the hardware price.
  • Cameras must be Rhombus, so there is no reuse of existing IP cameras and migrating away means replacing every device rather than changing software.
  • Cloud archiving is priced separately by retention and stream count, and long retention on multisensor cameras runs into five figures per camera, which can dwarf everything else in the quote.
  • On-camera storage is the default retention, so a camera physically stolen or destroyed takes its unarchived footage with it unless cloud archiving was paid for on that camera.
  • Analytics and integrations are good for mid-market needs but shallower than a dedicated enterprise VMS with a large third-party ecosystem, so specialist requirements like advanced LPR or forensic search hit limits.

Pricing, plan by plan

Nixpacks

Free
  • NixpacksFree
    • MIT licensed, no usage limits
    • No commercial edition and no support contract
    • In maintenance mode, superseded by Railpack

Rhombus Systems

$149/year
  • Professional$149/year
    • Per camera per year
    • Cloud console and management
    • On-camera storage retention
  • Enterprise$199/year
    • Per camera per year
    • Everything in Professional
    • Flexible cloud archiving options
  • Cloud archiving$undefined/year
    • Priced separately by retention period and stream count
    • Multisensor cameras cost several times a single sensor camera
    • Long retention on multisensor models can reach five figures per camera

Which should you pick?

Choose Nixpacks if

  • You need automatic language detection.
  • You want to start without paying.
  • You work on Linux, macOS, CLI, Docker.
  • You also want no dockerfile required.
Nixpacks review

Choose Rhombus Systems if

  • You need on-camera storage.
  • You work on Web, iOS, Android.
  • You also want no nvr or server.
Rhombus Systems review

Questions people ask

Is Nixpacks or Rhombus Systems better?
Neither clearly leads. Nixpacks starts at Free and Rhombus Systems at $149/year, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or Rhombus Systems?
Nixpacks has a free tier; the other does not. Paid plans start at Free for Nixpacks and $149/year for Rhombus Systems.
Does Nixpacks or Rhombus Systems run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. Rhombus Systems runs on Web, iOS, Android.
Can I use Nixpacks for free?
Yes. Nixpacks has a free tier, so you can try it without paying. Rhombus Systems starts at $149/year.
What is Nixpacks best used for?
Nixpacks is most often used for understanding the build behaviour of a platform that adopted nixpacks before it was frozen, producing container images from a polyglot monorepo where nobody wants to own several dockerfiles, reproducing an existing railway build locally while planning a migration to railpack, comparing what a nix based builder does differently from a buildpack before choosing a successor. Of those, understanding the build behaviour of a platform that adopted nixpacks before it was frozen and producing container images from a polyglot monorepo where nobody wants to own several dockerfiles are not what Rhombus Systems is typically brought in for.
What can Nixpacks do that Rhombus Systems cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. Rhombus Systems covers On-camera storage, No NVR or server, AI search, Access control.

Answered from the vendors’ own pages

Nixpacks: Should I start a new project on Nixpacks?

No. The documentation and README both say it is in maintenance mode and recommend Railpack. Choose Railpack, Cloud Native Buildpacks or a Dockerfile instead.

Rhombus Systems: Do I need an NVR or a server?

No. Cameras record on board and connect directly to the cloud console, which is the main operational reason organisations pick it.

Nixpacks: Will my existing Nixpacks builds stop working?

Not immediately. Pinned nixpkgs archives keep resolving, so builds continue. What you lose is support for new runtime major versions and any fix for a provider bug.

Rhombus Systems: What does the licence cost?

Roughly $149 per camera per year for Professional and about $199 for Enterprise, typically sold in one, three, five or ten year terms.

Nixpacks: What replaces it?

Railpack, also from Railway and also MIT licensed, rebuilt as a BuildKit custom frontend for finer grained caching and parallel steps.

Rhombus Systems: Is cloud storage included?

No. On-camera storage is the default. Cloud archiving is a separate charge priced by retention duration and number of streams.

Nixpacks: Is it still open source?

Yes, MIT, and the repository is not archived. Being open source does not help much when nobody is merging provider updates.

Rhombus Systems: Can I use my existing cameras?

No. The platform works only with Rhombus hardware, which is the trade-off for the zero-server architecture.

Share

Related pages

More on Nixpacks

More on Rhombus Systems

Keep looking

Other head to heads