RuleGo-Server

English | 简体中文

Official Website | Docs | Contribution Guide

RuleGo-Server is a lightweight, high-performance, modular, and integration-friendly automation workflow platform built on RuleGo.

It can be used for automation orchestration, iPaaS (Integration Platform as a Service), API orchestration, application orchestration, AI orchestration, data processing, IoT rule engine, AI assistant, and other scenarios.

Features

• Lightweight: Low memory usage, high performance, simple deployment, ready-to-use, no database required.
• Rich Components: Over 100 built-in components. Additionally, a component marketplace and rule chain marketplace are provided, supporting dynamic installation.
• Visualization: Supports visualization of rule chains.
• Modular: Compile and load on demand.
• Hot Updates: Workflow supports hot updates.
• AI Support: Supports large model components. The system automatically registers all components and rule chains as MCP tools for use by AI assistants.
• Bridge the Last Mile: Third-party system services can be easily encapsulated into MCP tools with the help of RuleGo-Server.

Experience Links

• Experience Link 1: http://8.134.32.225:9090/rulego-ipaas-ui/
• Experience Link 2: http://8.134.32.225:9090/ui/
• Experience Link 3: http://8.134.32.225:9090/editor/

HTTP API

API Documentation

Multi-Tenancy

This project supports multi-tenancy/users, with isolated rule chain data for each user. User data is stored in the data/workflows/{username} directory.

User permission verification is disabled by default, and all operations are performed as the default user. To enable permission verification:

• Obtain a token through username and password, then access other interfaces using the token. Example:

# Whether to enable JWT authentication for APIs. If disabled, operations will be performed as the default user (admin)
require_auth = true
# JWT secret key
jwt_secret_key = r6G7qZ8xk9P0y1Q2w3E4r5T6y7U8i9O0pL7z8x9CvBnM3k2l1
# JWT expiration time
jwt_expire_time = 43200000
# JWT issuer
jwt_issuer = rulego.cc
# User list
# Configure usernames and passwords in the format username=password[,apiKey]. The apiKey is optional.
# If apiKey is configured, the caller can access other interfaces directly using the apiKey without logging in.
[users]
admin = admin
user01 = user01

The frontend obtains a token through the login interface (/api/v1/login), then accesses other interfaces using the token. Example:

curl -H "Authorization: Bearer token" http://localhost:8080/api/resource

• Access other interfaces using the api_key method. Example:

# Whether to enable JWT authentication for APIs. If disabled, operations will be performed as the default user (admin)
require_auth = true
# User list
# Configure usernames and passwords in the format username=password[,apiKey]. The apiKey is optional.
# If apiKey is configured, the caller can access other interfaces directly using the apiKey without logging in.
[users]
admin = admin,2af255ea-5618-467d-914c-67a8beeca31d
user01 = user01

Then access other interfaces using the token. Example:

curl -H "Authorization: Bearer apiKey" http://localhost:8080/api/resource

Server Compilation

To save the size of the compiled file, the extension component rulego-components is not i

... View full README on GitHub