BotCity vs Pega RPA
BotCity
botcity.dev
Pega RPA
pega.comSide by side
| Figure | BotCity | Pega RPA |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Software Rpa | 8.5 (#2) | 7.8 (#8) |
| Spec score · Robotic Process Automation Software | 8.5 (#4) | 7.7 (#14) |
| Company | BotCity says it was founded in Brazil in 2018 and lists its address as 1110 Brickell Ave, Miami, Florida. | Pegasystems says it was founded in 1983 and is headquartered in Cambridge, Massachusetts. |
| Founded | 2018 | 1983 |
| Headquarters | Miami, Florida, United States | Waltham, Massachusetts, USA |
| Integrations | BotCity documentation names plugins for AWS, Google Suite, Microsoft Office, and Slack, and CI/CD integrations including Jenkins, GitLab CI/CD, and GitHub Actions. | Robot Studio adapters support Windows applications including Java apps and SAP GUI, web apps, and host or mainframe applications accessed through an emulator. |
| Purpose | BotCity provides visibility and control for governing Python scripts created and run across enterprises. | Pega RPA connects unrelated software systems and automates tedious manual work and repetitive tasks. |
| Security | BotCity states that customer databases and S3 buckets are encrypted at rest and that data in transit uses TLS 1.2 or higher. | For Pega Cloud, Pega states that data at rest uses AES 256-bit encryption and data in transit uses TLS 1.2 and TLS 1.3. |
| Support | BotCity documentation directs users to its support channel and provides courses through BotCity Academy. | Pega directs RPA users to its Support Center for questions and discussions, and says users can open a support ticket through My Support Portal for environment-specific guidance. |
Plans
In their own words
BotCity
BotCity provides visibility and control for governing Python scripts across enterprise environments. Its Sentinel product monitors script executions on company endpoints, adding execution context, alerts, policies, and audit evidence. Orchestrator centralizes scheduling, monitoring, queue management, alerts, and control for code-based automations. BotCity Runner can run automations on virtual or physical machines, containers, or AWS Lambda, while Studio supports Python, Java, and JavaScript automation code and includes computer vision tools for inspecting interface elements. Orchestrator can trigger bots through APIs and send real-time notifications through Teams, email, and WhatsApp. Documented plugins and integrations include AWS, Google Suite, Microsoft Office, Slack, Jenkins, GitLab CI/CD, and GitHub Actions. Orchestrator is cloud-based; agents and automations run in the customer's infrastructure behind its firewall and security layers. BotCity offers a free Community plan and a 30-day trial. After the trial, Community accounts are limited to one automation, one Runner, and 10 tasks per day; several features are disabled. The platform is aimed at developers and technology teams building enterprise automations.
Pega RPA
Pega RPA connects software systems and automates manual work across self-hosted, web, and Windows environments. Attended automation supplies digital assistants for tedious tasks in real time, while unattended bots can run in the background 24/7 without waiting for APIs. Robot Studio provides a low-code workspace to design, test, and deploy bots; design agents map applications and generate automations. Adapters cover Windows, web, and emulator applications, including Java, SAP GUI, Chrome, Electron, and host or mainframe systems. They can automate applications without recompiling or modifying the target, including systems without a well-defined API. Robot Manager manages work queues, monitors bot performance, and enables self-healing bots. Pega describes governance, testing, and reuse, and lists connections to Pega Agentic AI, Process Mining, and Process AI. Pega Cloud controls include role-based access, SAML, OAuth, Active Directory integration, AES 256-bit encryption at rest, and TLS 1.2 and 1.3 in transit. Documentation lists R25 and 22.1.