MorrowMake decisions inspectable.
Agents should have the business context, evidence, and authority boundary needed to act well. Every meaningful change needs a clear owner, an auditable reason, and a useful outcome record.
Open-source business software
Work that carries forward.
Morrow is being built as an agent-first ERP: deep applications that give agents a durable, understandable way to do real business work.
Current focusMorrow Desk is the first application: a trustworthy, MCP-first Desk + CRM foundation. The suite is deliberately not presented as a finished ERP.
The direction
One business module at a time.
Morrow grows through independently owned applications, not a universal object model or a plug-in catalog. Each module owns its policies, lifecycle, audit trail, and small agent interface.
Keep boundaries deep.
Business behavior stays inside the module that owns it. Adapters translate transport; they do not become the policy layer.
Earn trust in public.
Source, release notes, security practices, and limits should make it possible to see what is real before relying on it.
Architecture
Small interfaces. Deep ownership.
See how agent and customer channels reach module-owned business behavior on Cloudflare—and how a bounded context graph can improve retrieval without becoming a second source of truth.
First application
Morrow Desk
A trustworthy Desk + CRM foundation for support work that needs more than a chat window.
Pre-release foundation. Morrow Desk is in active development. It does not claim production readiness merely because a Worker can deploy.
- Operators
- MCP is the normal interface, with a narrow recovery surface for administrators.
- Customers
- An accessible support portal and approved channels meet customers where the work begins.
- Trust
- Business lifecycle, evidence, idempotency, delivery, and audit behavior belong in the module—not in prompts.
Open foundation
Release the evidence, not just the code.
Morrow is developed in public from a new, neutral history, with documentation, governance, security policy, and automated release checks that outside contributors can inspect.
Clean source
A new root with no tenant records, private deployment identity, or inherited history.
Honest docs
Clear scope, deployment path, architecture boundaries, and known V1 limits.
Repeatable releases
Checks, release evidence, security reporting, and change policy that can be inspected.
Open participation
A contribution path, governance model, and project roadmap that welcome independent work.
Follow the build, not a promise.
Read the current product scope and the public-release criteria before treating Morrow Desk as a production support desk or Morrow as a complete ERP.