- 8 minutes to read

Welcome to Nodinite Core Services

Discover the foundational components that power Nodinite, the monitoring, logging, and documentation platform for integration solutions. Nodinite Core Services run on .NET 10 and ASP.NET Core, and every Nodinite installation has them.

Whether you run a single-server proof of concept or a distributed enterprise deployment, Core Services are the foundation. With New 7.x v7, you describe the environment in the Nodinite Portal, download one package, and run it with PowerShell 7; the package installs and updates all Core Services for you.

What Are Nodinite Core Services?

Nodinite Core Services are the essential components that run in every Nodinite installation:

New 7.x Modern Technology Stack (v7)

  • .NET 10 and ASP.NET Core - On Windows Server, each service is its own IIS web site with its own port; container runtimes run each service as its own container
  • Generated deployment package - Values from the Nodinite Portal, run with Nodinite.Installer.Cli.exe
  • OAuth 2.0 / OpenID Connect - Optional enterprise sign-in for users and API clients; see Install with OpenID/OAuth
  • AI-ready - The MCP Endpoint gives AI clients typed access to your environment; see AI in Nodinite
  • Ongoing support - Monthly updates with new features and security patches

High-Level Service Overview

Nodinite is deployed entirely within your own infrastructure. No integration data, Log Events, or business information is transmitted to Nodinite as a vendor. Your data never leaves your defined boundaries.

graph TD subgraph boundary [" Your Infrastructure – All data stays here "] subgraph platforms ["Integration Platforms"] Platforms["fa:fa-network-wired BizTalk · Azure · MuleSoft
SAP · Custom APIs · Any platform"] end subgraph agents ["Nodinite Agents – on your servers"] LogAgent["fa:fa-cloud-arrow-down Log Agents
Collect log events from integrations"] MonAgent["fa:fa-watch-fitness Monitoring Agents
Check resource & service health"] end subgraph nodinite ["Nodinite Core Services – on your servers"] LogAPI["fa:fa-cloud-arrow-down Log API
Event ingestion"] CoreSvc["fa:fa-cogs Web API · Logging Service
Monitoring Service · MCP Endpoint"] DB["fa:fa-database SQL Databases
Config & Log Data"] WebClient["fa:fa-globe Web Client
Browser UI"] end Users["fa:fa-users Your Users
Browser – HTTPS"] end NodiniteVendor["fa:fa-building Nodinite (vendor)
Portal, product keys & update API"] Platforms -->|"Log events"| LogAgent Platforms -->|"Resource metrics"| MonAgent LogAgent -->|"HTTPS"| LogAPI MonAgent -->|"HTTPS"| CoreSvc LogAPI --> CoreSvc CoreSvc <-->|"Read / Write"| DB CoreSvc --> WebClient Users -->|"HTTPS"| WebClient NodiniteVendor -.->|"Admin-triggered version check
No data access"| CoreSvc

Nodinite is installed on your own servers. Log Agents collect events from your integration platforms and forward them to Core Services within your network. Users access the Web Client via browser over HTTPS. Nodinite as a vendor has no access to your systems, log data, or business transactions.

Important

Data Sovereignty: Nodinite is not a SaaS service. It is installed and operated entirely within your own infrastructure. The only optional outbound behavior from the installed environment is an administrator-initiated version check. Administrators may also use the Portal download workflow or optional direct MSI downloads for remote servers. See Install Nodinite v7 for the current outbound host allowlist. No integration data, messages, or business information ever leaves your environment.

Core Services Architecture

Understanding how Core Services work together helps you plan deployments and troubleshoot issues.

graph LR subgraph "SQL Server" roConfigDatabase(fal:fa-database Configuration database) --- | Linked Server | roLogDatabase(fal:fa-database fal:fa-database fal:fa-database Log databases) end subgraph "Application Server (IIS)" roLogAPI(fal:fa-cloud-arrow-down Log API) --- roConfigDatabase roWebClient(fal:fa-globe Web Client) ---roWebAPI(fal:fa-cloud-sun Web API) roWebAPI --- roConfigDatabase roLoggingService(fal:fa-hard-drive Logging Service) --- roWebAPI roLoggingService --- roConfigDatabase roMonitoringService(fal:fa-watch-fitness Monitoring Service) --- roConfigDatabase roMonitoringService --- roWebAPI roMcp(fal:fa-plug MCP Endpoint) --- roConfigDatabase roWebClient --- roMcp end

Diagram: Core Services on a Windows application server, each an IIS web site, and their connections to the Configuration Database and the Log Databases.

The Type column below describes the Windows Server (IIS) runtime. With the container runtimes, the same services run as containers; see Runtime Environments.

Component Breakdown

Component Type Purpose Key Features
Web Client IIS web site User interface for logging, monitoring, and documentation Log Views, Monitor Views, Repository Model, dashboards
Web API IIS web site (REST) Secure data access and operations Role-based access, audit logging, System Parameters endpoints
Log API IIS web site (REST) High-throughput Log Event ingestion Bulk logging from agents and custom solutions; optional OAuth
Logging Service IIS web site (background processing) Log Event processing Message Types, indexing, retention, Log Database creation and splitting
Monitoring Service IIS web site (background processing) Alert delivery and agent coordination Alarm Plugins, Alarm Queue, Remote Actions
MCP Endpoint IIS web site MCP access for AI clients AI Assistant, external MCP clients, MCP tools
Configuration Database SQL database Configuration and documentation storage Repository Model, Articles, System Parameters, users
Log Databases SQL databases Log Event and Monitoring Event storage Splitting on size or age, archiving, Linked Server access

What You Set in the Nodinite Portal

You don't configure IIS sites, ports, or service accounts by hand. You enter them per environment in the Nodinite Portal, and the generated package applies them to every Core Service:

What Portal step
Environment name and runtime (Windows Server IIS or containers) 1. Basics
Windows Authentication or OAuth 2.0 / OIDC, service account defaults, and OAuth values for the Web Client, Web API, Log API, and MCP Server 2. Auth
SQL Server type and connection string, SqlPackage path, proxy 3. Infrastructure
The Core Services host, TLS certificate, and the port and identity of each service 4. Servers → Core platform services
Agents on each server 5. Agents
Allocated ports, download 6. Review and Download
Run the package 7. Run the CLI Workflow

Each service's Install page lists the Portal values that apply to that service, for example Install the Web API and Install MCP Endpoint.

System Parameters by Service

System Parameters are environment-wide settings stored in the Configuration Database. You change them in the Web Client or through the Web API (Manage System Parameters); a change takes effect within about 15 seconds, without a restart. Each service documents the parameters it reads:

Service Its System Parameters
Web Client System Parameters that shape the Web Client - environment name and colour, Log View data protection, repair and resend, AI, content
Web API System Parameters the Web API reads - licence, MaintenanceMode, api/SystemParameters endpoints
Log API System Parameters read by the Log API - SqlServer, and what happens after an event is accepted
Logging Service Key System Parameters for the Logging Service - retention, cleanup, message processing
Monitoring Service Key System Parameters for the Monitoring Service - Alarm Queue, Monitoring Event and backup retention
MCP Endpoint System Parameters - the AI flags for the AI Assistant and BizTalk tools
Log Databases System Parameters for Log Databases - splitting, naming, file locations, recovery model
Configuration Database Where System Parameter values are stored

Deployment Flexibility

Nodinite Core Services support multiple deployment architectures:

Deployment Type Description Best For Typical Scale
Single Server All Core Services and SQL Server on one server POC, small environments, monitoring-only SQL Express, ~€10/month in Azure
Distributed Core Services on one host, SQL Server and agents on others Production, high availability Dedicated SQL Server, Always On Availability Groups
Cloud and containers Azure, AWS, or hybrid; container runtimes for evaluation Geographic distribution, managed services See Runtime Environments

Scalability Highlights

  • Scale up - From SQL Express to Enterprise Edition with minimal configuration changes
  • Scale out - Spread SQL Server, Log Agents, and Monitoring Agents across servers; Core Services run on one host per environment
  • No technical limitations - Supports everything from 10€/month Azure VMs to dedicated enterprise infrastructure
  • Performance key - Disk I/O is the primary performance factor for large logging volumes

Tip

See Planning Your Installation for detailed deployment scenarios and sizing recommendations.

New 7.x Installation & Updates (v7)

  • Generated package - The package from the Portal installs every Core Service and the agents you selected
  • Fast updates - Running the update typically takes a few minutes, agents included
  • Cumulative releases - Skip intermediate versions safely
  • Central management - Environments, product keys, and downloads in the Nodinite Portal
  • Integrated agents - Log Agents and Monitoring Agents are part of the same package

Note

What's Included in Core Services?

Core Services are packaged as one deployment unit: Web Client, Web API, Log API, Logging Service, Monitoring Service, MCP Endpoint, Configuration Database, and Log Databases.

What's Separate? Log Agents and Monitoring Agents can be installed on the Core Services server or on remote hosts for distributed architectures.

Multi-Tenant & Managed Services

Nodinite Core Services power managed service offerings for Partners:

graph LR subgraph "Nodinite Instance" roNodinite(fal:fa-code-commit Nodinite) end subgraph "Customer 1" roCustomerSouth((South)) roNodinite --> roCustomerSouth end subgraph "Customer 2" roCustomerContoso((Contoso)) roNodinite --> roCustomerContoso end subgraph "Customer 3" roCustomerNorth((North)) roNodinite --> roCustomerNorth end

Diagram: Multi-tenant architecture showing Partners can host multiple customers on a single Nodinite instance.

Managed Services Benefits

Partners use Nodinite to deliver integration support:

  • Multi-tenant hosting - One Nodinite instance, multiple customers
  • Flexible infrastructure - Host in Azure, AWS, or on-premises
  • Minimal configuration - Monitoring Agents connect with low overhead
  • Built-in knowledge base - Articles provide operator instructions and troubleshooting
  • SLA compliance - Proactive alerts with Custom Metadata keep support teams informed
  • Remote management - Execute Remote Actions to solve problems without customer access
  • Professional services - Deliver expert support for system integration solutions

Tip

Want to become a partner? Contact us!

Prerequisites & Permissions

Core Services require specific permissions on Windows Server, SQL Server, and the network firewall:

Windows Server SQL Firewall
Web Client
Web API
Log API
Logging Service
Monitoring Service
MCP Endpoint
Configuration Database
Log Databases

Use this table as your checklist when installing or troubleshooting Nodinite

Release Notes & Updates

Tip

Subscribe to Release Notes in the Nodinite Portal to never miss new features and improvements.

Note

Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.

Next Steps

Tip

Need help? Read more on the Support page or connect with a certified Partner.