Regarding the ABP Commercial license — just wanted to confirm what we found:
- With the purchased ABP Commercial license, we can create any number of projects — there's no limit on the number of applications/solutions we create.
- Once a project is created and development starts, the license is not required for deployment. The deployed application does not perform any license check at runtime.
- So we can do as many deployments as we need (dev, staging, production, client environments) without any additional licensing cost.
The license is tied to development (developer seats), not to the number of projects created or deployments made.
While planning our deployment, we found a license check in the generated project code that validates the license key/validity, and we want to understand its implications. For reference, here is the relevant configuration entry (license code redacted):
{
"AbpLicenseCode": "<YOUR_ABP_LICENSE_CODE>"
}
A few things we'd like to clarify:
- Could you confirm what this check actually does at runtime — does it only run during development/build, or could it affect a deployed/production instance? We want to make sure point 2 above still holds given this code exists in the generated solution.
- What happens if the ABP license is not renewed after it expires — does it affect already-deployed applications, or only new development going forward?
- What happens if the ABP license is downgraded to a lower tier — does that affect existing projects/deployments built under the higher tier, or only what can be created after the downgrade?
Please let us know if this understanding is correct, or if there's anything more we should be aware of.
Thanks!
9 Answer(s)
-
0
Please contact us at https://abp.io/contact.
(Your questions are specifically about ABP Commercial licensing terms—project limits, deployment rights, renewal/downgrade implications, and the runtime behavior/implications of
AbpLicenseCode—which are license/commercial topics that must be confirmed by Volosoft against your subscription.)
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
Point 2 needs a correction — the deployed application does run a license check at startup.
It's a local check: the app validates the
AbpLicenseCodefrom its own configuration, without contacting any ABP server and without needingabp loginon that machine, so it works on an offline server too. But the code has to stay in your production configuration. If it's missing or invalid, you getABP-LIC-ERRORin the logs and the app shuts down.The one case where a deployed instance does call abp.io is when it runs with
ASPNETCORE_ENVIRONMENT=Developmentor with a debugger attached. Keep it onProductionand the online check never runs. These two cover it in detail:https://abp.io/support/questions/817/How-to-delete-current-license-login-session https://abp.io/support/questions/1471/containerizing-abp-application
For your other two questions:
License not renewed: your deployed applications are not affected, they keep running. You can also keep developing your existing projects — ABP licenses are perpetual. What ends is creating new solutions from the pro templates, major/minor upgrades (you still get the patches of your current minor version), installing new pro modules and themes, ABP Suite, ABP Studio's pro features, and premium support. The full list is under "What happens when my license period ends?" on https://abp.io/faq
Downgrade: license plans can't be downgraded. If you need to change your plan, write to info@abp.io
Project count and deployments are both unlimited, and the license is tied to developer seats, not to the number of projects or deployments. One detail on the first point: you can create as many projects as you want while the license is active, and after it expires you can't create new ones, but everything you already have keeps working and can be deployed anywhere.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
also you can check out this link What Happens When My License Period Ends
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
[maliming] said: Hi,
Point 2 needs a correction — the deployed application does run a license check at startup.
It's a local check: the app validates the
AbpLicenseCodefrom its own configuration, without contacting any ABP server and without needingabp loginon that machine, so it works on an offline server too. But the code has to stay in your production configuration. If it's missing or invalid, you getABP-LIC-ERRORin the logs and the app shuts down.The one case where a deployed instance does call abp.io is when it runs with
ASPNETCORE_ENVIRONMENT=Developmentor with a debugger attached. Keep it onProductionand the online check never runs. These two cover it in detail:https://abp.io/support/questions/817/How-to-delete-current-license-login-session https://abp.io/support/questions/1471/containerizing-abp-application
For your other two questions:
License not renewed: your deployed applications are not affected, they keep running. You can also keep developing your existing projects — ABP licenses are perpetual. What ends is creating new solutions from the pro templates, major/minor upgrades (you still get the patches of your current minor version), installing new pro modules and themes, ABP Suite, ABP Studio's pro features, and premium support. The full list is under "What happens when my license period ends?" on https://abp.io/faq
Downgrade: license plans can't be downgraded. If you need to change your plan, write to info@abp.io
Project count and deployments are both unlimited, and the license is tied to developer seats, not to the number of projects or deployments. One detail on the first point: you can create as many projects as you want while the license is active, and after it expires you can't create new ones, but everything you already have keeps working and can be deployed anywhere.
Thanks
Hi,
Thanks for the correction, and for the detail on renewal and downgrade — that part is clear.
One follow-up on continuing to develop existing projects after the license period ends.
You mentioned that ABP licenses are perpetual, so we can keep developing our existing projects. What we're seeing today doesn't quite line up with that. When we clone one of our existing projects onto a fresh machine and install ABP there, running it under
ASPNETCORE_ENVIRONMENT=Developmentasks for the license account — which is exactly the case you described where the online check against abp.io runs.So I'd like to confirm what happens once the subscription has lapsed:
Development mode after expiry — if the developer account is still signed in through
abp loginbut the subscription has not been renewed, does the online check still pass? Or does it fail withABP-LIC-ERRORthe same way a missingAbpLicenseCodewould?New machine after expiry — when we clone an existing project onto a machine that has never had ABP installed:
- does
abp loginstill succeed on a lapsed account? - does NuGet restore of the commercial package versions we already use still work from the private feed?
- does
If Development mode does fail after expiry — is the supported way to keep working locally to run with
ASPNETCORE_ENVIRONMENT=ProductionorStaging? Would we lose any development-time features by doing that?
In short: does "you can keep developing your existing projects" cover the full local development loop — build, run and debug on any machine, including new ones — or only that already-deployed applications keep running?
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
- Your follow-up questions are about ABP Commercial licensing behavior after subscription lapse (login eligibility, private NuGet feed access, and whether Development-mode online checks still pass). These are commercial/license terms & account entitlements, and the only definitive/authoritative confirmation must come from Volosoft.
Please contact us at https://abp.io/contact.
(For reference, ABP’s FAQ entry about end-of-license period is here: https://abp.io/faq#what-happens-when-my-license-period-ends)
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
Development mode keeps working after the license expires. The online check doesn't fail the way a missing
AbpLicenseCodedoes — it passes and the app starts normally.What you hit on the fresh machine is a different thing: in
Developmentthe check needs that machine to be signed in, and a new machine has no CLI session yet. It reportsABP-LIC-ERRORas well, so the two are identical in the logs, but the cause here is only the missing sign-in. Runabp loginthere and it's fine — same before and after expiry.To your three points:
Development after expiry — the check passes. Your license still covers the commercial modules you are using, so existing projects build, run and debug as before.
New machine after expiry —
abp loginstill works on a lapsed account. The per-developer computer limit still applies, and that one is independent of the license state.On the packages: the commercial template writes your organization API key into the solution's
NuGet.Config, so if that file is in your repository a clone brings it along and restore needs no extra setup. The versions you are already on keep restoring after expiry. The Angular packages are on the public npm registry, sonpm installfor those versions isn't affected.Production / Staging — you don't need it, keep running
Developmentlocally. Switching would cost you the development-only behavior of the template, such as the developer exception page, and it wouldn't help while debugging anyway: an attached debugger runs the online check in any environment.
So the normal build, run and debug loop works on a new machine too, once that machine is signed in. The other post-expiry limits from my previous reply still apply.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
That clears up the fresh-machine case, thanks.
One more point, on the developer seats.
We are on three developer seats, and our team composition will change over time - at some point we will remove one developer from the organization and add a different person into that freed seat. We would like to confirm how that works once the license period has ended:
Can we still change the members of the organization after expiry - remove a developer and add a new one into the freed seat - or is member management one of the things that stops when the subscription lapses?
If we can, does the newly added developer get a working
abp loginon a lapsed license, the same way an existing developer does?That developer would be setting up a machine that has never had ABP installed, and cloning our existing project onto it. Will the Development-mode online check pass for them, so they can build, run and debug the existing project like the rest of the team?
In short: after expiry, is "you can keep developing your existing projects" tied to the three seats as a count, or to the three specific people who were holding them while the license was active?
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Please contact us at https://abp.io/contact.
Your specific questions (changing organization members / reassigning seats after the subscription lapses, whether a newly added developer can successfully
abp login, and whether Development-mode online checks will pass for that newly added person) are commercial/account entitlement topics and can only be confirmed definitively by Volosoft for your organization/subscription.(If you want to reference the general policy text, this is the closest official public summary: https://abp.io/faq#what-happens-when-my-license-period-ends)
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
It's tied to the seat count, not to the specific people.
Yes, member management keeps working after expiry. You can remove a developer and add someone else into the freed seat on the organization management page, the same way as while the license is active. The number of seats stays the same.
Yes. Once added, the new developer's
abp loginworks the same way as for the rest of the team.Yes. The Development-mode check passes for them as well, including on a machine that never had ABP installed. The fresh-machine steps from my previous reply are the same for them.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
