Regira-Packages

Licensing

Regira packages use a split licensing model designed to stay out of your way: most packages are Apache-2.0, and the handful that fund the project carry a commercial license with a built-in free tier.

At a glance

Packages License Key needed?
Everything except the nine below Apache License 2.0 Never — these packages contain no license validation and no runtime limits
Regira.Licensing, Regira.Entities.EFcore, Regira.Entities.DependencyInjection, Regira.Entities.Web, Regira.Entities.Mediator, Regira.Entities.Mapping.Mapster, Regira.Entities.Mapping.AutoMapper, Regira.Entities.Validation.FluentValidation, Regira.Office.Clients Regira Commercial License Only beyond the free tier

The front-end library @regira/modules (npm) is also Apache-2.0. The hosted services (services.regira.com) and the MCP server follow the commercial model with rate-limited free tiers.

The free tier

The free tier applies automatically — no payment, no registration, no key:

Product Free-tier limit
regira.entities 5 simple + 2 complex entity registrations per application
regira.services 5 requests per 60 seconds
regira.mcp 30 requests per 60 seconds

A registration is simple when it is made without custom sort or include type parameters (For<Product>(), For<Product, int, ProductSearchObject>(...)), and complex when it specifies them (For<Order, int, OrderSearchObject, OrderSortBy, OrderIncludes>(...)).

For any given released version, the free tier as shipped in that version remains available without time limit.

Commercial licenses

A license key removes the free-tier limits. Keys are validated fully offline with an RSA-signed token — no phone-home, no telemetry (the validation code is public: Regira.Licensing).

One key can cover multiple products; when several keys are registered, the best license per product wins (a key for the running major first, then paid over free). A key is valid for the major version it was issued for, a non-expiring key included, so a new major needs a new key. In-process packages refuse a key for another major at startup; the hosted services and the MCP server apply the free tier instead.

Registering a key

Register once, before module setup:

services.UseRegira(configuration);   // reads Regira:LicenseKeys from configuration
// or
services.UseRegira(licenseKey);      // pass keys explicitly
{
  "Regira": {
    "LicenseKeys": [ "<your-license-key>" ]
  }
}

UseRegira reports each registered key in one line, on the console when it runs and through ILogger (category Regira.Licensing) when the host starts:

[Regira] License — Customer: … | Products: … | Version: 6 | Issued: … | Expires: … | Limits: …

Version is the major the key is bound to: any for a key without a version, unreadable for a version that cannot be read. Regira Entities then logs Regira.Entities: n simple / n complex registered → tier = ….

FAQ

Questions: b2b@regira.com or the contact form.