HeapFileAI

Trust

Local-first by default. Governed when AI work becomes shared.

HeapFile separates local memory, account membership, product-owned connectors, mobile handoff, and organization controls. That keeps Free useful while making Premium cloud, data-center, and team features explicit.

Local-first

Free starts on device

Local memory and local evidence stay on the user's computer unless a cloud feature is explicitly configured.

Entitlements

Server-side gates

Desktop UI can explain tiers, but Premium cloud services must enforce paid access at their own server boundary.

Connectors

Authorized evidence

GitHub, AWS, Microsoft, Atlassian, and future connectors should use HeapFile-owned authorization flows and customer scopes.

Local AI

Compute is not context

Bring your own inference through Ollama, NIM, vLLM, hosted APIs, or enterprise stacks. HeapFile preserves the sourced memory, approval boundary, and evidence trail around them.

Account gate

heapfile.com owns account, billing, and access. heapfile.ai owns install and setup.

Users should not download the AI client from a public anonymous link. Send them to heapfile.com first, then show the correct installer and setup path for their account tier.

Local-first, not local-only. No overclaims. A cloud connector contacts its provider only over a route you authorize, and HeapFile names the permission level and data route first. A listed connector is not an authorized connector. Value reporting shows measured local proof, never inflated or fixed savings numbers, and we make no compliance or partnership claims.

Free tier Local install, local memory, personal workflows, setup feedback.
Premium Cloud sync, smart connectors, cross-device handoff, team features, and advanced automation.

Enterprise checklist

What organizations can ask for before a rollout.

For enterprise buyers, be ready to discuss tenant isolation, retention, export and deletion, support contacts, incident response, audit logs, DPA path, deployment boundaries, and the private security review packet. HeapFile does not claim compliance certifications that have not been independently completed.

  1. Data boundary. Identify what stays local and what syncs to cloud.
  2. Access boundary. Confirm account roles, connector scopes, and admin controls.
  3. Operational boundary. Confirm support owner, incident path, and rollback plan.
  4. Legal boundary. Prepare privacy, terms, DPA/security review, and retention answers without claiming formal compliance certification before review.
Privacy

Privacy notice

Read the privacy notice for local-first defaults, account data, support handling, and optional cloud features.

Data controls

Retention, export, delete

Read the data-control answers before putting organization data into cloud-backed features.