Local memory, Cloud Sync, and managed processing

Engraphis starts with a local memory database. Cloud Sync and managed processing are separate choices: connecting an account does not approve readable uploads, and encryption for sync does not describe the data that a processor must read.

This guide follows the published v1.7.8 sync documentation, connection guide, and local and hosted plan documentation. Current prices and trial terms are on the plan comparison; your account determines current hosted access.

Local storage and recall

The free engine, dashboard, MCP server, and manual consolidation run on your machine without a hosted account. Local memory is stored in SQLite. You choose the workspace and repository scope and can inspect the records in the dashboard.

Local storage and recall do not require sending memory content to Engraphis Cloud. Model downloads and optional features that call a configured LLM provider have their own network behavior. Review those settings before submitting private content to any provider.

To try the local workflow first, follow one convention across two sessions.

Optional Cloud Sync

Cloud Sync is part of the hosted Pro and Team offer. The customer client encrypts eligible workspace changes before they leave the device. Secret and session-scoped memories stay local. The relay stores encrypted bundles; it does not receive the workspace encryption key.

You hold that key. Connecting an account does not create or back it up. Before the first upload, configure it using the documented local setup, keep a separate secure backup, and confirm you can retrieve it. Use the same key on an additional authorized device. Engraphis Cloud cannot recover a lost key or decrypt old bundles without it.

Follow the published customer setup instructions. Never paste an encryption key or a connect token into a public issue or support request. Check the completed sync status; a partial or empty operation does not establish a useful result.

Separately approved managed processing

Analytics and managed automation need readable input to produce results. Explicit workspace approval in Manage → Settings is required before readable managed uploads. A cloud account connection or an encrypted sync does not grant that approval.

Approved processing sends a bounded, readable snapshot over TLS to the hosted processor. Cloud Sync's end-to-end encryption applies to sync bundles, not to that snapshot or to content you deliberately send to a configured LLM provider. Secret memories are excluded from managed uploads.

Review the workspace and processing choice before enabling a schedule. Hosted Auto Consolidation and Auto Dreaming produce proposals for review before local changes; free manual consolidation remains available. Inspect the completed result instead of treating a queued job as success.

Choose the boundary that fits your work

• Keep memory local: use the free engine and local inspection without a hosted account.
• Choose encrypted sync: connect an eligible workspace, configure your key, and check a completed sync.
• Choose managed processing: review and approve the workspace's readable upload boundary before using Analytics or automation.

The Team offer covers account roles, named seats, scoped credentials, organization audit history, and optional sync for eligible workspaces. Shared hosted Team memory and hosted MCP are not yet available. Check Team availability before starting.

Try a useful Pro workflow

The Pro trial lasts seven days after email verification and requires no card. Use an existing workspace when possible, connect your installation, and inspect a completed Analytics result for a growth, retention, or decay signal that helps you decide what to review. Too little history is a real limitation, not something to fill with sample results.

Pro is $10/month or $100/year when you subscribe. See the first-value checklist, manage access in your account, or use private support for account questions.