Softwr

Developer Tools · head to head

Nixpacks vs Semgrep

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
Semgrep logo

Semgrep

Cybersecurity

Open-source static analysis tool for finding security bugs and enforcing code standards.

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • 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.; Semgrep free tier caps out at 10 contributors and 10 repositories.
  • They diverge on capability: Nixpacks covers Automatic language detection, Semgrep covers Static code scanning.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nixpacks and Semgrep actually diverge.

Attributes where Nixpacks and Semgrep differ
AttributeNixpacksSemgrep
Pricing modelOpen source, no licence feefreemium
PlatformsLinux, macOS, CLI, Dockerweb, api, linux, mac, windows
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 Nixpacks

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

Only in Semgrep

  • Static code scanning
  • Supply chain scanning
  • Secrets detection
  • Cross-file analysis
  • AI-powered triage and remediation
  • CI/CD integration

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 Semgrep
  • Producing container images from a polyglot monorepo where nobody wants to own several Dockerfilesnot Semgrep
  • Reproducing an existing Railway build locally while planning a migration to Railpacknot Semgrep
  • Comparing what a Nix based builder does differently from a buildpack before choosing a successornot Semgrep

Semgrep

  • Scanning code for security vulnerabilities in CI/CDnot Nixpacks
  • Detecting vulnerable open-source dependenciesnot Nixpacks
  • Finding hardcoded secrets before code shipsnot Nixpacks
  • Enforcing custom code standards with rule setsnot Nixpacks
  • Prioritizing findings with AI-assisted triagenot 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.

Semgrep

  • Free tier caps out at 10 contributors and 10 repositories.
  • Secrets scanning is priced as a separate module ($15/contributor) from Code and Supply Chain.
  • Self-managed repositories and custom CI/CD require the Enterprise tier.
  • AI credits are limited per tier and additional usage requires upgrading.

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

Semgrep

Free
  • FreeFree
    • Up to 10 contributors
    • Code and Supply Chain scanning
    • 60 AI credits total
  • Teams$30/month
    • Code, Supply Chain, or Secrets scanning per contributor
    • Pro rules
    • AI-powered triage and remediation
  • Enterprise$undefined/month
    • On-prem support
    • Custom CI/CD
    • 50 AI credits per developer/month

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 Semgrep if

  • You need static code scanning.
  • You want to start without paying.
  • You work on web, api, linux, mac, windows.
  • You also want supply chain scanning.
Semgrep review

Questions people ask

Is Nixpacks or Semgrep better?
Neither clearly leads. Nixpacks starts at Free and Semgrep at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or Semgrep?
Nixpacks starts at Free and Semgrep at Free.
Does Nixpacks or Semgrep run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. Semgrep runs on web, api, linux, mac, windows.
Can I use Nixpacks for free?
Both have a free tier, so you can try either at no cost before committing.
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 Semgrep is typically brought in for.
What can Nixpacks do that Semgrep cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. Semgrep covers Static code scanning, Supply chain scanning, Secrets detection, Cross-file analysis.

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.

Semgrep: What does Semgrep cost?

The Free edition covers up to 10 contributors; Teams starts at $30/contributor/month for Code scanning (Supply Chain also $30, Secrets $15); Enterprise is custom-priced.

Source
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.

Semgrep: Is there a free plan, and what are its limits?

Yes, the Free edition supports up to 10 contributors and 10 repositories with Code and Supply Chain scanning plus 60 AI credits total.

Source
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.

Semgrep: How is usage metered?

Pricing is per contributor, defined as someone who made at least one commit to a scanned private repository in the past 90 days.

Source
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.

Semgrep: Is there special pricing for startups?

Yes, Semgrep offers special startup pricing upon request for early-stage companies.

Source
Share

Related pages

More on Nixpacks

More on Semgrep

Keep looking

Other head to heads