PeppermintGet started

Three ways to start

The pricing stays simple: one plan for yourself, one for teams, and one for larger deployments that need more structure.

Personal

FreeFor individual use

Start with a private memory layer for your own work and keep the thread intact across the tools you already use.

  • Private work memory for one person
  • Works across Slack, Docs, Codex, and Claude Code
  • Ask what changed, draft updates, and recover decisions
  • macOS today
Get started

Most teams start here

Team

$47Per user / month

Bring shared context into handoffs, updates, and team conversations without giving up private-by-default control.

  • Permissioned shared memory
  • Slack, Docs, and Linear reply surfaces
  • Weekly updates, handoffs, and decision recovery
  • Controls for where Peppermint can speak
Start with your team

Enterprise

CustomBy request

For larger rollouts that need procurement, access controls, and a tighter deployment path from day one.

  • SSO and workspace controls
  • Deployment support and rollout planning
  • Shared memory design for larger orgs
  • Direct support for implementation
Talk to us

FAQ

A few of the things people ask first

A few of the things people ask before they trust a memory layer with the thread behind their work.

Not really. Peppermint is the memory layer underneath the model. It turns the thread behind your work into usable memory, facts, summaries, and routines so Slack, Claude Code, Codex, Linear, or the next tool can work from real context instead of a blank box.

The MCP server exposes your memory store: searchable memories, structured facts, daily summaries, collections, preferences, routines, and permissioned team context. In practice, that means another tool can ask for the thread behind the work instead of making you restate it from scratch.

Your memory starts personal. Shared context is permissioned. You decide which replies, summaries, and handoffs leave your private memory layer and which ones stay with you.

Claude and Codex are great interfaces, but they do not keep the ongoing state of your work unless you keep feeding it back in. Peppermint keeps that state intact across tools, so the interface can change without the memory disappearing.

That is the point of the product. The memory stays with Peppermint, not with a single interface. You can move from Slack to Docs, from Linear to Claude Code, or from Codex to whatever comes next without rebuilding the story every time.

Peppermint is designed to run quietly in the background. The goal is to feel like part of your desktop, not another heavy app fighting for attention.