Picture the moment an AI agent gets triggered by an event — a support ticket, a queue message, a webhook — and has to reliably set off several things downstream in order. Most developers end up hand-wiring that themselves: retries, state tracking, a debugging session that starts with "okay, which step actually failed?" According to Colt McNealy, founder and CEO of LittleHorse, that's the moment a team building agents needs something underneath the agent framework they're already using.
"If you get to the point where your agent is triggered by an event somewhere... and then when the agent is done, something else has to happen, and then another thing has to happen, you're going to spend a lot of time wiring things together," McNealy told me in a briefing ahead of LittleHorse's Saddle Command Center 1.3 release. "You're not going to have an easy time debugging end-to-end what's going on, and you're going to need an orchestration system to make sure the right things happen in the right order."
LittleHorse was founded in 2022 and backed and advised by McNealy's father, Scott McNealy, co-founder and former CEO of Sun Microsystems. The idea traces back to a real estate startup where McNealy tried to build a scheduling system for open houses, showings, and escrow inspections, and found the business process scattered across Salesforce, DotLoop, several internal portals, a customer mobile app, and a lot of tribal knowledge. "That problem of any process being stitched, living in the point-to-point integrations and queue consumers... has only gotten worse as AI has come around," he said. "It's made it hard for customers to deploy agents into mission-critical business processes."
LittleHorse's answer is what it calls Business-as-Code: an open-source, Java-based workflow engine that turns an intended business process into a deployable, testable, version-controlled software artifact, then orchestrates it across whatever systems a company already runs. Developers write it in Java, Python, Go, or C# (JavaScript joins the list in 1.3), and it compiles into a process specification LittleHorse executes and tracks.
I asked McNealy what Business-as-Code does that the rest of a crowded orchestration field — Airflow, Temporal, Camunda, and agent frameworks like LangChain — doesn't already cover. Airflow, he said, is built for background data ETL, not real-time, high-speed business processes; one LittleHorse customer runs a virtual try-on product where a photo becomes a 10-step image-generation pipeline that has to run live, which he said isn't an Airflow use case. Temporal handles durable execution — safely retrying a failed function by replaying its prior side effects — but doesn't produce an end-to-end diagram a business user can actually read. "What LittleHorse gives you that Temporal doesn't... is a higher level for developers to get closer to the business process, closer to business value," McNealy said. Camunda, in his framing, doesn't produce a version-controlled, tested code artifact and isn't built for core product flows. LangChain and similar frameworks build the agent itself; in a LittleHorse workflow, that agent becomes one node inside a larger, deterministic process — and Saddle 1.3 adds a pre-built agent worker, running on LangChain under the hood, to make that pattern easier to deploy.
The clearest proof point McNealy offered is a utility and vegetation-management company — the kind of business that clears trees away from power lines — that had zero software engineers two years ago and ran operations on NetSuite plus roughly ten other SaaS systems. It decided to treat software as a competitive advantage, hired around 18 engineers, and started with one workflow: truck maintenance work orders, built on LittleHorse's open-source engine. It now runs more than 140 workflows in production, covering employee onboarding, job bidding, storm response and truck rerouting, and location tracking for 8,000 trucks every 30 seconds to generate a live heat map of completed jobs. Because the company owns that code instead of waiting on a vendor, McNealy said it has adopted agents in back-office workflows faster than competitors stuck waiting for SAP to ship an equivalent feature — one that, even then, would only work inside SAP.
That same logic shapes how LittleHorse handles agent guardrails, which McNealy walked through using a fraud-detection example from a financial-services customer. Their agent gets read-only access to internal systems through MCP, evaluates a transaction, and either the decision applies automatically below a set risk threshold or a human reviews the agent's report first. The agent never gets write access to push a transaction through on its own. "It really, really constrains what it can do and makes it a lot easier to verify and audit every single tool call that the agent has done," McNealy said. That split — deterministic code handles execution and audit, the agent handles judgment on ambiguous input — is also why it's worth the added layer at all, he argued: it cuts token usage and error rates, and shrinks the surface exposed to prompt injection, since the agent never touches the system doing the actual write.
Saddle Command Center 1.3 is built to reach that pattern from both ends: pre-built connectors and task workers, an integrated streaming layer, webhook and event triggers, and a serverless free trial so a team can try LittleHorse without standing up Kafka themselves — plus enough out-of-the-box capability that CIOs and architects don't need to write most of it.
Asked whether LittleHorse is easing a shift from human-driven business processes to agent-driven ones, McNealy didn't hesitate. "Even with the most complicated agents, there's still a larger process that causes the agent to run, and then when it's done doing its task, another thing happens in other systems," he said. "Those end-to-end workflows are what we codify." The bet behind Saddle 1.3 is that as agents move from prototypes into systems touching real trucks and real transactions, the question won't be whether a model is capable enough — it'll be whether anyone can say, with an audit trail, exactly what it was allowed to decide.
