Deployment

Self-hosted deployment for RubusNode

Self-hosted deployment runs the RubusNode control plane, PostgreSQL, Redis, Mosquitto, and MinIO inside an environment your team owns and operates — for organizations whose data boundary, infrastructure policy, or procurement requirements call for it.

What runs in your environment

The control plane itself, PostgreSQL for primary data, Redis for caching and coordination, Mosquitto as the MQTT broker for Non-GMS device push, and MinIO for object storage all run under your operational ownership.

  • PostgreSQL, Redis, Mosquitto, and MinIO under your infrastructure
  • Same IAM, PBAC, approvals, and hash-chained audit as every deployment model
  • Full GMS and Non-GMS/AOSP device coverage unaffected by deployment choice

When self-hosted fits

Self-hosted is the right model when your organization’s security policy, data residency requirements, or existing infrastructure investment call for operating the control plane yourselves rather than relying on a managed SaaS boundary.

Operational ownership

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

/ FAQ

Common questions

What infrastructure do we need to provision for self-hosted deployment?

PostgreSQL, Redis, Mosquitto (MQTT broker), and MinIO (object storage), alongside the RubusNode control plane itself. Talk to our team for current sizing guidance based on your fleet size.

See how RubusNode fits your endpoint fleet.

Book a walkthrough for this capability and the rest of the platform.