We are aware that the free version of Nexus (Nexus OSS) has a limit set at 100,000 components. However, upon checking our current usage, we found that we are already storing over 110,000 components.
Therefore, for our migration to version 3.79.1, our plan was to bypass this restriction by migrating the bundled DB from H2 to PostgreSQL. (The official guide states that this limit can be avoided by using PostgreSQL.)
However, after actually performing the migration, the message “Starting March 23, 2026, new components cannot be added. Purchase a license to remove limits, or if you have already purchased a license upload it here.” was displayed, and we are currently unable to add any more resources to Nexus.
Is there any official statement confirming that the limit cannot be removed without using the paid version?
Hi! There are a few things to talk about here. Let’s go through them one-by-one.
First, the free version of Nexus Repository is what we call “Community Edition.”
The 100,000 component limit you were warned about isn’t actually a limit. At around 100,000 components, your Nexus Repository will suggest you move to Postgres for stability and performance reasons. The H2 database isn’t meant to handle that many components. The Nexus Repository UI is just warning you that moving to Postgres will result in better performance, and you’ve already migrated – good job!
But there is a limit to be aware of. Community Edition permits 40,000 total components or 100,000 requests per day. If you’re over either of those limits, you get a grace period where operations continue as normal – that’s why the message says “March 23,” over a month away.
On March 23rd, if your total number of components is still above 40,000, you won’t be able to add new components. It’s a limitation of Community Edition. It has nothing to do with your database. Either remove components down to 40,000 (cleanup policies can help!) or think about purchasing a Pro license.
You’ll notice that I edited your original post to remove references to a configuration option. That option does not remove the limit. There is no configuration option for bypassing the limits imposed by Community Edition without upgrading to Pro. The limits aren’t a feature flag or configurable telemetry switch.