Hi Atera team,

First of all, I just want to say how impressed we are with the platform. The pace of development, the clarity of the API, and the overall reliability of the agent have made Atera a core part of how we operate day to day. It’s clear a lot of care has gone into building something that scales well for real-world MSP use.

We wanted to raise a small but potentially high-impact feature request around device naming and agent reporting.

At the moment, if a device hostname is changed locally at the OS level, that change does not appear to propagate back into the Atera dashboard or API. As a result, fields such as AgentName, SystemName, and MachineName remain static against the AgentID / DeviceGuid, even though the underlying system identity has changed.

It would be incredibly valuable if the agent could report the current OS-level device name back to the tenant on check-in and update those fields automatically.

This would unlock several practical benefits for all Atera users:

Improved estate accuracy
Device inventories would remain aligned with the actual environment, reducing drift between reality and the dashboard over time.

Cleaner automation and integrations
Many workflows, scripts, and third-party integrations rely on device names as human-readable identifiers. Keeping names in sync removes ambiguity and manual reconciliation.

Reduced operational overhead
MSPs would no longer need to manually correct naming mismatches after rebuilds, renames, or standardisation exercises.

Better reporting and analytics
Accurate naming improves confidence in reports, audits, and compliance checks, especially in larger or more dynamic estates.

Smoother onboarding and lifecycle changes
Device renames during provisioning, repurposing, or role changes would naturally flow through without additional admin effort.

From a data model perspective, this feels like a natural extension of the excellent work already done around agent telemetry, with the AgentID / DeviceGuid remaining the stable anchor while human-readable identity stays current.

We appreciate that there are always trade-offs and edge cases to consider, but this feels like a change that would quietly improve quality of life across the entire platform.

Thanks again for building such a solid product, and for being consistently open to feedback from the community. We’re very happy Atera users and excited to see how the platform continues to evolve.

Kind regards,
Ian