Nx logo
Verified by SaaSOffers
PremiumDeveloper & IT

Nx Coupon: Free Plan

Free Plan
Verified November 2026

Smart monorepo build system with caching, task orchestration, and CI optimization.

Sign up to unlock

Premium: $79/year for unlimited deals

✓ Verified deal✓ No spam, ever✓ 10,000+ startups

Deal Highlights

Free Plan
Deal Value
Premium Plan
Access Type
Developer & IT
Category

Our Nx listing: the Free Plan, which is Nx Cloud Hobby

Offer: Free Plan. Our listing sets no requirements, there is no promo code, and there is no special SaaSOffers link. You sign up at nx.dev.

We checked these plans and prices against Nx's official pricing and help pages in November 2026.

Nx is a build system for monorepos. The Nx tool itself runs on your machine and in your CI. Nx Cloud is the paid hosted service that adds a shared remote cache, task distribution across CI machines, analytics and an AI step that proposes fixes for failed pipelines. The "Free Plan" in our listing is the Hobby plan of Nx Cloud, which nx.dev lists as "Free forever" with no credit card required.

Hobby has no startup conditions attached. We looked for an Nx startup program on nx.dev and found none. The pricing page links an open source special offer form that redirects to a Google Form. We could not read its terms, so we cannot say what it grants. If your repository is public, ask Nx about it before you pay.

Hobby gives you 50,000 credits a month, and credits are the whole meter

Nx Cloud bills in credits. nx.dev lists these Hobby limits:

  • 50,000 credits, reset monthly
  • 5 complimentary contributors
  • 10 concurrent CI connections
  • All worker resource types
  • Basic analytics
  • Community support

A contributor is anyone who authored a commit in a CI pipeline execution during the billing cycle. A bot or a part-time contractor who pushes through CI counts the same as a full-time engineer.

Credits are spent on three things. Each CI pipeline execution costs 500 credits. Each resource usage report costs 10 credits. Compute on Nx Cloud workers costs credits per minute, set by machine size. The credit reference lists these Linux AMD64 rates:

Resource classSizeCredits per minute
Small1 vCPU5
Medium2 vCPU10
Large4 vCPU20
Extra large8 vCPU40

Linux ARM64 starts at Medium: 13 credits per minute for 2 vCPU, 26 for 4 vCPU and 52 for 8 vCPU. The one Windows class, Medium with 3 vCPU and 6 GB of RAM, costs 40 credits per minute. Every Linux agent has a 25 GiB disk, and Enterprise can ask for larger ones.

The self-healing step is metered by tokens, not minutes: 6,555 credits per 1 million input tokens and 32,700 credits per 1 million output tokens.

nx.dev does not publish Hobby overage rates. What happens when the 50,000 credits run out is not stated on the pages we could read, so treat it as unverified and plan to stay inside the allowance.

How far 50,000 credits goes

The 500-credit execution fee comes first. If you spent nothing on compute, 50,000 credits would cover 100 pipeline executions a month (50,000 divided by 500).

Add compute and the number drops. Take one pipeline that runs 20 minutes on one Medium Linux agent: 20 x 10 = 200 credits, plus 500 for the execution and 10 for the usage report, which is 710 credits. 50,000 divided by 710 is 70 runs a month. A team that merges 3 pull requests a day and runs CI about twice on each is already at roughly 130 runs. That team needs the paid plan, or fewer CI runs.

The $29 Team plan is mostly a credit wallet

Team costs $29 a month. nx.dev describes it as Hobby plus $29 of included usage credit and email support. Beyond that you pay for add-ons:

ItemPrice
Extra credits$5.50 per 10,000 credits
Extra contributor$19 per contributor
Extra concurrent CI connection$2.25 per connection

nx.dev publishes no annual price.

PlanBilled monthlyKey limits
Hobby$050,000 credits, 5 contributors, 10 concurrent CI connections, community support
Team$29$29 of included credit, then $5.50 per 10,000 credits, $19 per extra contributor, $2.25 per extra connection
EnterpriseCustomVolume discounts, 99.9% uptime SLA, static IPs, Private Links, corporate SSO, SCIM, CI observability

At $5.50 per 10,000 credits, one credit costs $0.00055. A Medium Linux minute at 10 credits costs $0.0055. GitHub's own 2-core Linux runner is $0.006 a minute, and Nx's own pricing note compares the two for that reason. At 8 vCPU both land at $0.022 a minute (40 credits x $0.00055).

What Hobby does not include

  • Email support. Hobby gets community support only. Team adds email support.
  • Any included credit past 50,000. Team's extra is $29 of credit, which at the overage rate is about 52,700 credits if you read it at face value, so it roughly doubles the allowance.
  • Enterprise items: a 99.9% uptime SLA, priority support, static IPs, Private Links, corporate SSO, SCIM and volume discounts.
  • Single-tenant or self-hosted installation. The pricing page marks single-tenant for some distribution features, and self-hosted for Enterprise setups.
  • Per-plan marking in the feature table. nx.dev's comparison grid lists Self-Healing CI, Ultracache, conformance rules and others by category but did not show which plan has each one when we read it. Only Ultracache is confirmed as included in Hobby, from the remote cache page.

Ultracache hashes a task by the files it actually read, recorded in Nx Cloud, instead of only the inputs you declared. Nx's page says it can cut CI compute "up to 3x in some cases". It needs Nx 24.0.0 or later for CI by default, it is included in every plan including Hobby, and traced tasks do not use credits.

Remote caching is the part most people use

Run npx nx@latest connect and Nx links your workspace to Nx Cloud. After that, a task that one person or one CI job already ran is restored from the cache on every other machine. Nx replays the terminal output and the declared output files without running the task again.

Each cache entry stores terminal output, the files matched by outputs and the task hash. Source input files are not stored. Entries are immutable once written.

The security model is token based. Read-write tokens go on protected branches such as main. Read-only tokens go everywhere else, and pull request writes are isolated from the main cache. Nx's page ties this design to CREEP (CVE-2025-36852). End-to-end encryption is available, with keys that Nx Cloud never sees. If Nx Cloud is unreachable, Nx still uses local cache hits and runs the rest.

If you do not want a vendor at all, Nx documents a self-hosted remote cache: any server that follows its OpenAPI specification will work. That route costs you hosting and maintenance, and it is a legitimate answer for a team with one platform engineer and a firm no-new-vendor rule.

What a CI run costs, using Nx's own math

Nx published a cost note comparing plain GitHub Actions to Nx Cloud on GitHub-hosted runners. Its figures for private repositories:

RunnerPer minute
Linux x64, 2 cores$0.006
Linux x64, 4 cores$0.012
Linux x64, 8 cores$0.022
Linux x64, 16 cores$0.042
Linux arm64, 2 cores$0.005
macOS, 3 to 4 cores$0.062

GitHub's included minutes are 2,000 on Free, 3,000 on Pro and Team, and 50,000 on Enterprise Cloud. Standard runners on public repos and self-hosted runners cost nothing.

Nx's note says each run costs $0.275 in credits (500 credits), plus 10 credits for each machine's usage report. Its worked cases, all at 500 runs a month:

  • Four-job matrix on 2-core runners, 120 machine-minutes per run, plain: $360.00 a month. With Nx at 50% of task time cached: $364.50. With 70% cached: $304.50, a 15% saving.
  • Eight-job matrix on 8-core runners, 160 machine-minutes per run, plain: $1,760.00. With Nx at 50% cached: $1,303.50, a 25% saving. At 70% cached: $1,039.50, a 40% saving.
  • One 30-minute job on one 2-core runner: about $90 a month plain, about $195 with Nx at 50% cached, though it finishes in 18 billed minutes instead of 30.

So the dollar saving depends on the cache hit rate and on how many machines you run. Small jobs on cheap runners can cost more with Nx. Wall-clock time is where the first example wins: 30 minutes falls to 17.5 at 50% cached and 12.1 at 70%.

Worked example: a 5-person team

Five engineers is exactly the Hobby contributor allowance. Say the team triggers 100 CI runs a month, and each uses one Medium Linux agent for 20 minutes.

  • Per run: 500 (execution) + 200 (20 x 10) + 10 (report) = 710 credits.
  • Per month: 100 x 710 = 71,000 credits.
  • Hobby covers 50,000. The gap is 21,000 credits.
  • If Team keeps Hobby's 50,000 credits, the 21,000 extra cost $11.55, inside the $29 credit, so the bill is $29. If every credit is billed, as in Nx's cost note, it is $39.05.

If the team stays under about 70 runs, it pays $0 on Hobby.

Worked example: a 10-person team

Ten engineers, 500 CI runs a month, same 710-credit run.

  • Credits: 500 x 710 = 355,000, or 35.5 x $5.50 = $195.25.
  • Contributors: Hobby includes 5. If Team keeps those 5 as complimentary, 5 extras cost 5 x $19 = $95. If it does not, 10 x $19 = $190. The pricing page does not say which.
  • Connections: assume 20 concurrent CI connections. Hobby's 10 are covered, and 10 extra x $2.25 = $22.50. Whether Team resets that count is also unstated.
  • Total: $195.25 + $95 + $22.50 = $312.75 a month in the best reading, or $407.75 in the other.

Self-healing CI, in plain terms

Add npx nx fix-ci as a step in your main CI job, set to run even when earlier steps fail. If every task passes, it does nothing. If something fails, Nx proposes a fix and posts it on the pull request, or sends it to Nx Console in VS Code, Cursor or WebStorm. You apply the fix from the PR comment, from the editor, or from the Nx Cloud UI. nx apply-locally <fix-identifier> pulls it onto your machine to tweak.

Cost: it spends credits by token, at the rates listed above. The pricing page does not mark which plans include it, so confirm before building a workflow on it with Hobby.

Who this suits

  • A team with 5 or fewer committers in CI and a monorepo of a few apps and libraries. Hobby covers you at $0.
  • A project where CI feels slow because every pipeline rebuilds things nobody changed. Remote caching fixes that first.
  • A team on Turborepo or plain npm workspaces that wants affected-task detection, generators and a graph view in one tool.
  • A company whose CI bill is mostly Linux minutes on GitHub-hosted runners and whose cache hit rate would clear 50%.

Who Nx is not for

  • A single-package repository. There is nothing to cache across projects.

  • A team of 6 or more committers that will not pay. You exceed the 5 complimentary contributors.

  • Teams that need SSO, SCIM, static IPs or an uptime SLA. Those are Enterprise.

  • Teams that run macOS or Windows jobs heavily. Windows Medium is 40 credits a minute, four times Linux Medium, and macOS jobs bill at $0.062 a minute on GitHub.

Nx against other monorepo and CI tools

ToolFree plan (published)Paid price (published)Note
Nx CloudHobby: 50,000 credits, 5 contributorsTeam $29/month plus usageCredits for compute and executions
TurborepoVercel Remote Cache is free on all plans, even if you do not host on VercelNot listed on the page we readHMAC-SHA256 artifact signing, self-hosting via the Remote Cache API
DepotNone, 7-day trialDeveloper $20/month, Startup $200/monthRunners at $0.006 a minute for 2 vCPU Linux
CircleCI30,000 credits a month, up to 5 usersPerformance from $15/month10 credits a minute on Linux Medium

Depot and CircleCI prices were checked in November 2026. Turborepo's remote cache is the closest like for like. Its page gives no speedup numbers, no task distribution and no credit meter. Nx Cloud has task distribution and a hosted AI fixer, and charges for them. If all you need is shared caching, Turborepo's cache is free.

Setting up without wasting credits

  1. Give protected branches a read-write token and every other branch a read-only token.
  2. Check --skipRemoteCache exists for debugging. It skips the cache for one command.
  3. Put nx affected in CI so only touched projects run. Nx runs 3 tasks at a time by default.
  4. Watch the credit meter for a week before turning on distribution. Each worker agent writes its own 10-credit usage report.

How to get the Nx offer

  1. Go to nx.dev and open the pricing page. Our listing has no special link or code.
  2. Create an Nx Cloud workspace on the Hobby plan. No credit card is needed.
  3. Run npx nx@latest connect in your repository.
  4. Keep the number of CI authors at 5 or fewer, and watch the 50,000-credit allowance.
  5. If your repository is public, ask Nx about its open source form before paying for Team.

Who Is This Deal For?

Early-Stage Startups

Seed and pre-seed companies looking to move fast without overspending on tools.

Growing SaaS Teams

Series A+ companies scaling their stack and optimizing software costs.

Solo Founders

Indie hackers and bootstrapped founders who need enterprise tools at startup prices.

Get Free Plan off Nx

Premium deal. Upgrade once, unlock everything.

Sign Up & Claim

Frequently Asked Questions

Everything you need to know about this startup deal.

Get the weekly deals digest

New verified startup deals every week. No spam, ever. Unsubscribe anytime.