Ice
Lightweight visual rule engine and business orchestration framework
Visual Rule Orchestration
Tree-based orchestration with a Web visual configuration interface. Nodes are independent and isolated, achieving true business decoupling and configuration flexibility.
Lightweight and High Performance
Pure in-memory computation with millisecond-level response and near-zero performance overhead. No database or middleware dependencies required. One-click Docker deployment.
Multi-Language SDKs
Feature-equivalent Java, Go, and Python SDKs. Hot reload rules that take effect in seconds without application restart.
Get Started in Three Steps
1. Deploy Ice Server
Visit http://localhost:8121 to access the visual configuration interface.
2. Integrate Client SDK
Shared Storage
Server and Client synchronize configurations by sharing the same ice-data directory, with no network communication required.
3. Configure Rules and Execute
Configure a rule tree in the Server interface -> click Publish -> Client automatically hot-loads the rules. Call execution in your code:
View the full Getting Started guide | Java SDK | Go SDK | Python SDK
Use Cases
| Scenario | Description |
|---|---|
| Marketing Campaigns | Flexible configuration of complex marketing rules like coupons, discount thresholds, and group deals |
| Risk Control | Credit risk assessment, anti-fraud, and real-time risk evaluation engines |
| Access Control | Dynamic permission management, role configuration, and resource access control |
| Process Orchestration | Ticket routing, approval workflows, and state machine management |
Why Choose Ice
| Feature | Ice | Traditional Rule Engines (Drools, etc.) |
|---|---|---|
| Learning Curve | Get started in 5 minutes | Requires learning a DSL |
| Deployment Complexity | One-click Docker deployment, zero dependencies | Requires database and middleware |
| Configuration Method | Web visual tree-based orchestration | Text or code |
| Performance | Pure in-memory, millisecond-level | Compiled execution with overhead |
| Rule Modification | Hot reload, takes effect in seconds | Requires restart or redeployment |
| Change Impact | Nodes are independent, no ripple effects | Changes cascade across the system |
Users
