Softwr

Developer Tools · head to head

Nixpacks vs TeamCity

Nixpacks logo

Nixpacks

Developer Tools

Build system that turns a source directory into an OCI image, now in maintenance mode

From
Free
Rated
-
Full reviewWebsite
TeamCity logo

TeamCity

Software Development

JetBrains continuous integration and delivery server

From
Free
Rated
-
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.; TeamCity detailed pricing requires visiting a calculator and isn't transparent on the main pricing page.
  • They diverge on capability: Nixpacks covers Automatic language detection, TeamCity covers Build Chains.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nixpacks and TeamCity actually diverge.

Attributes where Nixpacks and TeamCity differ
AttributeNixpacksTeamCity
Pricing modelOpen source, no licence feefreemium
PlatformsLinux, macOS, CLI, Dockerweb, windows, mac, linux, api
CategoryDeveloper ToolsSoftware Development

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 TeamCity

  • Build Chains
  • Parallel Test Execution
  • VCS Integration
  • Build History & Analytics
  • Docker & Kubernetes Support
  • Access Control

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

TeamCity

  • Running build and test pipelines for enterprise software teamsnot Nixpacks
  • Self-hosting CI/CD infrastructure behind a firewallnot Nixpacks
  • Coordinating multi-stage build chains with dependenciesnot Nixpacks
  • Scaling build capacity with additional agentsnot 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.

TeamCity

  • Detailed pricing requires visiting a calculator and isn't transparent on the main pricing page.
  • Self-hosted setup and agent management require more operational overhead than fully managed CI/CD services.
  • Additional build agents and users are priced incrementally, which can add up for larger teams.
  • The UI and configuration model have a steeper learning curve compared to YAML-first CI tools.

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

TeamCity

Free
  • Free TierFree
    • Includes 3 build agents
    • 100 build configurations
    • On-premises or Cloud
  • TeamCity Cloud / On-Premises$undefined/month
    • Priced per additional build agent
    • Additional users on Cloud plans
    • Enterprise support options

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

  • You need build chains.
  • You want to start without paying.
  • You work on web, windows, mac, linux, api.
  • You also want parallel test execution.
TeamCity review

Questions people ask

Is Nixpacks or TeamCity better?
Neither clearly leads. Nixpacks starts at Free and TeamCity at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or TeamCity?
Nixpacks starts at Free and TeamCity at Free.
Does Nixpacks or TeamCity run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. TeamCity runs on web, windows, mac, linux, api.
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 TeamCity is typically brought in for.
What can Nixpacks do that TeamCity cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. TeamCity covers Build Chains, Parallel Test Execution, VCS Integration, Build History & Analytics.

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.

TeamCity: How much does TeamCity cost?

TeamCity offers a free download option but specific pricing for commercial use is not detailed on the website. Customers must contact JetBrains for licensing and pricing information.

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.

TeamCity: Is TeamCity free to use?

TeamCity has a free option available for download, but full pricing and licensing details require contacting JetBrains directly.

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.

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

More on Nixpacks

More on TeamCity

Keep looking

Other head to heads