Softwr

Developer Tools · head to head

Nixpacks vs Sumsub

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

Sumsub

Cybersecurity

Identity verification and AML screening priced per verification

From
$1.35/verification
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.; Sumsub the published per-verification rate is undercut by a monthly minimum of 149 or 299 dollars, so low volume businesses pay a much higher effective rate than the headline suggests.
  • They diverge on capability: Nixpacks covers Automatic language detection, Sumsub covers Document verification.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Nixpacks and Sumsub actually diverge.

Attributes where Nixpacks and Sumsub differ
AttributeNixpacksSumsub
Starting priceFree$1.35/verification
Pricing modelOpen source, no licence feePer verification
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 Sumsub

  • Document verification
  • AML screening
  • KYB verification
  • No-code flow builder
  • Transaction monitoring
  • Travel Rule
  • Fraud and duplicate detection

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

Sumsub

  • A crypto exchange needing KYC plus Travel Rule handling under one contractnot Nixpacks
  • A gambling operator entering several European markets and needing document coverage without a separate vendor per countrynot Nixpacks
  • A fintech that wants a published price it can model in a business case before speaking to a salespersonnot Nixpacks
  • A marketplace verifying both individual sellers and the companies behind them without buying two productsnot 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.

Sumsub

  • The published per-verification rate is undercut by a monthly minimum of 149 or 299 dollars, so low volume businesses pay a much higher effective rate than the headline suggests.
  • You are billed per verification attempt in most configurations, meaning applicant drop-off and resubmissions cost money without producing a customer.
  • Pass rates and document support vary noticeably by country, and a market that works well in Europe can produce materially worse rejection rates in parts of Africa and South East Asia.
  • The AML screening tier bundles list coverage that large institutions would normally buy separately and tune, giving less control over match thresholds than a dedicated screening vendor.
  • The company originated in Russia before restructuring to a UK entity, and some financial institutions still raise that history in vendor risk review, which can slow or block procurement at conservative banks.

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

Sumsub

$1.35/verification
  • Basic$1.35/verification
    • 149 USD minimum monthly spend
    • Document verification and liveness
    • No-code flow builder
  • Compliance$1.85/verification
    • 299 USD minimum monthly spend
    • Everything in Basic
    • AML sanctions and PEP screening
  • Enterprise$undefined/year
    • Negotiated volume rate
    • Custom jurisdictions and languages
    • Dedicated support

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

  • You need document verification.
  • You work on Web, iOS, Android.
  • You also want aml screening.

Questions people ask

Is Nixpacks or Sumsub better?
Neither clearly leads. Nixpacks starts at Free and Sumsub at $1.35/verification, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or Sumsub?
Nixpacks has a free tier; the other does not. Paid plans start at Free for Nixpacks and $1.35/verification for Sumsub.
Does Nixpacks or Sumsub run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. Sumsub runs on Web, iOS, Android.
Can I use Nixpacks for free?
Yes. Nixpacks has a free tier, so you can try it without paying. Sumsub starts at $1.35/verification.
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 Sumsub is typically brought in for.
What can Nixpacks do that Sumsub cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. Sumsub covers Document verification, AML screening, KYB verification, No-code flow builder.

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.

Sumsub: What does a verification actually cost?

1.35 USD on Basic and 1.85 USD on Compliance, but with 149 and 299 USD monthly minimums respectively. Below roughly 110 or 160 checks a month you are paying the minimum, not the rate.

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.

Sumsub: Do failed verifications get charged?

Attempts are generally billable, so a poor onboarding funnel raises your bill. Confirm the exact resubmission policy in your contract.

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.

Sumsub: Does it cover business verification?

Yes, KYB with company registry lookups and beneficial owner resolution is part of the platform rather than a separate product.

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.

Share

Related pages

Other head to heads