top of page

Frequently Asked Questions

To assist you we have compiled a list of frequently question (FAQs) below. 

  • How scalable is the Regami OTA?
    Regami OTA servers are optimized for scalability and have been tested to handle hundreds of thousands of devices. Whether you're managing a few devices or an extensive global fleet, our server infrastructure can support your needs. We offer both hosted server solutions and self-managed infrastructure options, giving you the flexibility to choose the best fit for your environment. Our hosted plans handle the complexities of scaling, uptime, and performance, so you don’t have to worry about infrastructure management.
  • Can Regami OTA be deployed on private infrastructure?
    Yes, Regami OTA supports deployment on private servers, offering full control over your infrastructure. We provide detailed installation guides for self-hosted deployments in our documentation. Both Open Source and Enterprise versions of Regami OTA can be configured to run on your own servers.
  • Can I use Regami OTA without connecting to a central server?
    Yes, Regami OTA can operate in standalone mode, where no central server is required. Updates are managed directly on the device, either through manual commands or custom scripts. This is ideal for devices that lack network connectivity or are updated via external storage media like a USB drive.
  • Which devices and operating systems are supported by Regami OTA?
    Regami OTA supports a wide range of Linux-based operating systems, including Ubuntu, and Raspberry Pi OS. We also offer integrations for systems like Buildroot. If you're using a POSIX-compliant system, you may be able to compile the Regami OTA client to run directly.
  • Does Regami OTA support smaller devices or sensors?
    Yes, Regami OTA can act as a proxy through a gateway device to update smaller or resource-limited devices like sensors and MCUs (microcontroller units). For instance, you can deploy updates to external hardware by managing the updates via a connected gateway device. Our client is written in C++ to prepare for future compatibility with popular Real-Time Operating Systems (RTOS), such as QNX, Zephyr, FreeRTOS, and VxWorks. Follow our development progress on GitHub or check out our blog for the latest updates.
  • What bootloaders are supported by Regami OTA?
    Regami OTA currently supports the most widely used bootloaders, including GRUB and U-Boot. More details about bootloader compatibility and system requirements can be found in our documentation.
  • Does ROTA undergo regular security audits?
    Yes, ROTA works closely with third-party security auditors to ensure our OTA solution remains secure. Any vulnerabilities that are identified during these audits are addressed promptly.
  • Is communication between Regami clients and servers secure?
    Yes, all communication between the Regami OTA client and server is encrypted via HTTPS, ensuring no open ports are required on the client side. Only TLS connections are accepted, and insecure connections are automatically rejected. To further enhance security, the Regami client stores the server’s TLS certificate during the initial setup phase, such as when provisioning devices with Yocto or other supported OSes. We also support CA-signed certificates to meet higher security standards.
  • Does Regami OTA work with hardware-based security?
    Yes, Regami OTA can utilize private keys stored in Hardware Security Modules (HSM) or Trusted Platform Modules (TPM) to enhance the security of your OTA deployments.
  • How does Regami protect against denial-of-service attacks?
    Our Enterprise Server includes configurable API rate-limiting features to prevent DoS/DDoS attacks. If a device or user exceeds the rate limit, they will receive an HTTP 429: Too Many Requests response. More security details are available in our documentation.
bottom of page