Compose the process. Momor runs it.
A workflow engine for AI-driven processes. Bring an input, give a model its job, grant it tools, and wire where each output goes. Momor executes the process, records every step, and never loses its place — whether the work takes seconds or months.
An agent is anything that does work for you.
Agent, tool — the line barely matters here. Both are things that execute work, and the work can be as small as one search or one document summary, or as large as finding every deal that closed this quarter, which ones fell through, and why. Any model from any provider becomes that worker through the job you give it and the tools you grant it. Models decide; the engine executes — every requested tool runs through the engine, in parallel, with the results combined and fed exactly where the workflow points. Agents can be tools and tools can be agents, so workflows nest inside workflows without special machinery.
Bring your own capabilities
Tools plug in over MCP — point a workflow at your CRM, your document systems, your internal APIs, and they join the tool pool alongside Momor's built-ins. Extending what a workflow can do does not require writing code.
Humans are part of the flow
Approval gates, clarifying questions, and advisory notices are first-class constructs. A workflow can pause on a person for a minute or a month and resume exactly where it stopped.
Everything is on the record
Every run persists as a step-by-step ledger: which model ran, what it thought, which tools fired, what came back, where a person stepped in — the who, what, when, how, and why of the work. Runs are replayable, resumable after failure, and branchable — go back to any step and take a different path.
Built for long-lived work
Waits, deadlines, and external events are engine primitives. A workflow can span a months-long process as naturally as a single question — a conversation is just the simplest workflow.
Honest status.
The engine is real: it runs Momor's own search product in production. This is not a framework built beside the product — it is the product's architecture, opened up. The developer surface is in active development by a small team, .NET-first, and we are months out, not weeks out. Early-access teams shape the API with us.
There are no packages to download or docs to read yet. Early access means working with us directly.
Compose on the engine early.
Tell us the process you want to run and we'll tell you honestly where Workflows can and can't help yet.