- 5 minutes to read

Release Notes

Welcome to Nodinite Installation & Configuration

Successfully deploy Nodinite—the comprehensive monitoring and logging platform for integration solutions. Whether you're setting up a new instance, upgrading from v6, or exploring a proof-of-concept, this guide provides everything you need.

Nodinite supports flexible deployment architectures—from single-server installations to distributed enterprise environments in the cloud. Begin by planning your installation to understand your options, then review the prerequisites before following the step-by-step Installation Guide.

Choose Your Version

Nodinite has two major versions with different installation approaches:

Modern, automated installation using the CLI installer from the Nodinite Portal, typically executed from PowerShell 7 .

Nodinite v7 on Windows Server hosts Core Services and agents in IIS, which makes HTTPS/TLS the standard transport model for production deployments. Container runtimes use self-hosted .NET 10 web applications on assigned ports and do not use IIS.

Key Features

  • Automated installation via Nodinite.Installer.Cli.exe
  • Modern technology stack - .NET 10 + ASP.NET Core
  • OAuth 2.0/OpenID Connect support for enterprise authentication
  • Windows Server runtime with IIS-hosted Core Services and agents for secure production deployment
  • Container runtimes with self-hosted .NET 10 web apps and assigned endpoint ports (no IIS)
  • Multi-environment management from centralized portal
  • Ongoing support and updates

Nodinite v6 (Legacy – No Longer Supported)

Web-based Install and Update Tool for manual installation (deprecated).

Important

Nodinite v6 is no longer supported. Existing v6 customers should upgrade to v7 for continued support, security updates, and new features.

v6 Documentation (Historical Reference)

Nodinite v5 (Historical Archive)

Historical migration reference for customers who still run Nodinite v5.

Important

Nodinite v5 has been out of support for many years. A move from Nodinite v5 to Nodinite v7 is technically possible, but it should be planned with Support page or a certified Partner.

v5 Documentation (Historical Reference)

Version 4 (Historical Archive)

Legacy documentation for customers upgrading from Integration Manager v4 (2014-2016 era).

Main Resources

Installation & Configuration

Troubleshooting & Support

Docker (Experimental)

Nodinite now includes an experimental Docker-based path for POC scenarios where teams want to quickly evaluate the Web Client experience and explore the Repository Model.

Start with the dedicated Docker troubleshooting and setup guidance to understand current scope, OAuth requirements, and limitations.

Professional Services

About Nodinite Installation

Nodinite is installed as a dedicated instance for each customer or environment, ensuring:

  • Strict access control - Each instance has isolated user permissions
  • Data isolation - Complete separation between environments
  • Scalability - Deploy from single-server POCs to distributed enterprise installations
  • Flexibility - On-premise, cloud, or hybrid deployments

For Nodinite v7, the preferred production installation model on Windows Server is to host Core Services and agents in IIS with TLS enabled. For container runtimes, Core Services run as self-hosted .NET 10 web applications on assigned ports and rely on container ingress/route configuration instead of IIS.

Architecture Options

Icon Deployment Type Description Best For
Single Server All components on one server POC, small environments, monitoring-only
Distributed Components across multiple servers Production, high availability, large scale
Cloud Azure, AWS, or other cloud platforms Hybrid scenarios, geographic distribution

Tip

Planning Your Architecture? See Planning Your Installation for detailed deployment scenarios and requirements.

Next Step

Ready to begin? Follow the Installation Guide to get started, or explore these key resources:

Tip

Need help? Contact Support page or connect with a certified Partner.