TokST Persistent memory for people and AI agents

TokST Editions

TokST runs through one CLI, one MCP package, and one cross-platform release system. Choose Local or a cloud plan based on where memory is stored and how workspaces are shared.

EditionMonthly priceWorkspaces and AtlasesMonthly callsStorage
LocalFreeOne default workspace and Atlas on setup; additional local spaces are unlimitedLocalLocal disk
Cloud FreeFree1 personal workspace, 1 Atlas total1,000500 MB
Starter$3.93 personal workspaces, 5 Atlases per workspace, 15 total2,0002 GB
Pro$9.910 personal workspaces, 20 Atlases per workspace, 200 total10,00010 GB
Max$29.9Unlimited personal workspaces and Atlases50,000100 GB
Team$19 / workspace1 subscribed team workspace, 50 Atlases, 3 seats20,000 shared20 GB shared
EnterpriseContractContract capacityContractContract

Local

Local is free on macOS, Linux, and Windows. tokst setup --local creates a SQLite profile with a default workspace and Atlas. The same @tokst/cli and @tokst/mcp-server packages support local mode. Memory, attachments, search indexes, and backups remain on the current device.

Personal cloud plans

Free, Starter, Pro, and Max manage personal workspaces only. They can join any paid Team workspace through an invitation. Activity in a Team workspace uses that workspace subscription, seat, calls, and storage.

Team workspace subscriptions

Each Team workspace carries an independent subscription and Billing Owner. A user may belong to any number of Team workspaces. Team starts at $19/month for 3 seats, 20,000 shared calls, 20 GB shared storage, and 50 Atlases. Add-ons are $4/month per seat, $5/month per 50,000 calls, and $5/month per 100 GB.

Team provides Owner, Admin, and Member governance, trusted Agent identity, direct and broadcast Agent messages, and workspace audit. Team setup is assigned by an administrator in the current release; checkout and recurring billing follow in a later billing release.

Enterprise

Enterprise is annual contract only. It provides custom capacity, organization management, SSO, audit retention, SLA, deployment options, and migration support. Contact sales to provision it.

Calls and migration

A call is an authenticated CLI, MCP, or REST memory operation, search, context request, attachment upload initialization, Agent message, or workspace write. Login, OAuth, dashboard browsing, and download links are excluded. Calls and files use the target Atlas workspace: personal workspaces consume account quotas and Team workspaces consume shared quotas.

Former user-level Team accounts remain Legacy. Existing Team workspaces retain their 200,000 calls and 500 GB entitlement. Existing resources remain available; new resources follow the current plan limits.

Local-to-cloud sync

A Local Atlas can be explicitly bound and manually synchronized to a cloud Atlas. Sync transfers memory content, metadata, status, and tags. Attachments stay local, and conflicts preserve both records.

See the product overview.