HI,

Hope this article explains:

https://community1.pega.com/community/pega-support/question/deployment-portal-vs-robot-manager

Regards.

Hi , I would note down point wise for better understanding--

1. Pega Robotics deployment portal are outdated as of now.
2. The deployment portal was serving as a repository for Automation packages .
3. Now this is achieved by the combination of Robot Manager and Package Server.
4. Robot Manager - is used for

• monitoring all the runtime robots
• assign the packages
• change deployment levels , and many more..

    5. Package Server  is used -

• to deploy the Automation Package ( .openspan  &  .manifest  ) files
• when deployed from the Studio, the package gets published to Package server
• and the Automation metadata is published to Robot Manager

Thus the package management/distribution is done through Robot manager.

Each time runtime launches, it queries the Robot manager metadata , to compare if a latest version/package is available , if so , it pulls the latest package and runs.