Connect with the world of Intelligent automation at your fingertips

Cloud-Native Robot - Robotics-Connect with the world of Intelligent automation at your fingertips

Laiye Cloud-native Robotics provides a browser-based RPA Suite. Servers are available in a public cloud or in private deployment and generally run on Linux-based operating systems.

A Cloud-native robot links to you as long as you open your browser

Icon for Guarantee cost-effective results
Guarantee cost-effective results

Users can get access and use Creators and Workers on browsers without installation, which greatly reduces the deployment of each operating environment and the operation and maintenance costs.

Icon for Improve utilization rate
Improve utilization rate

Automation Suites are deployed in Docker containers. Resources are occupied only when applications run and process being executed, which will greatly improve the utilization rate of server resources.

Icon for Ensure uniformity and stability
Ensure uniformity and stability

Mirror environment provides a complete runtime environment including the kernel. The instance environment is created based on the mirror, improving the uniformity and stability of the production environment.

Cloud-Native Robot - Robotics-No client installation

No client installation

Creator and Worker are changed from C/S to B/S architecture, which means the RPA Suite can be installed on a group of servers, and after the servers are deployed, users can instantly use all the functions through the browser that supports HTML5.

Cloud-Native Robot - Robotics-Virtualization deployment

Virtualization deployment

Docker containers are used to achieve lightweight virtualization deployment of operating systems. Users can create processes and run unattended Automation Workers in each "container" environment. Meanwhile, process owners will not be bothered by robots while all logs can be recorded to meet the requirement of audit.

Cloud-Native Robot - Robotics-More stable execution

More stable execution

Programs and configuration are packaged in the image. A generic environment is provided by default while users can customize their environment based on the use case and default image. With this function, processes developed can be executed more stably regardless of the local environment.

Differences between community version & enterprise version

Community version
Entreprise version
Process editing
Need network connection
Parameters and credentials
Commands relating to The Hub
Commands relating to Date Service

Differences between SaaS Version & On-premise Version

SaaS Version
On-premise Version
Building Skills
Flow Builder
Table QA
Document search
Online Learning
Issue Management
Knowledge Mining
Preset Messaging Channel
Preset Voice Channel
Pre-built Connectors
Pre-integrate vendor
Preset Customer service
Custom Handover API
User Channel Widget
Customer experience
User Feedback
NLU Customization
Multi-Model Interaction
Dynamic Dialogue Policy
Personalized Experience
Metadata Application
Authority system
API Integration

Differences among different types

Attended & Floating
Attended & Node-locked
Unattended & Floating
With account and password
With “Activation code”
With Secret Key
Not Need
Not necessary

Differences between community version & enterprise version

Community Version
Enterprise Version
Process Execution
Node-locked License
High-Density Deployment

Differences between community version & enterprise version

Community Version
Enterprise Version
Foundational Function
Client Software Update
Parameters & Credentials
Real-time Monitoring and Screencap
Role & Department Management
Open API

How can we help you do better and be better ?