February 05

Welcome to the February 05, 2020 release of the rapyuta.io platform. There are significant updates in this release that we hope you will like.


  • Override restart policy option
    Modify or override the initial setting of restart policy for components with device runtime while deploying a package.
  • Rapyuta IO Communication Broker package’s restart policy
    The restart policy for Rapyuta IO Communication Broker package is Always.
  • Static routes
    To get a deterministic URL/route for your application while exposing the network endpoint externally, you must bind it to a static route. When you add a static route, an externally exposed endpoint is essentially guaranteed to be available at the URL of that particular static route. It makes externally exposed endpoints (and hence the deployments exposing them) resilient to failure or re-deployment, facilitates maintenance and upgrades to the backend/deployment while retaining the same unique globally available URL.
  • rapyuta.io Python SDK 0.11.0 released
    Python SDK 0.11.0 defines a method that adds restart policy for a device component. To use newer SDK, install it by using:
pip install https://storage.googleapis.com/rio-sdk-python/rapyuta_io-0.11.0-py2-none-any.whl


  • Improved the logging infrastructure.
  • The default filter value for device logs is set to all.

Notable Fixes

  • Fixed install and uninstall script giving false deployments running error.


February 12

Welcome to the February 12, 2020 release of rapyuta.io platform. This release includes several internal improvements, optimizations and bug fixes.


The rapyuta-agent services now have a delay between restarts in case of failure.