Customer Day-2 Operations

Can customers self-manage their deployments through Nuon?

›

How does Nuon provide real-time monitoring for deployed environments?

›

Does Nuon provide log aggregation for troubleshooting?

›

If I add a new component to an app do I need to manually trigger a deployment of all components on each install?

›

How can I pass an output from one component to another component or action?

›

How do we handle concerns about vulnerability scanning of our app by customers, potentially flagging "false positives"?

›

What happens if the app needs enhanced vendor access?

›

Do we need a separate observability tool to collect logs?

›

If we need separate monitoring stack outside of nuon - does that mean customer need to have 2 different cloud accounts to connect externally?

›

How do we debug when something goes wrong? Can we get into a customer's AWS console?

›

Would every interaction we have with our customers' clouds be intermediated through Nuon?

›

If we use Nuon, are we painting ourselves into a corner?

›

If a customer is down and the Nuon control plane is also down, we can no longer execute scripts to fix it?

›

Do we need dedicated infra engineers just to onboard customers

›

How do you manage bundling and release windows? Customers say you can only deploy between 7–9pm.

›

Customers are asking to see a changelog before each deployment. Do you have that?

›

How does Nuon handle complex one-time or periodic operational steps that require coordination across environments — things like certificate issuance, key material transfer, or rotation workfl

›