Customer Installs

What is an install?
What are workflows?
Do I need elevated permissions for the install in my customer's account?
How does my customer set up an install?
How many runners are in a customer install?
Why are there AWS resources after I de-provision an install?
If my install fails midway through and I push a fix, do I retry with the new changes or create a new install?
When do I reprovision a customer install?
When do I reprovision a customer install's sandbox?
Can I create vendor-managed, install-specific secrets?
Why is a component workflow in a Pending state?
What's the current and planned approach for automated retry policies on Terraform components? Can we define retry behavior declaratively in the app config, or is manual vendor-initiated retry
With Nuon BYOC, does state stay entirely within our RDS, or does any state data transit through Nuon-managed infrastructure?
When we release a new Terraform component module version, we manually rebuild & redeploy per install. Is there batch redeploy/progressive rollout functionality?
Our Terraform module doesn't need an EKS cluster or any Nuon-managed base infrastructure. Is there a path to making the sandbox truly optional for non-K8s workloads?
How would we handle scaling from 10 BYOC customers to 100, 300, or even 1,000?
How do we handle customizations unique to a specific customer where installs need to differ slightly?
Can customers trigger their own installs or do we control everything?
Do we have to spin up new infrastructure for each customer or can we deploy into what they already have?
Do you support queue deployment for multi-step ordered migrations (version N must land before version N+1)?
Do you support Flux and Argo CD?
Can customers bring just a Kubernetes cluster or namespace rather than a full account?
Have you seen customers migrate from in-house BYOC to Nuon? What does that look like?
If we use Nuon, do we still need Spacelift (we're evaluating moving from Pulumi Cloud)?
What is the recommended CI/CD pipeline for Nuon?
Can you support a two-level versioning model — platform version + internal per-customer versions within that?
In Multi-tenant SaaS (Nuon Cloud) if we have multiple customers in one dashboard, is there isolation between them?
What about SSO - do customers manage their own accounts or does the vendor manage it?
What would migration look like from their existing hand-rolled BYOC deployments?
Is there license tracking built in?
Can customers see and manage their own single-tenant install — not just the vendor?
What deployment model variability do vendors face when offering BYOC to their customers?