# One knowledge base. Every teammate's AI.

A shared knowledge base that ChatGPT and Claude can actually read. Built for small technical teams, founders, and indie SaaS: one place for the context your whole team keeps re-explaining.

## Everyone's AI, reading the same notes.

What changes when your team's context lives in one place your AI can read.

| Before Hjarni | With Hjarni |
| --- | --- |
| Every teammate explains context to their own AI | Every teammate's AI reads the same team notes |
| Decisions disappear into Slack | Decisions live in a searchable decision log |
| New hires interrupt senior people for basics | New hires ask Claude or ChatGPT first |
| Runbooks are passive docs | Runbooks become instructions the AI can follow |

## One shared brain. Every teammate's AI.

No new habits. Each person keeps the AI they already use.

1. **Put your team's context in shared folders**

   Runbooks, decisions, onboarding, customer interviews. Plain Markdown, one folder per kind of context, each with its own AI instructions.

2. **Everyone connects their own AI**

   Each teammate connects [ChatGPT](https://hjarni.com/docs/chatgpt) or [Claude](https://hjarni.com/docs/claude) to the team's knowledge base. No bundled AI, no per-seat token bills.

3. **Every AI reads and updates the same notes**

   Ask your assistant to search the team's folders before answering and save decisions back. The next teammate's AI can retrieve the updated notes.

One shared knowledge base, one folder per kind of context.

## A new hire asks. The team's notes answer.

No senior engineer interrupted. Claude reads the team's Runbooks and Decisions folders and answers from what's written down.

Claude answers a new hire's deploy question from the team's shared runbook.

## The context you keep re-explaining.

Write it down once. Ask each teammate's AI to check the shared notes.

### Runbooks the AI can read

Deploy steps, rollback procedures, and incident playbooks. Add a folder instruction and your team's AI becomes the first responder, not a wiki nobody opens at 3am.

### Decision logs as institutional memory

Why you picked Postgres, why pricing went flat, what you tried and rejected. When anyone asks "why do we do X this way", the answer comes from the log, not guesswork.

### Shared customer interview memory

Thirty interviews in, ask "what did our last ten customers say about onboarding" and get real answers with real quotes, from every teammate's AI.

### Onboarding for new hires

The unwritten context lives in three Slack channels and one person's head. Write it once and a new hire's AI reads it on day one.

## Simple on purpose, even for teams.

### AI-native, not AI-added

The MCP server is built in, not bolted on. Every folder can have its own AI instructions. Claude and ChatGPT follow them.

### Personal and shared together

Personal notes stay personal. The team knowledge base is shared. One login, both spaces.

### Roles, not all-or-nothing

Give each teammate a viewer, editor, or admin role, from a team-wide default down to individual folders. Sensitive folders stay read-only for most of the team while shared ones stay editable.

### No bundled AI

Team members bring their own ChatGPT or Claude. No per-message costs. No token limits per seat. No surprises on the bill.

## Who can edit what

Everyone on the team can read the shared knowledge base, so every teammate's AI works from the same notes. Roles just decide who can change what.

Each member has a role on every folder: a viewer reads, an editor reads and writes, an admin also manages other members' roles. Set a team-wide default, then override it per folder where you need to. The owner always keeps full control of every folder.

Team-wide rules sit above each folder's own. Every teammate's AI follows both when it reads team notes.

Need SAML SSO, SCIM provisioning, or a per-team audit log? [See Hjarni for Teams (Enterprise)](https://hjarni.com/for-teams/enterprise).

> My notes, generated by AI, shared with my team, so our AI agents always have the full context of everything.

Alvaro B, DevOps

[Read customer reviews](https://hjarni.com/reviews)

> We run Hjarni on Hjarni. Our roadmap, launch checklists, and customer notes live in one shared knowledge base, and Claude reads and updates it every session instead of me re-explaining where things stand.

Evert Van den Bruel, Founder, Hjarni

## Per seat. No AI on the bill.

Teams is **$20 per seat per month** for the shared knowledge base. Seats prorate automatically as people join or leave. Everyone brings the ChatGPT or Claude subscription they already have.

Start free for your first 25 team notes. No card needed.

[Read the teams and sharing docs](https://hjarni.com/docs/teams-and-sharing)

Common questions

## Common questions

**Can my team share memory across ChatGPT and Claude at the same time?**

Yes. The shared notes live in Hjarni, not inside any one AI product, so a teammate on ChatGPT and a teammate on Claude read and write the same knowledge base. That is the difference from ChatGPT memory or Claude Projects, where the context is locked to one product and usually to one person.

**What does a team actually get on the Team plan?**

A shared knowledge base separate from everyone's personal notes: shared folders, team-level AI instructions that every member's AI follows, per-folder viewer, editor, and admin roles, and member management. Each teammate connects the AI they already use to it. SAML single sign-on, SCIM provisioning, and a per-team audit log are available on request for companies that run a security review.

**Can the same note be both personal and shared?**

Each note lives in either your personal space or a team, and you can move it across whenever you need to.

**Do all teammates need their own AI subscription?**

Everyone uses the AI they already have, like ChatGPT, Claude, or Cursor. Hjarni gives that AI a shared memory rather than bundling one, so each teammate keeps their own subscription.

**How does pricing work for teams?**

Teams is $20 per seat per month, free for your first 25 team notes. Seats prorate automatically as people join or leave, and the plan covers shared folders, team-level AI instructions, and member management.

**Can different teammates set different AI instructions?**

Team-level instructions are shared across the team. Personal instructions stay personal.

**Can I control who can edit which folders?**

Each member has a viewer, editor, or admin role on every folder, resolved from a team-wide default and any per-folder overrides. A viewer reads, an editor also writes, an admin also manages other members' roles. Everyone on the team can read the shared folders; roles decide who can change them. Roles cascade to subfolders, and the team owner always keeps full control.

**Which templates fit a team setup?**

[Developer Project Memory](https://hjarni.com/templates/developer-project-memory) and [Customer Interview Repository](https://hjarni.com/templates/customer-interview-repository) are the two strongest team starters. [Meeting Memory](https://hjarni.com/templates/meeting-memory) and [Writing Style Guide](https://hjarni.com/templates/writing-style-guide) pair well once the team is past the first install. Templates build their folder tree in your personal space; move the folders into the team when you bring the team in.