Why Monora: the missing middle between Drive and git

Two tools, each missing half

If you’ve tried to give your team and your agents a shared knowledge base, you’ve felt this. There are two mature options, and each is missing exactly what the other has.

• Google Drive / Notion have per-folder permissions. Anyone can use them. But there’s no file tracking underneath - no clean diffs, no branches, no reviewable history. An agent can’t cleanly edit, version, or review, and structure quietly drifts.
• Git has the agent loop - diffs, branches, PRs, file-writing agents. But access is all-or-nothing per repo: clone it and you have everything, including all history.

So you’re forced to choose between safe-but-dumb and smart-but-leaky. Monora exists to refuse that choice.

The bet: a folder is a git repo

Monora’s architecture is one decision followed to its conclusion: the unit of access is the folder, and a folder is one git repository. Its access-control list lives with it.

From that, the rest falls out:

• A connector clones the folders you’re authorized for and composes them into one local working tree - your view of the brain. You operate on a normal git tree; your agent never knows the difference.
• Write-back is a normal git push per folder, gated by write permission. There is no fragile reverse-projection step.
• Underneath it’s real git: every change has an author, a diff, and a reviewable history, plus an access log of who - and which agent - read what.

Enforced, not hidden

The permission check happens on the server, on every fetch and push. A folder you’re not authorized for is absent from your clone and its history - not greyed out, never written to your disk. That’s the difference between a UI that hides things and a system you can actually trust with the board deck.

The same brain, the right view for each

The payoff is one coherent company brain where every member - a teammate or an autonomous agent - sees only their authorized folders, assembled into a real git tree. You stop feeding your agents everything. You give them exactly the right context, safely.

The company brain itself is commoditized. The permission layer is the product. That’s Monora.