Softwr

Developer Tools · head to head

Nixpacks vs Semperis

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

Semperis

Cybersecurity

Identity threat detection and Active Directory forest recovery for AD, Entra ID and Okta, from a privately held US vendor.

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.; Semperis scope is limited to Active Directory, Entra ID and Okta, so an organisation whose critical identity lives elsewhere gets little from it, and the recovery value declines in direct proportion to how much has already moved off on-premises AD.
  • They diverge on capability: Nixpacks covers Automatic language detection, Semperis covers Active Directory Forest Recovery.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nixpacks and Semperis actually diverge.

Attributes where Nixpacks and Semperis differ
AttributeNixpacksSemperis
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, CLI, DockerWeb
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 Semperis

  • Active Directory Forest Recovery
  • Malware-free restore
  • Replication-stream monitoring
  • Automated rollback
  • Attack indicator scoring
  • Entra ID and Okta coverage
  • Purple Knight
  • Forest Druid

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

Semperis

  • An organisation that cannot answer an auditor or insurer asking how long it would take to rebuild Active Directory after a destructive attacknot Nixpacks
  • Post-incident recovery where domain controllers are compromised and restoring from system-state backup would reintroduce the attacker's footholdnot Nixpacks
  • Continuous detection of privileged group changes and directory-level tampering that domain controller security logs missnot Nixpacks
  • Hybrid estates where AD, Entra ID and Okta all matter and no single tool currently shows changes across the threenot 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.

Semperis

  • Scope is limited to Active Directory, Entra ID and Okta, so an organisation whose critical identity lives elsewhere gets little from it, and the recovery value declines in direct proportion to how much has already moved off on-premises AD.
  • The licence buys tooling, not a proven runbook: forest recovery is only worth what your last rehearsal demonstrated, and a plan that has never been executed end to end in a lab is an untested assumption regardless of what was purchased.
  • It overlaps with backup and directory management products from Quest, Veeam, Commvault and others, so the buyer must argue internally why a dedicated product is needed alongside a backup contract that already claims to protect Active Directory.
  • Running Directory Services Protector well requires someone who understands AD internals, replication metadata and Tier 0 attack paths, and without that person the alerts on privileged changes are either ignored or auto-reverted in ways that break legitimate administration.
  • Licensing is driven by identity object counts, so directories carrying years of stale user accounts and service principals pay for objects that should have been deleted, and the cleanup project that would reduce the bill is the one nobody has time for.

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

Semperis

On request

No published plan breakdown. See the Semperis review.

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.

Choose Semperis if

  • You need active directory forest recovery.
  • You also want malware-free restore.

Questions people ask

Is Nixpacks or Semperis better?
Neither clearly leads. Nixpacks starts at Free and Semperis at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or Semperis?
Nixpacks has a free tier; the other does not. Paid plans start at Free for Nixpacks and On request for Semperis.
Does Nixpacks or Semperis run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. Semperis runs on Web.
Can I use Nixpacks for free?
Yes. Nixpacks has a free tier, so you can try it without paying. Semperis 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 Semperis is typically brought in for.
What can Nixpacks do that Semperis cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. Semperis covers Active Directory Forest Recovery, Malware-free restore, Replication-stream monitoring, Automated rollback.

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.

Semperis: Does this replace my backups?

No. It replaces the Active Directory recovery procedure specifically. You still need backups for everything else, and the point of Semperis is that a generic system-state backup of a domain controller is a poor way to recover a forest because it restores the operating system along with whatever compromised 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.

Semperis: Is it useful if we are cloud-only on Entra ID?

Partly. Directory Services Protector covers Entra ID and Okta for change tracking and posture, but the forest recovery product, which is the strongest reason to buy, applies to on-premises Active Directory. A genuinely cloud-only organisation should weigh it against Microsoft's own tooling.

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.

Semperis: Are Purple Knight and Forest Druid really free?

Yes, both are free downloads with no licence requirement, and they are widely used by organisations that are not Semperis customers. They are also, transparently, the top of the sales funnel.

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.

Semperis: How long does forest recovery actually take?

The honest answer is whatever your rehearsal took. The vendor's case is hours instead of days, and automation genuinely removes most manual steps, but the number that matters for your board is the one from a test in your own environment.

Semperis: Does it require agents on domain controllers?

It collects directory changes from the AD replication stream, which is what lets it see changes that bypass the security log. Deployment details vary by product and version, so confirm the exact architecture against your domain controller change-control rules.

Share

Related pages

Other head to heads