Distr vs Nuon for BYOC Software Distribution
Distr and Nuon both provision infrastructure and deploy software in customer-controlled cloud accounts. They differ in how infrastructure is packaged, which operations workflows come built in and whether the same platform also covers existing clusters, servers and air-gapped networks.

Executive Summary
Distr and Nuon can both provision infrastructure and deploy applications inside customer-owned cloud accounts.
Distr packages existing OpenTofu or Terraform configurations as versioned controller images. Its infrastructure controller provisions and reconciles cloud resources, while its Kubernetes controller deploys the application onto the resulting cluster. Infrastructure and application releases use the same Distr distribution workflow.
Nuon provides a more opinionated operating model for vendor-managed BYOC on AWS, Azure and Google Cloud. Its advantages include staged fleet rollouts, approval gates, operational actions, release windows, break-glass access and integrated drift remediation.
Distr fits into the deployment workflows a vendor already has. It reuses existing infrastructure code, Helm charts, Compose files and pipeline templates, builds on open standards such as OpenTofu and OCI and so keeps lock-in low. Beyond BYOC on any cloud with an OpenTofu provider, it covers existing clusters, on-premises servers and fully air-gapped and offline installations.
Nuon fits vendors that start their BYOC offering from scratch, serve customers on AWS, Azure and Google Cloud only and want a prescribed process to follow, including break-glass access, a dedicated action framework, approval workflows and release windows.
Distr vs Nuon at a Glance
| Capability | Distr | Nuon |
|---|---|---|
| Provision customer-cloud infrastructure | Yes, through OpenTofu controllers | Yes |
| Deploy applications into customer clouds | Yes | Yes |
| Reuse existing Terraform or OpenTofu configurations | Yes | Yes, within Nuon’s application model |
| Periodic infrastructure reconciliation | Yes | Yes |
| Infrastructure drift detection | Yes | Yes |
| Packaged drift review and remediation | Reconciliation and deployment logs | More integrated workflow |
| Existing Kubernetes clusters | Yes | Focused on AWS, Azure and Google Cloud BYOC |
| Docker and virtual machine deployments | Yes | Not the primary deployment model |
| On-premises environments | Yes | Not the primary deployment model |
| Air-gapped environments | Yes | Not the primary deployment model |
| Customer-managed CI/CD | Yes | Vendor-operated model |
| Software licensing | Built-in signed offline licenses | Not a native product capability |
| Artifact entitlements and OCI registry | Built-in entitlements and registry | Artifact sync into installs; different entitlement model |
| Staged fleet rollout groups | Per-customer version and deployment updates | Packaged install groups with plan and approval |
| Customer approval gates | Customer-controlled update timing | Built-in BYOC approval workflow |
| Operational actions | Application and controller operations | Dedicated action framework |
| Break-glass access | No packaged workflow; documented remote access through Tailscale or Cloudflare Tunnel | Built-in temporary elevated access |
| Open source | Yes (Apache 2.0) | Yes (AGPL) |
| Self-hostable platform | Yes | Yes (AWS self-host and Nuon BYOC; Nuon Cloud also available) |
The Short Answer
Choose Distr when:
- BYOC should fit into existing deployment workflows and pipeline templates.
- Existing Terraform or OpenTofu configurations, Helm charts or Compose files should be reused.
- Open standards and low lock-in matter more than a prescribed process.
- Customers run on clouds beyond AWS, Azure and Google Cloud.
- Some customers provide an existing Kubernetes cluster or virtual machine.
- On-premises, fully air-gapped or offline installations are required.
- Customers may deploy through their own CI/CD pipelines.
Choose Nuon when:
- The BYOC offering is built from scratch, with no deployment workflows to keep.
- All customers run on AWS, Azure or Google Cloud.
- The team wants to follow Nuon’s application model and processes.
- Packaged staged fleet rollouts and approval gates are central requirements.
- Operational actions need a dedicated execution framework.
- Release windows and customer-approved updates are required.
- Break-glass access must be part of the platform.
- A packaged drift investigation workflow matters more than infrastructure portability.
The Core Difference
Distr Uses Versioned Infrastructure Controllers
Distr treats infrastructure as another versioned application.
The vendor packages an OpenTofu or Terraform configuration in an infrastructure controller image. That controller runs inside the customer environment and provisions the resources required by the application.
Those resources can include:
- Virtual networks
- Kubernetes clusters
- Managed databases
- Object storage
- DNS records
- IAM roles and policies
- Other resources supported by OpenTofu providers
The vendor publishes a new controller image when the infrastructure configuration changes. Updating the Distr deployment rolls out the new infrastructure version.
The controller creates an OpenTofu plan, applies the required changes and records the result in the deployment logs. Periodic reconciliation detects configuration changes and infrastructure drift.
Distr can then use its Kubernetes controller to deploy the application onto the provisioned cluster.
This creates a two-layer deployment:
- The infrastructure controller provisions and reconciles the environment.
- The Kubernetes controller installs and updates the product.
Distr manages both layers through versioned applications, customer deployments, secrets, logs, health information and release controls.
Infrastructure Controllers
Nuon Uses a Dedicated BYOC Application Model
Nuon models the customer-cloud installation as a complete BYOC application.
The vendor defines the infrastructure, application components, inputs, policies, actions and deployment behavior within Nuon’s platform. A runner inside the customer account executes the required operations with customer-controlled permissions.
Nuon coordinates the installation lifecycle through its control plane. Its operating model covers infrastructure provisioning, application deployment, customer approvals, operational actions and fleet management.
This approach gives vendors a structured system for operating installations across many customer accounts on AWS, Azure and Google Cloud.
The tradeoff is a more opinionated platform model. Infrastructure and operational workflows become part of Nuon’s application structure rather than remaining independent OpenTofu automation.
Infrastructure Provisioning
Reusing Existing Infrastructure Code With Distr
Distr works with standard OpenTofu and Terraform configurations.
A controller image contains:
- The infrastructure configuration
- The provider lock file
- The Distr OpenTofu controller
- Vendor-defined supporting files
OpenTofu installs the providers locked in that file when the controller runs. For installations that cannot reach the public provider registry, vendors can mirror providers into an OCI registry and point the controller at it.
Customer-specific values are passed through standard OpenTofu variables. Cloud credentials remain inside the customer environment, for example as Distr secrets consumed by the controller.
The infrastructure definition stays in the vendor’s repository and remains compatible with standard OpenTofu tooling. The vendor can test, review and run the same configuration outside Distr.
This model fits vendors that already manage their SaaS or enterprise infrastructure with Terraform or OpenTofu. Infrastructure engineers can keep using familiar modules, providers, resource definitions and review processes.
Using Nuon’s BYOC Model
Nuon also supports infrastructure-as-code workflows, but it coordinates them through its broader BYOC application model.
The platform connects infrastructure provisioning with application components, installation inputs, actions, policies and rollout behavior.
This model provides more built-in operational structure. It also creates a tighter relationship between the infrastructure workflow and the Nuon platform.
Nuon fits vendors that want the BYOC platform to define how the complete installation operates.
Distr fits vendors that want existing OpenTofu automation to remain the primary infrastructure definition.
Updates and Drift
Both platforms can update infrastructure and detect drift.
Distr’s OpenTofu controller periodically reconciles the declared configuration. It creates a plan when the infrastructure version, variables or underlying resources change.
The controller records resource changes in the deployment logs. A failed reconciliation affects deployment health and can trigger an alert.
Distr can either reconcile the infrastructure automatically or run in plan-only mode. In plan-only mode the controller logs the plan for review and does not apply it, except for a confirmed destroy. The customer controls the controller’s credentials and permissions.
Nuon provides a more integrated day-two workflow around infrastructure changes. Its platform is designed to help vendors review, approve, coordinate and remediate changes across customer installations.
Nuon has the advantage when visual drift investigation and coordinated remediation are central operating requirements.
Distr has the advantage when the declared OpenTofu configuration should remain portable and automatic reconciliation is sufficient.
Operating Customer-Cloud Installations With Distr
Distr also fits vendors that operate the installation in the customer’s cloud account themselves. The vendor runs both layers from the Vendor Portal:
- Infrastructure and application ship as versioned Distr applications and roll out through the same deployment workflow.
- Each customer deployment runs a specific version, and the vendor decides when it moves to the next one.
- Plan-only mode logs every infrastructure change for review before it is applied.
- Failed reconciliations show in deployment health and trigger alerts.
- Deployment logs and status cover the infrastructure and the application.
The customer keeps the cloud credentials and permissions. The vendor needs no standing access to the account.
BYOC
Fleet Operations
Nuon’s strongest differentiation appears after the initial installation.
Nuon provides packaged workflows for:
- Staged rollout groups
- Customer approval gates
- Release windows
- Pull-request plans
- Operational actions
- Break-glass access
- Installation-wide audit history
- Coordinated drift remediation
These capabilities support vendors that actively operate a fleet of customer environments on AWS, Azure and Google Cloud.
Distr manages infrastructure and application versions across customer deployments. Vendors can monitor deployment status, release updates, inspect logs, receive alerts and control which version each customer can access.
Distr does not currently provide the same packaged operating model for staged BYOC rollouts, temporary operational access and arbitrary actions across customer environments.
Nuon is stronger when the vendor needs a dedicated operations platform for a large BYOC fleet on AWS, Azure and Google Cloud.
Distr is stronger when the vendor wants a simpler controller model or expects customers to retain more operational control.
Security and Customer Control
Both products run components inside the customer environment.
Distr’s infrastructure and deployment controllers receive only the credentials and permissions required for their configurations.
The customer controls:
- Cloud credentials supplied to the controllers
- IAM policies
- Kubernetes permissions
- Infrastructure variables
- Controller deployment
- Registry access
- Update timing
The vendor does not require interactive access to the customer account. When a support case needs it, the customer can let the vendor deploy a remote access application next to the application and undeploy it once the case is closed.
Customers can also choose not to run a deployment controller. They can pull approved artifacts from Distr and deploy them through their own CI/CD pipeline.
Nuon also uses an in-account runner with customer-controlled permissions. Its operating model assumes that the vendor remains more involved in running the installation.
Nuon adds controls for that relationship, including release windows, customer approvals, operational actions, audit history and break-glass access.
Distr fits environments where the customer may operate the deployment independently.
Nuon fits environments where the vendor operates the deployment under customer-defined guardrails.
Beyond BYOC on AWS, Azure and Google Cloud
Distr covers distribution models outside BYOC on AWS, Azure and Google Cloud.
The same platform can distribute software to:
- Customer-owned cloud accounts
- Existing Kubernetes clusters
- Docker hosts
- Linux virtual machines
- Private data centers
- Air-gapped networks
- Customer-managed CI/CD pipelines
Distr also provides the commercial distribution layer around those deployments.
That layer includes:
- Customer and application entitlements
- Authenticated OCI artifact distribution
- Version access controls
- Software license generation
- Offline license verification
- Vendor and customer portals
- Deployment health and logs
- Documentation and support workflows
These capabilities matter when customers have different security, infrastructure or operating requirements.
A vendor can provision a new Kubernetes cluster for one customer, deploy into an existing cluster for another and distribute Docker artifacts to a third. The same customer, licensing and release model applies across those installations.
Nuon is more focused. Its platform is designed around vendor-operated applications inside customer-owned accounts on AWS, Azure and Google Cloud.
That focus allows Nuon to provide deeper workflows for that BYOC operating model. Distr’s broader scope allows one platform to cover BYOC and traditional self-hosted software distribution.
BYOC
When Distr Is the Better Fit
Choose Distr when BYOC should fit into the way the team already ships software.
Distr is a stronger fit when:
- Existing OpenTofu or Terraform configurations, Helm charts and Compose files should be reused and remain portable.
- Existing CI/CD pipelines and deployment templates should keep working.
- The platform should build on open standards such as OpenTofu, Helm and OCI, so the vendor can change tools without rewriting its delivery.
- Customers run on clouds beyond AWS, Azure and Google Cloud.
- Some customers provide an existing cluster or virtual machine.
- On-premises, fully air-gapped or offline installations are required.
- The company wants an open-source, self-hostable platform.
Distr adapts to the vendor’s workflows rather than prescribing its own, and the same platform serves BYOC, self-hosted and air-gapped customers.
When Nuon Is the Better Fit
Choose Nuon when a vendor builds its BYOC service from the ground up and wants an established process to follow.
Nuon is a stronger fit when:
- There are no existing deployment workflows to keep.
- All customers run on AWS, Azure or Google Cloud.
- Customers expect controlled, temporary vendor access to their accounts.
- Rollouts require staged installation groups.
- Customers must approve updates or define release windows.
- Operational actions must run across customer installations.
- Break-glass access needs a packaged workflow.
- Drift investigation and remediation are central platform functions.
- The company prefers Nuon’s application model over maintaining independent controllers.
Nuon provides more packaged operating structure around vendor access, actions and release coordination for customer-cloud environments.
Final Comparison
Distr and Nuon overlap across infrastructure provisioning and application deployment, but they optimize for different distribution strategies.
Nuon provides a more opinionated process for vendors that operate applications inside customer accounts on AWS, Azure and Google Cloud. Its strongest advantages are staged fleet rollouts, approval gates, operational actions, release windows, break-glass access and integrated drift operations.
Distr fits into the deployment workflows a vendor already runs. It packages existing infrastructure code as portable OpenTofu controller images, reuses Helm charts, Compose files and pipeline templates and builds on open standards, so the vendor is not tied to one platform. The same Distr platform also reaches clouds beyond the big three, existing clusters, on-premises servers and fully air-gapped and offline environments.
Choose Nuon when the BYOC offering starts from scratch, every customer runs on AWS, Azure or Google Cloud and the team is happy to adopt Nuon’s way of operating it.
Choose Distr when BYOC should fit into existing workflows, when flexibility and low lock-in matter or when BYOC is one of several ways customers run the software.






