Developer
FreeStart using shared context with your AI.
- 1,000 monthly credits
- 1,000 stored facts
- Permissions by collection
- MCP, SDKs, and REST API
Choose the monthly credits and memory capacity that fit your work. Add credit packs when you need more usage.
Start using shared context with your AI.
More capacity for ongoing projects.
For people who retain more context and use memory more frequently.
Prices in USD. Monthly subscriptions.
Individual subscriptions. Invitations grant collection access; they do not transfer a plan or create a shared allowance. Usage credits and fact capacity are separate limits.
For teams that need to manage people, collections, and usage together.
Discuss volume, rollout, and corporate security and governance requirements.
Teams and Enterprise are planned offerings. Express your interest to discuss scope and availability; the described features are not part of an active offer yet.
| Features and capacity | Developer | Starter | Pro |
|---|---|---|---|
| Subscription | Individual | Individual | Individual |
| Monthly credits | 1,000 | 10,000 | 75,000 |
| Stored facts | 1,000 | 10,000 | 100,000 |
| Owned collections* | 2 | 10 | 50 |
| Active AI connections per user* | 1 | 2 | 2 |
| Read and write permissions per collection | Included | Included | Included |
| External invitations | Available | Available | Available |
| MCP, SDKs, and REST API | Available | Available | Available |
| Additional credit purchases | Yes, without a subscription | Yes | Yes |
| Central team management and billing | Not included | Not included | Not included |
* Commercial configuration under validation. The proposal includes up to 3 people with write access on the free plan; counting rules and paid-plan invitation limits are not final. An invitation grants collection access without transferring the owner’s subscription or multiplying credits.
Packs are available on every plan, including free Developer accounts. Buy more credits without changing your subscription.
View credit packs in the dashboardOne-time credit purchases do not increase facts, collections, participants, or connections. Expiry, rollover, and consumption order are still being defined.
Writing 1 fact uses 1 credit; reading 4 facts uses 1 credit. Count the facts returned, not just the queries. Your AI subscription is separate.
A fact is a stored relationship, such as a project delivery scheduled for Friday. A message or document can contain several facts.
Group information by project and define the participants and read or write permissions for each collection.
No. Credits are used by operations; the fact limit is your memory capacity. Reading stored information and adding information serve different purposes, and a single call can work with several facts.
Packs add credits. The number of facts your plan can store remains unchanged.
Open your Gomind dashboard to check your organization’s credit balance, manage your subscription, and view available credit packs.
Gomind is separate from your AI app. Your app determines which connection features your account can use. Check its connection guide before getting started.
It is a stored relationship: a subject, a relationship, and another entity or value. For example: Project Aurora → delivery → Friday. One fact does not equal a message or document.
A collection groups facts inside your organization. Use one for each project, product, or client, and define its participants and permissions. Connected AIs with access to the same collection can consult that shared memory.
Yes. With write permission, you can remove a fact or the facts associated with an entity. You can also delete a collection when you have permission to do so. This removes information from Gomind; it does not erase copies already returned to another tool.