TiloBox
Back to directory
LiteFlow project preview

LiteFlow

Lightweight, fast, and component-based business rules and orchestration engine.

LicenseApache-2.0
GitHub stars6.5k
Last commit1 weeks ago
Tags5 topics
BusinessComponent OrchestrationBusiness Rules EngineRule Chain ExecutorLiteflow Framework
Overview

Why consider LiteFlow?

LiteFlow is an open-source, lightweight business rules and logic orchestration engine written in Java by Bryan. LiteFlow organizes complex business decisions into pluggable script components, executing sequential, parallel, conditional, and retry flow rules with low overhead.

Guided learning

Learn LiteFlow by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of LiteFlow

LiteFlow builds modular business rule chains and validation logic in Spring Boot apps.

Quickstart

xml
1<dependency>
2 <groupId>com.yomahub</groupId>
3 <artifactId>liteflow-spring-boot-starter</artifactId>
4 <version>2.12.0</version>
5</dependency>

LiteFlow is licensed under the Apache License Version 2.0.

Related tools

More options with a similar category or technology profile.

LiteFlow FAQs

LiteFlow is listed as a Business tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

LiteFlow is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

LiteFlow is listed as an alternative to Flowable. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.