Knowledge changes.
A .gram file remembers.

Thegram

.gram keeps
every moment
between us.

r0Now

Mac

One file
for every desk

Five .gram files on this Mac, in a team Vault and in Google Drive, used in Thegram for Mac. One of them is a product launch told through Slack and Gmail. Try Thegram in the web app

Light Dark

iPhone & iPad

The same file
in your pocket

Thegram for iPhone and iPad opens the same .gram files: the dashboard, every past revision, the graph, the document, its history and search. It is in beta on TestFlight for iOS 26 and iPadOS 26. On any other device, the web app opens them in a browser. Join the iOS beta

AI agents

Memory your
agents share

Claude Code, Codex, OpenCode and OMP on your Mac, and ChatGPT in the cloud, read the same .gram memory before they answer and record decisions, tasks and what happened as they work. Each write is a new revision, so you can see what your agents knew on any day. How agent memory works

Privacy & security

Know where
your data goes

Local files can stay on your Mac and work offline. When you connect a Vault or Google Drive, the related documents are sent to the service you chose to sync and use. Read the Privacy Policy

Vault storageEncrypted at restActive Vault data and backup archives created after the P3 rollout are sealed with AES-256-GCM. Older backups and storage remnants have not all been erased, so this does not cover every historical copy.At-rest encryption · not E2EE
While processingThe server can read itThe Vault server decrypts content in memory for Core and MCP. This is not end-to-end encryption; data is plaintext while the service processes it.Memory · tmpfs
Vault MCP agent accessGrant each connectionAccess is scoped per OAuth client_id: none, read, write or delete. Each client’s first connection defaults to write for a Thegram Vault you own; other Vaults default to none. Google Drive access is controlled separately.OAuth client_id · least privilege

Encryption keys are kept in the cluster and a copy on the operator’s Mac, not an external KMS. This does not protect against whole-node disk theft or access to a running server. Local-only use remains offline; configured Vault or Drive sync transmits the data needed for that service.