Runavelo is designed for real business systems. Workflows run on the user's computer, an enterprise server, or another customer-designated environment by default. Customers manage business accounts, passwords, verification codes, and execution data under their own access policies.
Automation interacts with business systems, so execution environments, account permissions, and log retention are central to the security design.
Orders, customer records, admin pages, exported files, and other business data can be processed on customer computers, servers, or internal networks. Enterprise delivery can integrate with existing directories, databases, and access policies.
Customers maintain platform accounts, passwords, verification codes, browser environments, and login sessions. For sensitive systems, use dedicated execution accounts, least privilege, and regular credential rotation.
Workflow files, runtime logs, error screenshots, and execution results can remain local under the delivery plan for troubleshooting, auditing, and ongoing optimization.
For enterprise use, start with a frequent, rules-based workflow that a person can verify. Once validated, expand gradually to additional systems and accounts.
Rules-based processes such as repeated logins, data transfer, spreadsheet processing, order synchronization, bulk queries, report downloads, and notifications.
Processes involving fund transfers, irreversible submissions, sensitive approvals, or tightly controlled platforms should include human confirmation, allowlists, and permission isolation.
We do not promise to bypass third-party risk controls or guarantee that every page will remain stable indefinitely. Page redesigns, CAPTCHAs, and platform restrictions may require workflow updates.
Users configure and maintain business-system accounts, passwords, verification codes, and sessions on their own computers, servers, or enterprise environments. We recommend dedicated runner accounts with least-privilege access for enterprise deployments.
Execution data such as orders, spreadsheets, screenshots, and logs can be stored in local directories according to the deployment plan. For sensitive data, the customer should define retention periods and access permissions.
The Enterprise edition can be evaluated for intranet deployment, offline activation, dedicated runners, and customer-managed execution machines. The final design depends on system entry points, network policies, account permissions, and operational requirements.
Automation does not promise to bypass third-party risk controls. When a redesign, CAPTCHA, dialog, or platform restriction interrupts a workflow, logs and screenshots can identify the failed step for human review or workflow adjustment.
High-risk actions such as fund transfers, irreversible submissions, sensitive approvals, and customer-data changes should not run entirely unattended. Add human confirmation, allowlists, permission isolation, and audit trails.