Is Monorch a framework like Mastra or Nest?

No. It is a library. You keep your server, router, auth, and deployment. Monorch plugs into handlers.

Do I need to rewrite my app around Monorch?

No. Call agent.run, agent.stream, or graph.start from the routes you already have.

Where does Rust show up for me?

Through @monorch/runtime. You rarely touch it directly. Schema parse, permissions, agent steps, and graph advance run there.

Introduction

Monorch is a TypeScript AI control-plane library backed by a Rust execution engine. It is not a framework and not an HTTP stack.

Product lock

Agents, tools, graphs, checkpoints, AiEvent streaming, MCP bridges, memory interfaces, and OTel hooks. Not an HTTP framework, Studio, or RAG product.

What you get

@monorch/ai is the sole user-facing package. Validation, tool authorization, agent run state, and graph orchestration live in Rust and surface through @monorch/runtime.

Mental model

Your HTTP handler owns the request — Fastify, Hono, Nest, or anything else. Monorch owns the agent loop and graph cursor. Model HTTP, tool execute, edge predicates, and checkpointer I/O stay in TypeScript. One AiEvent stream feeds SSE, logs, and optional OpenTelemetry.

What feels different

Interruptible graphs you can checkpoint across requests. MCP tools that become normal tool() defs. Handoffs between named agents. Observability that reuses the same events you already stream to the UI.