One shared memory for every AI you use

Bitsy syncs read-only context from 8 work apps and distills your conversations into source-cited facts. Every assistant reads the same truth over MCP 2025-06-18.

Sources
8
AI assistants
8
Vault cipher
AES-256-GCM
Vault boundary
AES-256-GCM Read-only
Source stream gmail.readonly
Re: Launch schedule & investor check-in [Gmail · 14 min ago]

Investor demo with Northwind Ventures moved to Thursday at 4:00 PM IST

Investor demo scheduled for Tuesday at 2:00 PM IST Replaced
Recalled over OAuth 2.1 + PKCE (S256) Token-scoped
Claude -> recall("gmail") 1 fact

How it works

Read-only collection, standalone facts, universal recall

01 · Connect read-only

Approve apps on their own sign-in screen

Connect any of the 8 supported sources with read-only OAuth scopes. Bitsy skips unchanged documents and re-syncs automatically every 6 hours.

Gmail Google Calendar Google Drive GitHub Notion Slack Linear LinkedIn
02 · Distill facts

Current truth replaces stale notes

Gemini (gemini-3.5-flash-lite) turns raw threads and docs into concise standalone facts. When a schedule, owner, or status changes, the newer fact supersedes the old one automatically.

03 · Recall everywhere

One MCP vault for 8 AI clients

Add https://mark-100.tailca891a.ts.net/mcp once. Every assistant checks your memory before answering and logs what it learned.

Connected sources

8 apps synced with read-only permissions

Inspect exact OAuth scopes

Gmail

Live

Recent emails from the last 90 days, excluding promotions and spam.

gmail.readonly · openid · email

Google Calendar

Live

Events from the past 30 days and the next 60 days.

calendar.readonly · openid · email

Google Drive

Live

The text of your most recently edited Google Docs.

drive.readonly · openid · email

GitHub

OAuth

READMEs of your recent repositories and your recent issues and pull requests.

read:user · repo (read-only sync)

Notion

Live

The text of pages you share with Bitsy, most recently edited first.

notion.readonly · owner=user

Slack

OAuth

The last 30 days of messages in channels you belong to.

channels:history · channels:read · groups:history · groups:read · users:read

Linear

OAuth

Your most recently updated issues and their status.

read

LinkedIn

OAuth

Your LinkedIn profile details (and posts when social read access is granted).

openid · profile · email

AI assistants

Works across 8 web apps and coding agents

View MCP setup steps
Claude
Anthropic · Web & desktop
ChatGPT
OpenAI · Web & desktop
Gemini
Google · Web & desktop
Le Chat
Mistral · Web & desktop
Claude Code
Anthropic CLI · Coding agent
Gemini CLI
Google CLI · Coding agent
Cursor
Cursor IDE · Coding agent
Codex
OpenAI CLI · Coding agent

Security architecture

How Bitsy protects your credentials, notes, and AI connections

Every integration boundary is enforced on the server before data is stored or returned to an AI client. Nothing relies on prompt promises alone.

Full security specification
01 · Upstream sources
Read-only OAuth scopes
gmail.readonly · drive.readonly · calendar.readonly · linear:read
Write access: none
02 · Isolated vault
Sealed per-user store
AES-256-GCM tokens · scrypt + SHA-256 auth · user_id isolated SQLite
03 · MCP 2025-06-18
Scoped AI assistants
OAuth 2.1 + PKCE (S256) · Single-use refresh rotation
One-click revoke anytime
01

Strict read-only source scopes

Bitsy only requests read scopes from your apps. It cannot send emails, edit Notion pages, comment on Linear issues, or post to Slack.

Provider OAuth apps request gmail.readonly, calendar.readonly, drive.readonly, Linear read, and user-approved Notion pages.

Every provider consent screen lists the exact read-only permissions before you approve access.

02

AES-256-GCM credential sealing at rest

Third-party OAuth access and refresh tokens are encrypted with authenticated AES-256-GCM using a dedicated key stored outside the SQLite file.

Every token is sealed with a fresh 12-byte random IV and GCM authentication tag via BITSY_SECRET_KEY or a mode-0600 key file.

A copy of bitsy.db alone exposes zero usable upstream provider tokens.

03

OAuth 2.1 + PKCE and rotating tokens

AI assistants connect over OAuth 2.1 with mandatory S256 PKCE verification, 1-hour access tokens, and single-use rotating refresh tokens.

Access tokens, refresh tokens, auth codes, and session cookies are stored solely as SHA-256 hashes — plaintext tokens never persist.

Reusing an old refresh token fails immediately, and removing an assistant invalidates its entire token family at once.

04

Per-user isolation and instant deletion

Every document, extracted fact, conversation, and lookup log is partitioned by user_id, with strict HTTP headers and one-click removal.

Passwords use random-salted scrypt with timingSafeEqual; web responses enforce nonce CSP, HttpOnly cookies, and open-redirect checks.

Clicking Forget archives a fact immediately so no assistant receives it again, and disconnecting purges source access.

Pricing

Start free, upgrade when you connect more AIs

All paid plans include a 7-day free trial with no card required to start.

Compare all plans

Free

$0 forever

Try cross-AI memory with one assistant and core connectors

  • 1 connected AI assistant over MCP
  • Up to 3 read-only source connections
  • Full-text + vector hybrid recall
  • One-click forget & instant revocation
Start free

Pro

7-day trial
$10 per month

For solo founders and developers switching across multiple AI tools daily

  • Up to 3 AI assistants in sync
  • Up to 20 read-only connected accounts
  • Automatic 6-hour background re-sync
  • Contradiction replacement & Gemini embeddings
Start 7-day trial

Max

$49 per month

Unlimited AI assistants and accounts for heavy daily workflows

  • Unlimited web, desktop, and CLI assistants
  • Unlimited read-only connected accounts
  • Priority Gemini fact extraction & recall
  • Full conversation & lookup audit history
Start 7-day trial

Team

$25 per seat / month

Shared workspace context and central billing for teams of 3 to 30

  • 3-seat minimum · central workspace billing
  • Private personal vaults isolated from shared knowledge
  • Role-scoped team access & approval workflow
  • Unified OAuth 2.1 + PKCE token governance
Choose Team plan