Running agents in parallel, and together, is a mess.
×
You coordinate every agent by hand
Agent work sits in a flat local list, not a live log other
agents and tools can react to, so you run the tests, trigger
the next step, and wire every handoff.
×
No one else can join a run
A session is trapped on the machine it started on, so a
teammate can’t watch or join it and another agent
can’t pick up where one left off. Working together means
pasting transcripts after the fact.
×
Parallel agents diverge without visibility
Each runs in its own VM, blind to the others’ changes
and how they relate, so the work drifts apart into merge hell.
×
Hosted orchestrators aren’t local-first
Cloud-hosted agents lock your environment, tools, and data to
a vendor’s app, limiting your control and the workflows
you can build.
The root cause
Git was built for one codebase, not a whole system of work.
As a version control system it only tracks text files, line by line.
Commits and syncs are manual, so work and the context behind changes
get lost, submodules barely work, and there is no real access control.
Git versions
Code
It can’t see
EnvironmentPlansDecisionsTranscriptsIssuesReviews
Different data, different access, different audiences.
Syncs in fromGitHubLinearNotion+ Postgres, REST, …
Inference workers runClaudeGPTGemini+ open models
Local
A collaborative, versioned harness in your terminal.
Sessions as a versioned logParallel branches, no worktreesFork, explore, keep the bestAttributed, shared changelogMove runs between machines
Web
Agent workflows made easy to share and collaborate on.
SessionsCanvasesConnect your agentsCheckpoints & revertExtensible harness
Ecosystem
A few primitives that birth an ecosystem.
Every piece is one typed object on the shared log, so they
interoperate by default. Build the part you need, run it on your
machine, deploy it, or publish it for others. No integrations, just
the same log.
Workers
Watch the log and do the work, inference, tools, and evals,
running in your own sandbox on any host.
Tools
Give agents new capabilities to call. Build a tool once and any
session can invoke it.
Connectors
Sync outside data in and out, GitHub, Linear, Notion, Postgres,
a REST API, while the log stays the source of truth.
Canvases
New surfaces on the same data: a review canvas, a board, a
dashboard. Just another view of the log.
Workspaces
Package how your team works, sessions, tools, and layout, into a
workspace others can fork and extend.
Network effects
GitHub owns the network around repos. Mod owns it around agent
workspaces.
GitHubrepos
Git commoditized version control. GitHub captured the network on
top, collaborators, identity, and discovery, and became the
default home for code.
Modagent workspaces
The harness is commoditizing the same way. Mod captures the
network around the whole workspace, sessions, agents, tools, and
people, not just code.
Every shared session, fork, and published workspace pulls in the next
collaborator and the next builder. Shared work brings teammates, the
ecosystem brings builders, forks spread the substrate, and the graph
of who built what only lives in Mod.
Market
Agents need infrastructure for collaboration.
$165B+
$60B
$8B
$8B· The wedge
Agent infrastructure. The layer teams already buy to run
agents, growing ~46% a year. Where we land.
$60B· The category
Collaboration software. Docs, trackers, design, code
hosting, all built for humans coordinating with humans, all
getting rebuilt for humans and agents.
$165B+· The prize
The digital workplace. As work shifts to fleets of agents,
the value moves to the infrastructure layer the whole stack
runs on.
Every team is becoming a few people and a hundred agents.
We’re not building a better app, we’re building
the layer the next generation of them runs on.
Competition
Productivity apps bolt AI on. Mod is the infrastructure
underneath.
The market we take
Productivity & collaboration apps, built for the human
era.
What the agentic age needs
Productivity apps
Mod
Versions the whole system, not a silo
◐
●
Agents as first-class collaborators
◐
●
Parallel agent work: branch & merge
✕
●
Checkpoint, attribute & roll back
✕
●
Local-first, runs on your infrastructure
✕
●
One programmable substrate, not a fixed app
✕
●
An app can add AI features. It can’t become
infrastructure. That gap is the whole opportunity.
Team
Built by the people who built the primitives.
Nassar Hayat
Co-founder & CEO
Head of Platform at MultiOn, building browser agents.
Led the developer ecosystem team at Radicle, a
peer-to-peer GitHub alternative. Co-founded Foodchain, a
B2B platform bootstrapped to $5M ARR.
Built
Alex Good
Co-founder & CTO
Lead maintainer of Automerge, the leading open-source
CRDT library, at Ink & Switch. Led the protocol team
at Radicle. Co-founded Foodchain. Speaker at Local-First
Conf and QCon London.
Built
Years of R&D on local-first collaboration and agent
architectures. We have shipped together before.
Longtime collaborators, and each other’s best man.
GTM
We sell the infrastructure agents run on.
We sell subscriptions that bundle the four things agents
consume:
OS inferenceStorageHosted VMsSync
Revenue
(ARR)Teams
We launch in ~3 months. Year-3 target: Cursor’s ~50k team
scale and $250M ARR (~$5k per team).
0 → 1k teams · $5k ACV
Open source or free tier to seed adoption
Developers find it, use it, love it, bring it into their
team
Team usage triggers upgrade/paid conversion
Content + community (HN, Reddit, X, YouTube) drives top of
funnel
Land and expand: start with one team, spread across the
org
Traction
Technical leaders are already pulling for it.
“Give me a way to share my agent data with the team and I
will stop using Linear, GitHub, and Notion.”
Engineering leaderCloudflare
“Our product and engineering teams are stuck in so much
grunt work trying to organise and collaborate on plans.”
Director of AISnyk
“We’re struggling to manage agents across Notion for
specs, Linear to track, and a separate GitHub repo for local
context.”
CTORecall AI
“Our teams own idea-to-deploy individually, but it’s
hard to collaborate on design and review.”
CTOAGI Inc
“It’s hard to review agent-generated code. Tracking
the full context would be very helpful.”
Engineering managerRemote.com
“Worktrees don’t work.”
FounderNominal.dev
“I set parallel agents off to work and their output is
mostly useless, they have no context of what the others did.”
FounderReflex AI
“Everybody’s building the same thing: prompts replace
code, a thread viewer replaces the file viewer. But who’s
going to figure out collaboration? I’m bullish on sync
engines.”
CTOParadigm
“GitHub is dying and git is not the right primitive.”
CEOT3
“GitHub was the best solution for 2010. In 2026 it’s
hanging on by a thread. The needs of today are so different the
form factor doesn’t work anymore.”
Founder & CTOHashiCorp
“Git worktrees are fun and all, until you have 3,563
instances of node_modules.”
EngineerOpenCode
“Feels weird that git still can’t manage empty
directories, or submodules that aren’t the root of another
repo. Git submodules are pretty lame.”
Creatorpi.dev
The ask
Raising to reach the first 1,000 teams.
$5M
To grow the team below and put Mod in front of its first 1,000
teams.