+1 for this feature request.

In managed rollout scenarios using RMM tools like Datto RMM, the 5-minute token lifetime is a significant blocker for automated deployments. The reality is that jobs are scheduled across hundreds of devices, but execution depends on device availability and queue timing. Devices may be offline, in sleep mode, or simply not checking in at the exact moment. Even when online, jobs can take several minutes just to start executing depending on agent check-in intervals. There's no way to guarantee that hundreds of devices will all be online and execute the job within a 5-minute window.

To be clear, we need the Radar agents because the native Datto RMM sync doesn't populate all fields sufficiently for our documentation standards. This isn't meant as criticism of the integration, but the missing data points require us to supplement with the agent to get complete documentation. Without that, Hudu simply doesn't meet our requirements.

Manual deployment works fine but isn't feasible at scale when onboarding larger environments. It would be great if admins could configure the token lifetime themselves, for example 15 minutes, 30 minutes, 1 hour, or even 24 hours for larger rollouts. Alternatively, consider allowing tokenless authentication for the agent to gateway connection entirely. The token requirement for the main Radar application makes sense, but for automated agent rollouts it's just a barrier. This would make Hudu Radar viable for MSPs managing hundreds or thousands of endpoints. Without this, we're stuck choosing between manual deployment which doesn't scale or not using Radar at all.