Managed the same way as Non-GMS
AOSP devices are managed through the same Device Owner / MQTT push path as Non-GMS devices, since both lack Google Mobile Services. This is the same code path, not a separate integration.
Why this matters for air-gapped and regulated fleets
AOSP devices are common in environments where a dependency on Google’s infrastructure is unacceptable — which is also where RubusNode’s air-gapped deployment model applies. The device-management path and the deployment model are designed to work together.
See how RubusNode fits your endpoint fleet.
Book a walkthrough for this capability and the rest of the platform.