Developer Tools · head to head
Nixpacks vs ThetaRay
Nixpacks
Developer Tools
Build system that turns a source directory into an OCI image, now in maintenance mode
- From
- Free
- Free plan
- Yes
ThetaRay
Cybersecurity
Unsupervised AI transaction monitoring for cross-border and correspondent banking
- From
- On request
- Free plan
- No
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.; 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: Nixpacks covers Automatic language detection, ThetaRay covers Unsupervised detection.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Nixpacks and ThetaRay actually diverge.
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 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.
Nixpacks
- Understanding the build behaviour of a platform that adopted Nixpacks before it was frozennot ThetaRay
- Producing container images from a polyglot monorepo where nobody wants to own several Dockerfilesnot ThetaRay
- Reproducing an existing Railway build locally while planning a migration to Railpacknot ThetaRay
- Comparing what a Nix based builder does differently from a buildpack before choosing a successornot ThetaRay
ThetaRay
- A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot Nixpacks
- A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot Nixpacks
- A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot Nixpacks
- A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot 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.
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
Nixpacks
Free- NixpacksFree
- MIT licensed, no usage limits
- No commercial edition and no support contract
- In maintenance mode, superseded by Railpack
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 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.
Questions people ask
- Is Nixpacks or ThetaRay better?
- Neither clearly leads. Nixpacks 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, Nixpacks or ThetaRay?
- Nixpacks has a free tier; the other does not. Paid plans start at Free for Nixpacks and On request for ThetaRay.
- Does Nixpacks or ThetaRay run on more platforms?
- Nixpacks runs on Linux, macOS, CLI, Docker. ThetaRay runs on Web.
- Can I use Nixpacks for free?
- Yes. Nixpacks has a free tier, so you can try it without paying. ThetaRay starts at On request.
- 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 ThetaRay is typically brought in for.
- What can Nixpacks do that ThetaRay cannot?
- Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.
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.
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.
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.
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.
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.
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.
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.
Related pages
Other head to heads
- Nixpacks vs Depot
- Nixpacks vs Earthly
- Nixpacks vs Cloud Native Buildpacks
- Nixpacks vs Dagger
- Nixpacks vs Nx Cloud
- Nixpacks vs Tilt
- Nixpacks vs Blacksmith
- Nixpacks vs WarpBuild
- Nixpacks vs Namespace
- Nixpacks vs Rust
- Nixpacks vs Ona (formerly Gitpod)
- Nixpacks vs Bazel
- Nixpacks vs ConfigCat
- Nixpacks vs Cortex
- Nixpacks vs Deep Code
- Nixpacks vs Deno
- Nixpacks vs Fig
- Nixpacks vs Feedzai
- Nixpacks vs Unit21
- Nixpacks vs Quantexa
- Nixpacks vs Silent Eight
- Nixpacks vs NICE Actimize
- Nixpacks vs Sardine
- Nixpacks vs Fenergo
- Nixpacks vs Jumio
- Nixpacks vs Featurespace ARIC Risk Hub
- Nixpacks vs Sumsub
- Nixpacks vs iDenfy
- Nixpacks vs Shufti Pro
- Nixpacks vs VMware Carbon Black
- Nixpacks vs Wireshark
- Nixpacks vs WorkOS
- Nixpacks vs Zscaler Internet Access
- Nixpacks vs Milestone XProtect
- Nixpacks vs Osano
- ThetaRay vs Depot
- ThetaRay vs Earthly
- ThetaRay vs Cloud Native Buildpacks
- ThetaRay vs Dagger
- ThetaRay vs Nx Cloud
- ThetaRay vs Tilt
- ThetaRay vs Blacksmith
- ThetaRay vs WarpBuild
- ThetaRay vs Namespace
- ThetaRay vs Rust
- ThetaRay vs Ona (formerly Gitpod)
- ThetaRay vs Bazel
- ThetaRay vs ConfigCat
- ThetaRay vs Cortex
- ThetaRay vs Deep Code
- ThetaRay vs Deno
- ThetaRay vs Fig
- ThetaRay vs Feedzai
- ThetaRay vs Unit21
- ThetaRay vs Quantexa
- ThetaRay vs Silent Eight
- ThetaRay vs NICE Actimize
- ThetaRay vs Sardine
- ThetaRay vs Fenergo
- ThetaRay vs Jumio
- ThetaRay vs Featurespace ARIC Risk Hub
- ThetaRay vs Sumsub
- ThetaRay vs iDenfy
- ThetaRay vs Shufti Pro
- ThetaRay vs VMware Carbon Black
- ThetaRay vs Wireshark
- ThetaRay vs WorkOS
- ThetaRay vs Zscaler Internet Access
- ThetaRay vs Milestone XProtect
- ThetaRay vs Osano