---
title: instibrain vs Markdown in a Git repo: what a team adds
description: Git is a good home for Markdown, and a small technical team can keep its pages there; a team that puts every AI on those pages needs what a repo leaves out.
url: https://instibrain.ai/compare/git
updated: 2026-11-10
site: https://instibrain.ai/llms.txt
---

# Git is a good home for Markdown. A team's AIs need more.

A repo is the first weekend of a brain. A team adds readers per space, one address for every AI, and a host that cannot read what it must not.

a Git repo is enough for  A small technical team that reads everything.
- everyone reads every page
- Claude Code on a clone
- review in pull requests
a brain adds  What a repo leaves out.
- readers per space
- every AI, web and phone too
- sync with no commit
- sealed from the host
- a check on every save

first, what Git does better

## Git wins on five counts.

If one of these decides it for you, keep your pages in a repo.

- Free for a team Git costs nothing. A brain is free for one person only.
- Open source You can read Git's code. Ours is not published.
- On your own server Any host you choose. We host the brain.
- Offline Every commit works with no network.
- Review first Branches and pull requests. A brain has neither.

the differences

## Seven differences, a picture each.

On the left, Markdown in a Git repo. On the right, the same Markdown in a brain.

1

### Who reads what?

a Git repo

company-docs · one repo
- pricing/
- pay/
- legal/
- sales
- finance
- a contractor

All three read pay/ and legal/ too.

Whoever has the repo reads all of it.    a brain

team
- everyone
finance
- finance
legal · sealed
- two people
Each space has its own readers.

**The detail**

a Git repoA Git host grants read access to a whole repository. What only some people may read needs a repository of its own, and an AI with the repo reads every file in it.

a brainEach space has named readers, editors and managers, and a space is shared whole: no folder inside it is shared on its own. An AI reads only the spaces its person gives it, never more than its person. Spaces.
2

### How does a change reach everyone?

a Git repo

-  commit
-  push
-  pull, by each reader

Until a reader pulls, their AI answers from the old page.

A commit, a push, and everyone's pull.    a brain

-  save
-  synced for you

Every AI reads the new version at its next read.

Save. Every AI reads it next.

**The detail**

a Git repoA change is a commit, then a push, then a pull on every machine that reads it. That works well for people who live in Git, and it is three steps nobody else takes.

a brainThe sync client runs at login and syncs after each burst of edits, and as soon as a teammate's change reaches the brain. When two people changed the same page, yours stands, the brain's copy lands beside it, and your AI merges them. How it keeps in step.
3

### Which AI reads it?

a Git repo

- a coding AI, on a clone
- an AI on the web
- an AI on the phone

The last two only through a connector to the Git host, with the whole repository.

The AI that has a clone.    a brain

- Claude Code
- Codex
- Claude on the web
- Claude on the phone

One address, over MCP. ChatGPT and Cursor speak MCP and have not run on our brain yet.

Every AI you connect, at one address.

**The detail**

a Git repoA coding AI reads a cloned repo as files. An AI on the web or the phone has no clone: it reaches the repo only through a connector to the Git host, and that connector opens the whole repository.

a brainAny AI that speaks MCP connects to the brain's address. Run on our brain: Claude Code on Mac, Windows and Linux, Codex, and Claude on the web and the phone. ChatGPT and Cursor speak MCP and have not run on ours yet, so we promise no result for them. Connect your AI.
4

### What history does it keep?

a Git repo

```
a91c3f2 raise the enterprise floor
7be02d1 add the Acme exception
40c9e11 first pricing page
every commit, for good
```

Every commit, for everyone with the repo.  Git keeps more, for longer     a brain

```
v41 a person, in the browser
v40 an AI, as its person
v39 a computer, from a file
each save names its writer
```

Every save names its writer.

**The detail**

a Git repoGit keeps every commit for good, with its author and its diff, and everyone with the repository reads all of it.

a brainEach save is a version that names its writer: a person, a computer, an AI, or an agent. An open space keeps every version for 30 days, then one a day for a year, then one a week. A space's managers read old versions; readers and editors read the page as it is now. Our server keeps no version of a sealed page: with Git on, your computer does. Version history.
5

### What can the host read?

a Git repo

```
pay/bands.md, on the host
senior engineer: band 4
raise cap: 8% a year
```

The host reads every file.    a brain

```
sealed, on our server
rT9b8QDUyii5i+4ftgFBFd0C1brw==
UqEW2qJ84uwjJFQu4hKyH3oELpNmxG3n==
```

A sealed space reaches us as ciphertext.

**The detail**

a Git repoA Git host reads the whole repository, unless your team encrypts files itself. On your own server, the host is you, and that is a real answer.

a brainAn open space is not hidden from us: our server reads it, which is how a web AI and a phone read it. A sealed space is encrypted on the computers of the people it is shared with, and we hold ciphertext, so no web AI or phone reads it. We still see its size and timing. The limits, in full.
6

### What keeps it true?

a Git repo

-  branch
-  pull request
-  a reviewer, if asked

A person reads the change before it lands.

Review, where your team asks for one.  Git reviews before a change lands     a brain

```
the check's answer to a save, an example
line 5  history: "we decided"
line 9  a long sentence, 34 words
line 12 a sentence pricing/floors.md holds already
```

A check on every save, which refuses nothing.

**The detail**

a Git repoBranches, diffs and pull requests let a person read a change before it lands. A brain has no branches and no pull requests: if every change must pass a review first, Git does that and instibrain does not.

a brainA check at every save flags a line that is too long, vague, written as history, or repeated from another page. It refuses nothing, so a person still decides. A save lands at once, and any version comes back. An AI that may not write a page leaves a proposal, which an editor applies. The check, on a real page.
7

### Who can write a page?

a Git repo

```
$ git add pricing/floors.md
$ git commit -m "raise the floor"
$ git push
```

Whoever can commit.    a brain

- in the browser: Edit, then Save
- as a file, in any editor
- through their AI

A sealed space's page is a file on a computer alone.

Anyone the space lets write, with no Git.

**The detail**

a Git repoWriting a page means a commit. That suits engineers, and it keeps most of a company out of the pages its AIs read.

a brainA space's editors open the page in the browser, click Edit, change the Markdown, and save. The editor opens the pages of open spaces; a sealed space's page is a file on a computer, edited there. The editor.

side by side

## The whole comparison in one table.

Each row is a difference above; its detail is there.

| The question | Markdown in a Git repo | instibrain |
| Who reads what? | The whole repo, or none of it | Readers set per space |
| A change reaches everyone | Commit, push, each one's pull | On save, by the sync client |
| Which AI reads it? | A coding AI with a clone | Every AI you connect over MCP |
| History | Every commit, for good | Every save, thinned after 30 days |
| Review before it lands | Branches and pull requests | None; a check on every save |
| What the host reads | Every file | Open spaces; never a sealed one |
| Who writes a page | Whoever can commit | Editors, in the browser too |
| Price and source | Free, open source, self-hosted | Free for one person; hosted by us |

Git here is Git as its own documentation describes it, with a host your team chose. What a host grants is in that host's documentation. The same argument, beside a skill and a project in an AI's app: a repo, a skill, and a project.

which one

## Choose by who reads, and through which AI.

When everyone reads everything through a clone, a repo does the job.

choose instibrain if Not everyone reads everything, or not everyone uses Git.
-  Some pages are for a few people: pay, legal, a client's file
-  Your team's AIs run on the web and the phone, not only in a terminal
-  People who never used Git have to write and correct pages
-  Some pages must be closed to the host that stores them

a Git repo is enough if A small technical team reads all of it, from a clone.
-  Everyone on the team may read every page
-  Everyone works in Claude Code, or another coding AI, on a clone
-  You want every change reviewed in a pull request before it lands
-  Free, open source, and on your own server matter most

together

## Keep Git. The brain's folder is Markdown too.

One setting commits each space's folder to your own Git at every sync.

-
Start from your repo Markdown you already keep becomes pages as it stands: put the folder in a space, and it syncs
-
Keep your own history With `INSTIBRAIN_GIT=1`, each sync is a commit in a Git repository on your computer
-
Sealed history is Git's Our server keeps no version of a sealed page. With Git on, your computer does

What a team builds on top of a repo before every AI can read it: a repo is the first weekend.

questions

## What people ask who keep their Markdown in Git.

**Why not keep our Markdown in a Git repo?**

Keep it there if your team is small, technical, and reads all of it. A repo holds the pages and their history well. It gives each reader the whole repository, and an AI on the web or the phone reaches it only through a connector to the host.

**Can we use Git and instibrain together?**

Yes. Each space is a folder of Markdown on your computers. Set `INSTIBRAIN_GIT=1`, and the sync client commits the folder to a Git repository there at each sync.

**Does instibrain have branches or pull requests?**

No. A save lands at once, every version names its writer, and any version comes back. An AI that may not write a page leaves a proposal, which an editor applies. If every change must pass a review before it lands, Git does that and instibrain does not.

**Can someone who never used Git edit a page?**

Yes. They open the page in the browser, click Edit, change the Markdown, and save. The editor opens the pages of open spaces. A sealed space's page is a file on a computer, edited there.

**What does instibrain not do?**

It runs no AI and imports no documents. We host the brain: you cannot run it on your own servers, and its source is not published. A personal brain is free, up to 200 pages and 20 MB; a team's price is by request.

## Give every AI your team uses the same pages.

Start with a free personal brain. For a team's account, write to us.

Sign up free  →
compare  instibrain vs Basic Memory

Open source and self-hosted, or readers per space and sealed.
compare  instibrain vs Obsidian

One person's vault, or a team's pages for every AI.
compare  All comparisons

What instibrain does not do, said first.

---

instibrain is made by WebWork AI, Inc. Everyone uses the same models · the difference is what yours knows.
