Mapped gateways are managed appliances used to securely connect building systems, equipment, and data sources to the Mapped platform. Mapped follows a model similar to other managed infrastructure appliances, such as network equipment, wireless access points, access control systems, and other vendor-managed edge devices, where the vendor manages the software, operating system, security and update lifecycle.
Mapped is responsible for maintaining the gateway agent software and operating system required for the system to function securely and reliably.
This includes:
Customers are not expected to manage the gateway, including any software installs, patches, or system-level changes.
The gateway is intentionally designed as a hardened, managed appliance. Local access is limited to the Mapped gateway configuration and diagnostic interface, which supports tasks such as network configuration, connectivity testing, proxy configuration, certificate configuration, and reboot actions. It does not expose a full operating system shell or customer-accessible root account. This design helps preserve the security, consistency, and supportability of the appliance.
Mapped updates gateways remotely as needed. Updates may be deployed to address a product issue, improve functionality, enhance security, or remediate an operating system vulnerability. This may include updates to the gateway agent, operating system components, supporting services, or configuration. If any update has the potential to impact gateway availability, connectivity to the site, or data collection, Mapped will coordinate with the customer as needed.
Security patching is also part of the managed gateway lifecycle. If a relevant vulnerability is identified, Mapped evaluates the exposure, impact, and required remediation. The response may include an operating system update, gateway agent update, configuration change, dependency update, or other compensating control.
Mapped manages this process so that gateways can be patched consistently, without requiring customer-side administrative efforts.
Customers remain responsible for the local environment needed for the gateway to operate, including:
As those independent from manually updating the gateway, patching the gateway, or managing the underlying operating system, they remain in customer control.