Your team's
context.
In your AI.
Everyone keeps using their own AI. Save decisions, learnings and references in Gomind so your team can continue with shared context and access defined for each person.
A perspective cube made of thousands of moving dots and strands. Hovering creates gradient light and a gentle distortion between the dots.
CONTEXT THAT MOVES WORK FORWARD
Connect
Keep using your AI. Connect it to Gomind.
Share
Organize context into collections and choose who can access it.
Continue
The next conversation starts with what has already been shared.
Your team has already learned a lot.
The next conversation can start there.
See more use cases 
CamilaClient serviceusing
GeminiHow can I help today?
Memory
What one person learns can help the next conversation. Gather decisions, discoveries and knowledge in collections your AIs can consult.
- Context collections
- Shared knowledge
- Everyone with their own AI
Permissions
Share context with the people who need it. You choose who joins each collection and who can read or add knowledge.
- Access per collection
- Readers and writers
- Authorized people
Continuity
The next conversation can pick up where work left off. Your AI consults authorized context to help you move forward.
- Decisions preserved
- Context across people
- Different AIs connected
Camila records the agreements. Bruno updates the scope. Pedro finds it all in the same memory.
Available to PedroCoordination · Project AuroraYour AIs.
One shared memory.
Connect the tools people already use. Share context through collections, with the access that makes sense for your team.
Explore connectionsConnect Gomind
to your own software.
Bring project context into your applications and agents. Connect Gomind's shared memory through SDKs, the API or MCP.
Read the developer quickstartA place for every context.
Organize memory by organization and collection.
Control over what stays.
Remember, recall, or delete facts with the corresponding permissions.
Tools for your agents.
Use MCP tools to consult and record information as work progresses.
npm install @gomind/sdkimport { GomindClient } from '@gomind/sdk';
const memory = new GomindClient(
'https://api.gominddb.com',
process.env.GOMIND_API_KEY!
);
await memory.remember(
'project:aurora', 'delivery_day', 'friday'
);
const { facts } = await memory.recall('project:aurora');
console.log(facts);
go get github.com/ingate/[email protected]package main
import (
"context"
"fmt"
"log"
"os"
gomind "github.com/ingate/gomind-go-sdk"
)
func main() {
memory, err := gomind.NewClient(os.Getenv("GOMIND_API_KEY"))
if err != nil { log.Fatal(err) }
ctx := context.Background()
_, err = memory.Remember(ctx, "project:aurora", "delivery_day", "friday", "")
if err != nil { log.Fatal(err) }
result, err := memory.Recall(ctx, "project:aurora", 20)
if err != nil { log.Fatal(err) }
fmt.Println(result.Facts)
}
composer require ingate/gomind-php-sdk<?php
require 'vendor/autoload.php';
use Ingate\Gomind\Client;
$memory = new Client(getenv('GOMIND_API_KEY'));
$memory->remember(
'project:aurora', 'delivery_day', 'friday'
);
$result = $memory->recall('project:aurora', 20);
foreach ($result->getFacts() as $fact) {
echo $fact->getObjectOrValue();
}
export GOMIND_API_KEY="your-api-key"# Store a fact
curl https://api.gominddb.com/v1/remember \
-H "Authorization: Bearer $GOMIND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"subject": "project:aurora",
"predicate": "delivery_day",
"object": "friday"
}'
# Recall it in another session
curl https://api.gominddb.com/v1/recall \
-H "Authorization: Bearer $GOMIND_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "project:aurora", "limit": 20}'
Your team already has the context. Move every conversation forward.
1
Shared memory
2
Access levels: read and write
3
Steps: account, collection, connection
∞
Ways to keep going
Share knowledge.
Keep control.
Protected data
Encryption, HTTPS/TLS and hashed credentials. Responses exclude authentication secrets and payment details.
Defined access
Boundaries per organization and collection. Read and write access for your team and authorized partners.
Memory control
Delete facts and collections with the appropriate permission. You decide what remains available.
Traceability
Context, source and date in records. Action traces and identifiers help track operations and investigate failures.
Does everyone need to use the same AI?
No. Each person can connect one or more compatible AIs to Gomind. To share the same project memory, those connections need access to the same organization and collection.
Does Gomind send automatic summaries to the team?
Summaries are produced by the AI that consults Gomind. Ask for one in a conversation, or configure a routine if your bot supports it. Gomind provides shared memory; retrieval, summaries, and scheduling depend on the connected tool.
Does Gomind save every conversation?
Connecting provides tools for recording and consulting information. Ask your AI to use Gomind and check what was saved. Chat history is not automatically imported.
Do I need to code?
The connection guides explain setup in compatible AI apps. SDKs and the API are available for custom integrations.
What can I share?
Meeting decisions, client agreements, project learnings and useful references. Organize this knowledge into collections and choose what to share with each group so others can continue the work.
How do I get started?
Create your account, organize a collection and connect a compatible AI. Then gather the context you want to share and set access for the people who will continue the work with you.
What is a fact?
A fact is one unit of memory: a relationship between a subject and another entity or value. For example: project → uses → PostgreSQL. It can represent a decision, a preference, or a piece of knowledge about the project.
Does one conversation equal one fact?
No. A message or document can contain several facts. Gomind stores the relationships you or your agents send, so they can be connected and consulted later. It does not automatically import every conversation.
What is the difference between facts and credits?
Facts measure stored memory; credits are consumed by operations. A single operation can work with several facts. Additional credit packs increase usage credits, without changing the plan’s fact limit.
What is a collection?
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.
Can I delete stored information?
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.
Who can access a collection?
The people invited to participate, according to their permissions. Define who can read information and who can also write.
Can I invite people outside my organization?
Yes. External professionals can participate in the collections they are invited to, with permissions matching their role.