Softwr

Developer Tools · head to head

Nixpacks vs Very Good Security

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
Very Good Security logo

Very Good Security

Cybersecurity

Tokenisation proxy that keeps card and personal data out of your own systems and out of PCI scope

From
$1000/month
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.; Very Good Security vGS sits in the live path of every request carrying sensitive data, so its latency and availability become yours, and an outage in the proxy is a payment outage no matter how healthy your own systems are.
  • They diverge on capability: Nixpacks covers Automatic language detection, Very Good Security covers Aliasing proxy.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nixpacks and Very Good Security actually diverge.

Attributes where Nixpacks and Very Good Security differ
AttributeNixpacksVery Good Security
Starting priceFree$1000/month
Pricing modelOpen source, no licence feePer month
Free tierYesNo
PlatformsLinux, macOS, CLI, DockerWeb, API
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 Very Good Security

  • Aliasing proxy
  • PCI scope reduction
  • Network tokenisation
  • Processor optionality
  • Card issuing data
  • Vault and access controls
  • Data residency options
  • Compliance artefacts

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

Very Good Security

  • A marketplace facing its first PCI DSS Level 1 assessment that wants to keep card data off its own estate rather than harden a dozen servicesnot Nixpacks
  • A merchant negotiating with a second acquirer that needs card credentials portable so the negotiation is real rather than theoreticalnot Nixpacks
  • A fintech collecting bank account and identity documents that wants sensitive fields absent from logs, backups and analytics warehouses by constructionnot Nixpacks
  • A card issuer that must display a full PAN in its own mobile app without the app or its backend touching cardholder datanot 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.

Very Good Security

  • VGS sits in the live path of every request carrying sensitive data, so its latency and availability become yours, and an outage in the proxy is a payment outage no matter how healthy your own systems are.
  • Token portability is the whole selling point yet leaving VGS means migrating tokens back out, a project the vendor has no incentive to streamline, so the lock-in you removed from your acquirer partly moves to VGS.
  • Entry pricing at around one thousand US dollars a month is real money for a pre-revenue fintech, and it buys volume-limited throughput, so cost scales with exactly the growth that made you buy it.
  • Scope reduction is not scope elimination: your QSA still assesses how you integrate, and teams regularly discover that a support tool or an internal admin screen pulled plaintext back in and dragged systems into scope again.
  • Proxy-based interception constrains how you design request flows, and non-standard payloads, streaming uploads or binary formats often need custom routing rules that make debugging production issues noticeably harder.

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

Very Good Security

$1000/month
  • Starter$1000/month
    • Aliasing proxy
    • Vault storage
    • PCI scope reduction
  • Growth$undefined/month
    • Network tokenisation
    • Multiple processors
    • Data residency options
  • Enterprise$undefined/year
    • Custom vault architecture
    • Dedicated support and SLA
    • Contractual compliance coverage

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 Very Good Security if

  • You need aliasing proxy.
  • You work on Web, API.
  • You also want pci scope reduction.
Very Good Security review

Questions people ask

Is Nixpacks or Very Good Security better?
Neither clearly leads. Nixpacks starts at Free and Very Good Security at $1000/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or Very Good Security?
Nixpacks has a free tier; the other does not. Paid plans start at Free for Nixpacks and $1000/month for Very Good Security.
Does Nixpacks or Very Good Security run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. Very Good Security runs on Web, API.
Can I use Nixpacks for free?
Yes. Nixpacks has a free tier, so you can try it without paying. Very Good Security starts at $1000/month.
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 Very Good Security is typically brought in for.
What can Nixpacks do that Very Good Security cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. Very Good Security covers Aliasing proxy, PCI scope reduction, Network tokenisation, Processor optionality.

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.

Very Good Security: Does VGS make me PCI compliant?

No. It removes cardholder data from your systems so your assessment covers a far smaller boundary, but you still complete an assessment and your integration is part of 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.

Very Good Security: Can I move to another processor without re-collecting cards?

Yes, that is a core reason people buy it. The vault reveals stored credentials to whichever processor you route to.

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.

Very Good Security: What does it cost?

Published entry pricing is about one thousand US dollars per month; growth and enterprise tiers are quoted.

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.

Very Good Security: Is it only for card data?

No. The proxy handles any sensitive field, including bank details, national identifiers and documents, though payments is where the product is now focused.

Share

Related pages

More on Nixpacks

More on Very Good Security

Keep looking

Other head to heads