We are preparing for FDA compliance, which requires us to submit the licenses for all software components used in the project.
Our medical software is a .NET application built primarily on ABP.io. As part of the ABP.io layered architecture template (Blazor), several open-source libraries and components are included by default. However, we have learned that not all of these libraries are permitted for commercial use, such as Redis and Blazorise, and others
For example, Redis was licensed under BSD up to version 7.2.4 Final. After version 7.2.4, Redis reportedly no longer allows commercial use unless a business license is purchased from Redis Inc. This is a concern for us because we did not intentionally choose Redis as a standard component; it was included by default with ABP.io. The same concern applies to Blazorise, which also appears to require a commercial license.
Since we have already purchased ABP.io, does that mean the Redis commercial license is also covered?
Please advise on how we should proceed to avoid any license violations. Do we need to remove Redis and replace it with an alternative?
2 Answer(s)
-
0
Please contact us at https://abp.io/contact.
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,
Quick answers to your three points:
ABP commercial license scope: our license covers our own
Volo.*modules only — it doesn't bundle any third-party component license. The one exception is Blazorise: we have an agreement with Megabit, so every ABP commercial customer automatically gets a Blazorise PRO license at no extra cost. Sign in (or register) at https://blazorise.com/account/user/manage/license using the same email as your abp.io account to get your license key and Product Token. Full steps are in https://abp.io/support/questions/9912.Redis: the concern is outdated. Here's the timeline:
- Redis ≤ 7.2.4 — BSD-3-Clause (open source)
- Redis 7.4 / 7.x (from March 2024) — RSALv2 + SSPLv1 dual-license. SSPL primarily restricts cloud providers re-packaging Redis as a managed service.
- Redis 8.0+ (released May 2025) — tri-licensed under RSALv2 + SSPLv1 + AGPLv3. AGPLv3 is OSI-approved open source, so you can use Redis 8.0+ commercially under AGPLv3 with no payment required.
Refs: https://redis.io/blog/agplv3/ and https://redis.io/legal/licenses/.
Also worth noting — the client library we ship is
StackExchange.Redis, which is MIT-licensed and independent from the Redis server license.If you'd still rather not depend on Redis, you can — ABP only depends on the
IDistributedCacheabstraction, so any compatible implementation works as a drop-in replacement.Other built-in libraries: the third-party packages we pull in by default are all under permissive licenses — MIT, Apache 2.0, or BSD-3-Clause (e.g. Newtonsoft.Json, AutoMapper, OpenIddict, Serilog). ABP code is written against interfaces and common abstractions, so if any third-party we depend on ever introduces a license that doesn't fit a commercial customer, we'd switch to an open-source alternative before you hit a problem.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
