Use cases · Teams

A shared source
of truth you own.

For small teams that keep a knowledge base in a shared folder or repo — handbooks, docs, and runbooks in plain markdown. Portable, encryptable, and versioned, with a one-time license instead of another monthly bill.

See pricing

Honest about what this is

Ampersand is not real-time multiplayer editing. It is a great editor for a team that shares a folder or repo of markdown and syncs it with git, iCloud Drive, or Dropbox. If you want plain files, real ownership, and no lock-in — read on. If you need live shared cursors, this is not that tool.
Docs the team can trust

One knowledge base,
zero lock-in

The pieces a small team needs to keep shared docs clean, safe, and portable — over files everyone can read.

Share a folder, not a platform

Your knowledge base is a directory of plain .md files. Sync it with git, iCloud Drive, or Dropbox — everyone edits with the tool they prefer, and nothing is trapped in a service.

No lock-in, ever

Standard markdown means your docs are portable by default. Fork the repo, move to another host, or open the files in anything — the team owns its own words.

Consistent, branded export

Turn a handbook or proposal into a clean PDF, Word, or HTML document with consistent margins, headers, and page numbers — so everything that leaves the team looks the same.

Encrypt the sensitive parts

Lock individual notes with per-note encryption (age + Touch ID). Credentials, incident notes, and contracts stay ciphertext on disk while the rest of the vault stays open.

Version history built in

Every save is tracked with a timeline, diff, and one-click restore per file — a safety net beneath whatever git or cloud sync you already use.

Bring your own AI keys

The team controls its own providers and spend — Claude, OpenAI, Apple Intelligence, local models, or CLI agents. No AI seats bundled into a bill you did not choose.

team-vault/
team-vault/
├── handbook/
│   ├── onboarding.md
│   └── engineering.md
├── runbooks/
│   ├── incident-response.md
│   └── deploys.md
├── rfcs/
│   └── 0007-search.md
└── contracts.md.age   # encrypted
Share the folder

Sync it the way
you already work

Put the vault in a git repo for branches, review, and history — or in iCloud Drive or Dropbox for effortless syncing. Because every doc is standard markdown, there is no proprietary server in the middle and no migration to dread later.
  • Git, iCloud Drive, or Dropbox
  • Plain .md — portable by default
  • Multiple vaults for separate spaces
Everyday use

The documents a
team lives on

From the handbook a new hire reads on day one to the runbook someone opens at 3am, it all sits in one searchable vault — with the sensitive parts encrypted and every change recoverable.

  • Onboarding handbooks and team wikis
  • Runbooks and incident playbooks
  • RFCs, specs, and design docs
  • Meeting notes and decision logs
  • Policies with per-note encryption
  • Multiple vaults for separate spaces
contracts.md.age — locked at rest
Restore any earlier version
Switch between multiple vaults
One-time license, up to 3 devices
Safe by design

Protect the docs
that need it

Lock individual notes with per-note encryption backed by a vault passphrase and Touch ID, so credentials and contracts are ciphertext at rest even inside a synced folder. Version history keeps a per-file safety net, and multiple vaults keep spaces cleanly apart.
  • Per-note encryption with Touch ID
  • Version history with restore
  • Separate vaults per team or client

Review like code

Keep the vault in git for branches, pull requests, and a full audit trail.

One house style

Export handbooks and proposals with consistent, branded PDF and Word output.

Own the AI bill

Bring your own provider keys — the team controls the model and the spend.

Leave anytime

Plain files mean no migration project the day you decide to move on.

Questions

Good to know

Does Ampersand support real-time collaborative editing?

No — and we want to be clear about that. Ampersand is not multiplayer. It is built for teams that share a folder or repo of markdown and sync it with git, iCloud Drive, or Dropbox. Everyone works in their own copy and changes come together through your sync tool, not a live shared cursor.

How do we actually share the knowledge base?

Point everyone at the same vault folder and sync it however your team already works. A git repo gives you branches, review, and history; iCloud Drive or Dropbox gives you effortless syncing. Because it is all plain .md, any of these work without a special integration.

Can we keep sensitive documents protected?

Yes. Individual notes can be encrypted with a per-note key protected by a vault passphrase and Touch ID, so contracts, credentials, and incident notes are ciphertext on disk. Multiple vaults let you separate a shared team space from private work entirely.

What does it cost for a team, and is it per seat?

The editor is free forever. Pro is a one-time $29 launch price (regularly $49) per person, valid on up to three devices, with a 14-day money-back guarantee. There is no per-seat subscription — you buy licenses once and own them.

Get started

Give your team
docs it can keep.

Free forever for the full editor, with a one-time Pro license per person and no per-seat subscription. Start with a shared folder and grow from there.

Free to start · macOS 13+ · No account required