- 5 minutes to read

Run Nodinite with Docker Compose (Experimental POC)

Nodinite now supports an experimental Docker Compose-based POC path for teams that want fast local evaluation with low setup overhead. This path currently focuses on Core Services and intentionally keeps scope narrow while we mature the container-first deployment model.

This guide explains what is available today, what is not yet available, and how to choose between Docker Compose and a traditional Windows Server installation.

Current Scope and Intended Usage

The current Docker Compose delivery is best for local and short-lived POC evaluation.

  • Nodinite Core Services are available for experimental use in Docker Compose.
  • You can explore the Repository Model and C4 Diagrams capabilities.
  • You can evaluate Mapify capabilities.
  • You can evaluate AI features in the Nodinite Web Client.
  • Monitoring agents and logging agents are not included yet in the Docker delivery.
  • SQL Server is an external dependency provided by the customer.

Important

Docker Compose in this phase is a POC track, not a full production replacement for the standard Windows Server installation.

Understanding the Docker Runtime Architecture

The current runtime model uses containerized Nodinite Core Services with an OAuth 2.0 and OpenID Connect identity provider.

In this container track, Core Services are self-hosted .NET 10 web applications running on assigned container ports. IIS is not used.

flowchart LR USER["fa:fa-user User on Laptop"] subgraph "Docker Compose" CORE["fa:fa-box Nodinite Core Services"] CORE --> CFG["fa:fa-database SQL Server"] CORE --> IDP["fa:fa-id-card OAuth 2.0/OpenID Connect IDP"] CORE --> REG["fa:fa-box-archive Container Registry"] end USER --> CORE USER --> IDP style IDP fill:#FFD700,stroke:#8a6d00 style CFG fill:#90EE90,stroke:#2e7d32 style REG fill:#87CEEB,stroke:#1e5f86

Diagram: Docker sandbox runtime where Core Services run in containers, images are pulled from the container registry, and authentication is delegated to OAuth 2.0/OpenID Connect.

Nodinite Docker Runtime (7.0)
Example of the current Nodinite Docker runtime topology used for local POC environments.

Authentication Model in Docker Compose

Docker Compose deployments do not support Active Directory sign-in in the current experimental implementation. Use an OAuth 2.0 compliant IDP with OpenID Connect instead.

  • Required: OAuth 2.x-compliant IDP.
  • Not available in this track: Active Directory integrated authentication.
  • Any OAuth 2.0/OpenID Connect provider can be used if claims and scopes are configured correctly.
  • Environment-specific OAuth settings are managed through Nodinite Portal configuration.

Tip

If your evaluation requires Active Directory today, use the standard Windows Server path and follow the regular Installation Guide.

Nodinite Web Client in Docker (7.0)
Example of the Nodinite Web Client running from a Docker-based POC setup authenticated through a local OAuth IDP.

Docker Compose vs Windows Server Feature Matrix

Capability Docker Compose (Experimental POC) Windows Server Installation Learn More
Setup speed on a laptop ✅ High ⚠️ Medium Proof of Concept (POC) Guide
Core Services ✅ Available ✅ Available Core Services Overview
Monitoring agents ❌ Not yet available ✅ Available Installing Monitor Agents
Logging agents ❌ Not yet available ✅ Available Installing Log Agents
Repository Model exploration ✅ Available ✅ Available Repository Model Overview
Mapify exploration ✅ Available ✅ Available Mapify Overview
C4 Diagrams exploration ✅ Available ✅ Available C4 Diagrams Overview
AI exploration ✅ Available ✅ Available AI Overview
Active Directory authentication ❌ Not available ✅ Available IIS Authentication settings
OAuth 2.0 / OpenID Connect ✅ Required ✅ Optional / Supported Install Nodinite v7 - OpenID
Production readiness ⚠️ Experimental ✅ Recommended path Installation Guide

Container Registry and Portal Configuration ZIP

Container images are delivered through the container registry and should be consumed through runtime-specific instructions from the Nodinite Portal.

Use this flow:

  • Download the customer-specific configuration ZIP from Nodinite Portal.
  • Open the bundled readme.md for runtime-specific instructions.
  • Pull container images from the container registry according to the readme guidance.
  • Configure OAuth 2.0/OpenID Connect values before first startup.

Important

Container runtimes currently focus on Core Services only. Monitoring agents and logging agents are not bundled in this Docker Compose runtime track.

Licensing and Runtime Choices

For container runtime licensing guidance and recommended choices for personal testing versus customer Test and PROD environments, use the dedicated page:

Honest Pros and Cons

USPs and Advantages

  • Very fast POC startup for developers and architects on their own laptops.
  • Minimal local footprint compared with a full Windows Server build.
  • Easy to reset and re-run test scenarios for AI, Mapify, C4 Diagrams, and Repository Model learning.
  • Great for demos, workshops, and early design conversations.

Trade-offs and Limitations

  • Monitoring/logging agents are currently out of scope.
  • No Active Directory support in the current implementation.
  • You must provide an OAuth 2.0/OpenID Connect IDP.
  • Production hardening and platform operations are still evolving for this deployment style.

Best POC Scenarios

Use Docker Compose right now when your goal is rapid product exploration rather than full operational rollout.

  • Discover how the Repository Model structures systems, services, and integrations.
  • Evaluate Mapify navigation and filtering behavior.
  • Build and review C4 Diagrams.
  • Test AI-assisted discovery and diagnostics flows.

For a broader POC plan, follow the Proof of Concept (POC) Guide.

Roadmap Direction

The target direction is to package Docker Compose deployment as a configuration-file-driven install flow, where the suitable installer ZIP is retrieved from the Nodinite Portal, similar to other install tracks.

Planned evolution includes:

  • Continuous improvements to configuration-file-based install experience.
  • Customer-specific runtime ZIP content from Nodinite Portal.
  • Additional container hosting options over time, including Podman.

Note

Roadmap items are directional and can change between releases.

Next Step