Q: Number of bots
Hi,
I am considering buying Tier 6 for commercial use of the system. So I have a few questions:
1. 24 hours per month of Cloud runs seems like a lot, I mean bots run fast af mostly. But when I go to your monthly pricing even the Solo has 80 hours per month. How much is 24 hours really? Is it actual time of scripts running?
2. I was doing RPA back in 2008 using Ubot Studio. The thing about Ubot was there was no limit on the number of bots you could build. Here I see the max I can have is 20 Production and 10 Application. I am wondering if that means "running bots." Can I create unlimited scripts/flows (in Tier 6) for different tasks and then only use limited amounts at the same time? Is that where the restriction is?
3. Is it possible to Self-host this AppSumo Version (like N8N on a VPS)?

Faik_Robomotion
Apr 23, 2025A: Hello,
1. This is a shared resource for your robots. Depending on the complexity of the flow, it may take anywhere from five minutes to one hour to complete.
2. In Tier 6, you can create unlimited flows (automation projects or node sequences) and schedule them on your production robots. A production robot can run any of your unattended flows. Most customers start with one production robot, then expand to two or three, so having 20 robots is actually quite large in RPA. Because there’s a finite amount of automation in any given company, many AppSumo users leverage these robots as shared resources, outsourcing automations for clients and running them on demand. A major advantage of Robomotion over other leading RPA platforms is that a single robot can execute parallel sequences within the same flow. For example, one robot can process 10 or even 100 scraping or invoice-processing tasks simultaneously in a single flow (not to be confused with running separate flows), greatly multiplying its throughput.
3. This offer applies to the Starter Plan, including the self-hosted version of the entire backend system (not just the robots which is very easy to setup on your system). Please note that this option requires strong technical expertise to manage a Linux server and a local Kubernetes cluster. We provide scripts to help you set up your servers, but we do not support infrastructure tasks such as Linux administration, Kubernetes operations, networking, or DNS configuration. You’re welcome to seek help in our community or engage us for a paid setup service, but if your team only works with Windows, you’ll need outside assistance for the Linux/Kubernetes setup. Our scripts generally run automatically and can install a functioning system in a few minutes, but any errors may require deep expertise in Linux, networking, and Kubernetes. We also don’t maintain an always-up-to-date, automated on-premise installer. While we typically work with our online hosted cloud system (used by most of our clients), larger on-premise projects require us to build a custom installation package with the latest version of our platform. This manual process takes additional time, so please expect a slower turnaround for on-premise deployments. Note that Cloud Run also cannot be applied to this setup if chosen because everything must be installed on your own system.
Best,