- 3 minutes to read

Runtime Environments for Nodinite

Use this page to choose the correct Nodinite runtime environment and understand how the platform model affects installation, authentication, and operations.

Understanding the Runtime Model

Nodinite now supports five runtime environments. The Windows Server path remains the full operational baseline, while the container-based paths focus on Core Services with external dependencies.

flowchart LR PORTAL["fa:fa-globe Nodinite Portal"] --> ZIP["fa:fa-file-zipper Configuration ZIP"] ZIP --> WIN["fab:fa-windows Windows Server (IIS)"] ZIP --> DOCKER["fab:fa-docker Docker Compose"] ZIP --> K8S["fab:fa-kubernetes Kubernetes"] ZIP --> OCP["fab:fa-redhat OpenShift"] ZIP --> ACA["fa:fa-container-storage Azure Container Apps"] DOCKER --> REG["fa:fa-box-archive Container Registry"] K8S --> REG OCP --> REG ACA --> REG DOCKER --> OAUTH["fa:fa-key OAuth 2.0 / OpenID Connect"] K8S --> OAUTH OCP --> OAUTH ACA --> OAUTH style WIN fill:#90EE90,stroke:#2e7d32 style DOCKER fill:#87CEEB,stroke:#1e5f86 style K8S fill:#87CEEB,stroke:#1e5f86 style OCP fill:#87CEEB,stroke:#1e5f86 style ACA fill:#87CEEB,stroke:#1e5f86 style OAUTH fill:#FFD700,stroke:#8a6d00

Diagram: Runtime selection starts in Nodinite Portal and branches into five supported environments, where all container runtimes use OAuth 2.0/OpenID Connect and pull images from the container registry.

Runtime Comparison

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 PowerShell installer from Portal ZIP
Docker Compose Container runtime Core Services only (sandbox) OAuth 2.0/OpenID Connect (required) Configuration ZIP + readme + container images
Kubernetes Container orchestrator Core Services only (sandbox) OAuth 2.0/OpenID Connect (required) Configuration ZIP + readme + Helm chart instructions
OpenShift Kubernetes distribution Core Services only (sandbox) OAuth 2.0/OpenID Connect (required) Configuration ZIP + readme + Helm chart instructions
Azure Container Apps Managed Kubernetes service Core Services only (sandbox) OAuth 2.0/OpenID Connect (required) Configuration ZIP + readme + Bicep + az command flow

Container Delivery Model

For container runtimes, users must start in Nodinite Portal to download a customer-specific configuration ZIP.

The ZIP includes environment-specific settings and a readme.md describing the deployment flow:

  • Helm chart retrieval and deployment guidance for Kubernetes and OpenShift.
  • Bicep deployment guidance with az command usage for Azure Container Apps.
  • Runtime-specific configuration values aligned with selected environment settings and selected agent choices.

Important

Container runtimes currently deliver only Nodinite Core Services. Monitoring agents and logging agents are not bundled in these runtime tracks.

Authentication Baseline

All container runtimes require OAuth 2.x and OpenID Connect.

  • Plan identity provider configuration before deployment.
  • Validate issuer URL, client IDs, scopes, and claims mapping.
  • Ensure callback and redirect URLs match the selected runtime endpoint.

If OAuth configuration fails, review Troubleshooting OAuth2 Validation Failures.

Choosing the Right Runtime

Use these practical criteria when selecting a runtime for your Nodinite environment.

  • Choose Windows Server (IIS) when you need the full runtime with bundled agent support.
  • Choose Docker Compose when you want quick local sandbox validation.
  • Choose Kubernetes or OpenShift when your organization standardizes on cluster-based operations.
  • Choose Azure Container Apps when you want a managed Kubernetes service in Azure.
  • Expect new runtime choices, such as Podman, to follow the same Portal ZIP + readme + OAuth baseline pattern.

Next Step