Environment Name
Easily identify and manage your Nodinite environments with custom names and color schemes. On this page, you will:
- ✅ Instantly see the environment type and customer name in the Nodinite Web Client
- ✅ Clearly distinguish between multiple environments with custom names and colors
- ✅ Ensure compliance and clarity with always-visible license details
- ✅ Manage environments through the Nodinite Portal
- ✅ Get expert support for environment changes and licensing
Note
Nodinite v7 uses semantic versioning (MAJOR.MINOR.PATCH) for clear, predictable version tracking. This ensures transparency and easier upgrade planning.
Note
The environment name applies to all Core Services for each Nodinite instance, making it easy to manage multiple installations on the same host.
At the top of the Web Client, you instantly view the type of environment and the customer name of the licensee.
The environment name and customer details are always visible for clarity and compliance.
Every Nodinite installation is licensed and tied to a specific customer. The Customer Name links to the ProductKey. During the first installation, you define the environment name in the Nodinite Portal, ensuring clear identification from day one.
Common real-life examples of environment types include:
- PROD
- Demo
- Test
- QA
You define the environment name during the installation of Nodinite Core Services. This value cannot be easily changed. If you need to update the environment name, contact our Support or email support@nodinite.com for expert assistance.
Environment Color
You can apply a color scheme to visually distinguish between multiple environments. Learn more about the Environment Color feature in the documentation.
Environment Isolation
Every Nodinite installation is a fully independent instance. Production, test, staging, and development environments share no infrastructure, no credentials, and no data.
What is Isolated Per Environment
Each Nodinite instance has its own dedicated:
- SQL Databases – Separate Configuration Database and Log Databases with no linked servers between environments
- Windows Services – Dedicated Logging Service and Monitoring Service processes running under environment-specific service accounts
- Web Application pools – Isolated IIS application pools for Web Client, Web API, and Log API
- Credentials – Environment-specific service accounts, connection strings, and API keys. No credential sharing across environments
- Data – Log events, monitor results, repository configuration, and user data are stored exclusively in that environment's databases
Visual Safeguards Against Mistakes
The environment name and color scheme are displayed prominently at the top of every page in the Web Client. This is a deliberate safeguard — users can see immediately which environment they are operating in before taking any action.
Tip
Use distinct, high-contrast colors for production environments (e.g., red) and neutral colors for test/staging. This makes it immediately obvious when a user is connected to a production system.
Deployment Architecture Guarantees Isolation
Because Nodinite is deployed as a dedicated on-premise instance per environment, isolation is architectural rather than policy-based:
- There is no multi-tenant shared platform where environments could bleed into each other
- Each environment runs on its own servers (or dedicated VMs/containers) with no runtime dependency on other environments
- Agents configured for one environment report exclusively to that environment's Log API and cannot be redirected without a configuration change
Note
For organizations using a single host for multiple environments (e.g., a test server running both QA and staging), Nodinite instances are separated by distinct IIS sites, service instances, and SQL databases. The environment name and color make it visually unambiguous which instance a user is accessing.
Related System Parameters
Next Step
Nodinite Portal
Update Nodinite v7