DocsHelp & Billing

Billing and Plans

Local-first usage stays free. Paid plans unlock hosted sync, dashboard controls, and advanced BYODB features.

billingpricingplansstripe

Billing applies to the optional cloud layer, not the default local-first path.

If you only want the local runtime, you should still be able to install Coppermind, connect a client, and use memory without paying first.

Current plan shape

PlanPriceBest for
Free$0Local-first usage
Pro$19/monthHosted sync and richer managed controls
Team$49/user/monthShared controls and advanced cloud usage
EnterpriseCustomSupported rollouts, governance, and advanced BYODB needs

What stays free

The free local-first path includes:

  • local runtime
  • local memory
  • local diagnostics
  • supported local client integrations

What paid plans unlock

Paid plans are for the cloud layer:

  • hosted sync
  • dashboard controls
  • API-key-based cloud access
  • BYODB attach
  • org and governance features

Feature summary

CapabilityFreeProTeamEnterprise
Local runtimeYesYesYesYes
No-login local useYesYesYesYes
Hosted syncNoYesYesYes
Dashboard controlsNoYesYesYes
Workspaces and org adminNoNoYesYes
BYODB attachNoNoYesYes
Supported BYODB rolloutNoNoNoYes

Billing flow

Coppermind uses Stripe for billing flows such as:

  • checkout
  • subscription changes
  • payment method updates

The dashboard reflects the resulting plan and entitlement state.

Upgrading from local to cloud

If you start local-first and later decide to adopt cloud features, Coppermind should give you a bridge rather than forcing a brand-new workflow.

One example is importing local history after you configure cloud auth:

coppermind dashboard import-local

That is an upgrade path, not a requirement for normal use.

The important product rule

Billing should not turn local-first usage into a paywall.

If a new user cannot get local Coppermind working without thinking about plans, the product story has drifted.

Where to go next