Browse documentation

Help / Cloud and Teams

Cloud and Teams

How hosted and shared memory differ from Recon Local without blurring the storage boundary.

Recon Local, Cloud, and Teams share a product idea but not the same storage boundary.

Local

Local is free private memory for one person on one Mac. Its PGlite store is authoritative for that installation. It reads selected local sources and works with the AI account you choose.

Cloud

Cloud is one hosted authoritative memory for an individual who needs connectors, access beyond one Mac, or continuity across environments. It is not a hidden table-level synchronization between an unrelated Local database and a hosted database.

Hosted Recon already has connector infrastructure for systems such as Notion. The Local app does not yet bridge those hosted connectors into its private store.

Teams

Teams uses the hosted substrate with multiple contributors, permissions, source receipts, and reconciliation when people or systems disagree. The value is shared reasoning: engineering can understand customer constraints, customer teams can understand technical trade-offs, and both can see why a decision changed.

When to ask for access

Request Cloud or Teams when you need one of these:

  • Notion or another hosted connector in the same memory
  • access from multiple machines
  • shared memory across contributors
  • permissions and team-level source boundaries
  • reconciliation of conflicting team or system evidence

Contact Recon with the sources, contributors, and workflow you need. Access is opened with early users based on real demand; the Local app does not pretend those connections are already active.