littlehorse-enterprises/littlehorse

LittleHorse Server: Business-as-Code Platform for Microservices, Workflows, and Agents

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on March 19th, 2025
Created on July 19th, 2023
Open Issues & Pull Requests: 223 (+0)
GitHub issues: Enabled
Number of forks: 38
Total Stargazers: 400 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.8 days
Mean response time: 82.5 days
90th percentile: 275.9 days
Tracked items: 558

Maintainer activity

9 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 32% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "dashboard" is answered fastest, typically in about 6 days, while "documentation" waits about 8 months. 51% of tracked open issues have had no activity in three months. Only 48% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 195
New in 7 days: 2
Closed in 7 days: 4
Avg open age: 269 days
Stale 30+ days: 171
Stale 90+ days: 140

Recent activity

Opened in 7 days: 2
Closed in 7 days: 4
Comments in 7 days: 0
Events in 7 days: 2

Top labels

  • server (258)
  • dashboard (197)
  • clients (79)
  • needs-proposal (74)
  • lhctl (14)
  • documentation (13)
  • canary (3)
  • javascript (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

LittleHorse is a high-throughput, low-latency orchestration engine written in Java that enables developers to codify business processes spanning agents, microservices, integrations, and workflows using a Business-as-Code approach. The platform is built on Apache Kafka and Kafka Streams, providing two-way rich integrations with the Kafka ecosystem so that workflows can be triggered by Kafka events and emit state changes back to Kafka in real time. This architecture allows LittleHorse to handle the operational complexity of distributed systems while keeping workflow definitions closely aligned with actual business logic.

The core value proposition of LittleHorse addresses several pain points in microservice orchestration. Rather than manually wiring microservices together with RPC calls or message queues, developers define workflows that LittleHorse executes durably. The platform abstracts away concerns like retries, timeouts, dead-letter queues, distributed tracing, asynchronous scheduling, and backpressure management, allowing teams to focus on business process logic rather than infrastructure plumbing. The Business-as-Code model enables product and engineering teams to maintain better alignment by expressing processes in code that mirrors actual business workflows.

LittleHorse provides multi-language SDK support across Java, Go, Python, JavaScript, and C#, with client packages available through standard package managers including Maven Central, PyPI, npm, and NuGet. The platform includes a dashboard accessible at localhost:8080 for inspecting workflow runs and their execution state. The project also provides lhctl, a command-line interface for interacting with the LittleHorse server and investigating workflow executions.

The project is licensed under the GNU Affero General Public License Version 3 for server and dashboard code, while SDKs, lhctl, examples, and other packages use the Apache License 2.0. LittleHorse follows Semantic Versioning after version 1.0 and maintains a documented project lifecycle with guidelines for releases and deprecation strategy. The platform includes comprehensive quickstart examples and documentation at littlehorse.io/docs, with an active Slack community for user engagement. The architecture separates concerns into task definitions (units of work), workflow specifications, and a workflow engine that ensures correct execution while task workers handle integrations with external systems and databases.