On-Prem deployment for RubusNode

What runs in your environment

RubusNode installs from documented container images. The control plane, PostgreSQL, Redis, the Mosquitto MQTT broker, and S3-compatible object storage all run under your operational ownership, and installation secrets such as database, signing, and encryption keys stay in your own secret store.

• Your own physical servers or your own cloud account
• Same IAM, PBAC, approvals, and hash-chained audit as SaaS
• GMS devices through RubusNode Cloud Services; Non-GMS/AOSP devices through the RubusNode Agent in Device Owner mode

RubusNode Cloud Services

Google-backed and managed capabilities reach your installation through a per-installation Cloud Services Connector: Android Enterprise, Zero-Touch enrollment, FCM push, Play Integrity, managed email, and the remote-support relay.

• Each installation authenticates with its own revocable, scoped credential
• RubusNode-held secrets, such as Google service account and mail provider keys, never ship to your infrastructure
• Every connector call is rate-limited and audited
• The data each service handles is documented, so you can review data residency before adoption

When the connection is unavailable

The console, IAM, approvals, audit, policies, and Non-GMS/AOSP device management through the RubusNode Agent keep working if the connection to RubusNode Cloud Services is interrupted. Capabilities that depend on Cloud Services show a clear unavailable state instead of failing silently.

Operational ownership

Your team owns patching, scaling, and availability for the On-Prem components. Talk to our team about the operational runbook and support model before committing to this path.