How the Nodinite Portal Works
Unlock the full potential of the Nodinite Portal—a secure web platform for partners, customers, and users to download Nodinite binaries, manage product keys, and onboard new organizations.
✅ Secure registration and onboarding for partners, customers, and users
✅ Download the latest Nodinite binaries for your environment
✅ Effortless product key management and contract compliance
✅ Choose the right runtime environment for each Nodinite installation
✅ Streamlined approval and support from Nodinite admins
The Nodinite Portal is designed for secure, role-based access. Each actor has specific responsibilities and approval steps to ensure compliance, security, and a smooth experience.
Portal and Support are part of the same web application, and both are authenticated through login.nodinite.com with Azure Entra ID.
- User – The main actor who interacts with the portal. Is either a Partner or associated with one or more Customers.
- Customer – An organization that uses Nodinite and is associated with a single Partner. Customers can request product keys and download binaries if there is an active contract.
- Partner – A company that manages multiple Customers and can create new ones. Partners can create trial product keys and request non-trial keys if there is an active contract.
- Nodinite Admin – Oversees registrations, approves Partners, maintains contracts, and grants rights.

Example of the start screen after logging into the Nodinite Portal.
Choose Runtime Environment for Nodinite 7
Review the Runtime Environments Overview page for the full comparison. You must choose the target runtime and configure it before downloading.
Runtime Environment Options
| Runtime environment | Platform type | Current scope | Authentication | Deployment artifact |
|---|---|---|---|---|
| Windows Server (IIS) | Traditional host runtime | Core Services and agents | Windows or OAuth 2.0/OpenID Connect | CLI installer from Portal ZIP |
| Docker Compose | Container runtime | Core Services only | OAuth 2.0/OpenID Connect | Configuration ZIP + readme + container images |
| Kubernetes | Container orchestrator | Core Services only | OAuth 2.0/OpenID Connect | Configuration ZIP + readme + Helm guidance |
| OpenShift | Kubernetes distribution | Core Services only | OAuth 2.0/OpenID Connect | Configuration ZIP + readme + Helm guidance |
| Azure Container Apps | Managed Kubernetes service | Core Services only | OAuth 2.0/OpenID Connect | Configuration ZIP + readme + Bicep + az guidance |
For container runtimes, the Portal provides a customer-specific configuration ZIP (for each Environment). Use the runtime overview page for the container delivery model and authentication baseline.
User
A User is the main actor interacting with the Nodinite Portal. Users must register with a company email address (personal domains like gmail.com/outlook.com are generally not approved). A User is associated with either one Partner or multiple Customers. Users without any association can only download Nodinite 6 binaries. Once registered, contact our Support to get associated with a Partner or [Customer]. Read more on the Support page. (#fa-user-group-crown-customer). Nodinite admins can grant additional rights, such as creating product keys or adding and managing environments for Nodinite version 7.
User registration and association workflow in the Nodinite Portal.
Step-by-Step: User Actions
- Register your personal account with your company email address.
- Contact Nodinite support to be associated with a Partner or Customer.
- Download Nodinite binaries (v6 or v7 based on association).
- Request additional rights for product key creation or Environment management if needed.
Login to the Portal
To log in to the Nodinite Portal, navigate to the Nodinite Portal. Sign-in is handled by login.nodinite.com for both Portal and Support.

Example of the Nodinite Portal login screen.
Register a New Account
If you do not have an account, click the "Sign up now" link to create a new account using your company email address. The registration flow has changed, and we are now using a new support experience. The database behind the portal is the same as before, so no customer data was lost, but users must re-register for the new support and portal workflow.
Use your existing company email details when registering, even if you previously used the old support system. Do not use this as an opportunity to create a second identity; the new support experience is a refresh of the same account model, not a brand-new customer database.

Example of the sign-up screen for the new portal registration flow.

Example of the additional account details required during portal registration.
After you submit the form, complete the confirmation step and verify the account through the code or email flow shown in the portal.

Example of the confirmation step used to validate the new support and portal account.
Once approved, the portal will present the requested permissions and onboarding state for the account. This is the new support workflow and is expected before you can continue with product access or support requests.

Example of the requested permissions screen displayed during the updated registration and onboarding flow.
Note
For support and help requests, use the dedicated Support Portal instead of email. The underlying database is the same as before, but you must register a new account in the new support experience. Old tickets remain in the legacy system, and new requests must be submitted in the new portal going forward.
Note
Please use your first and last name as Display name when registering. This helps us identify you and associate you with the correct organization.
Customer
A Customer is an organization that uses Nodinite and is associated with a single Partner. A Customer must have an active contract maintained by Nodinite admins to acquire a non-trial product key. Individual Users can be associated with multiple Customers. A Partner can create new Customers in the portal and issue trial product keys. Nodinite admins maintain contracts and grant rights as needed. To manage an Environment for Nodinite version 7, the Customer must have an active contract, and the User must be granted rights by a Nodinite admin.
Customer onboarding and product key management workflow in the Nodinite Portal.
Step-by-Step: Customer Actions
- Register with your personal company email address. Navigate to the Nodinite Portal.
- Wait for portal review and association with your Partner.
- Download Nodinite binaries once approved.
- Request product keys as needed (requires admin rights).
- Contact Nodinite support for additional rights or contract questions.
Partner
A Partner manages customer creation, product key requests, and environment setup. Partners must be registered and approved by Nodinite admins. Partners can create new Customers and spawn trial product keys. To create non-trial keys, there must be an active contract for the Customer, maintained by Nodinite admins. A Partner can be associated with many Customers.
Partner registration and customer management workflow in the Nodinite Portal.
Step-by-Step: Partner Actions
- Login with your User account.
- If your organization is not listed, contact Nodinite support for manual approval.
- Create new Customers and manage their associations.
- Create trial product keys for POC Customers.
- Create non-trial keys when contracts are active.
- Set up new environments for Nodinite v7 (if granted rights).
- Download Nodinite binaries as needed.
Nodinite Admin
Nodinite admins oversee registrations, approve Partners, maintain contracts, and grant rights for key creation and environment management. They ensure compliance and provide support for all portal users. Admins must manually review and approve new Partners, add them to the portal, and manage associations and contracts behind the scenes.
Admin approval and contract management workflow in the Nodinite Portal.
Step-by-Step: Nodinite Admin Actions
- Review and approve Partner, Customer, and User registrations.
- Add new Partners to the portal as needed.
- Associate Users and Customers with Partners.
- Maintain and update Customer contracts.
- Grant rights for product key creation and environment management.
- Provide support and ensure compliance.
Feature Matrix – What You Can Do in the Nodinite Portal
| Feature | Partner | Customer | User | Nodinite Admin | Requirement/Note |
|---|---|---|---|---|---|
| Register in Portal | ✅ | Company email required | |||
| Download Nodinite v6 binaries | ✅ | ✅ | ✅ | ✅ | Must be registered |
| Download Nodinite v7 binaries | ✅ | ✅ | ✅ | ✅ |
|
| Create trial product keys | ✅ | ✅ | Self-service | ||
| Create rental product keys | ✅ | ✅ | ✅ | ✅ | Self-service
|
| Create new Customer | ✅ | ✅ | Partner must be approved | ||
| Create new Environments (v7) | ✅ | ✅ | ✅ | ✅ |
|
| Create new Partner | ✅ | Nodinite Admin action | |||
| Associate User with partner | ✅ | Nodinite Admin action | |||
| Associate User with multiple customers | ✅ | Nodinite Admin action | |||
| Maintain Customer Contracts | ✅ | Nodinite Admin action | |||
| Grant rights for key/environment creation | ✅ | Nodinite Admin action | |||
| Delete Partner/Customer/User/Contract | ✅ | Nodinite Admin action |
Note
To get elevated rights, contact the Nodinite Support page. As some of the actions require manual review and approval, please plan ahead and allow some time for processing.
Security Best Practices
- Use unique accounts for each broker or queue to enhance security.
- Multiple accounts help isolate access and reduce risk.
- Nodinite admins manage associations and rights to ensure compliance.
Next Step
- Product Key System Parameter Management
- Runtime Environments Overview
- Step 1: Basics - Installation of Nodinite v7 and registration of the first environment.
- Nodinite Portal