A serious amount of machine, for one team
A memory that outlasts any single AI, accounts it can act on, skills on a clock, a server of the team's own.
gbrain.io
A memory that outlasts any single AI, accounts it can act on, skills that run on a clock, and a server of the team's own. Here is what using it looks like.
What it knows about the team and the work, in files the team owns.
Connect any AI that supports MCP, the standard connection, to the same notes. One memory for all.
See how it works
Everything the workspace knows is a file you can open, edit, and copy.
See how it works
Read can search and recall. Full can also remember, link and forget. Set it for each AI.
See how it works
Ask about "the pricing call" and it finds the note titled "Q2 renewal terms."
See how it works
Lately shows what it learned this week. People shows everything it knows about one person.
See how it works
The accounts it reaches, and what each AI may do with them.
One address, pasted once into ChatGPT, Claude, Claude Code or Cursor. Each gets the same accounts and rules.
See how it works
Gmail, Calendar and web search from a terminal. Claude Code and Codex run the same commands.
See how it works
Connected accounts are held by gbrain. An AI gets the result of a call, never the key.
See how it works
Gmail has four levels, Calendar two, web search is on or off. Set per application; every AI follows.
See how it works
Every tool on every account has a daily line. Cross it and that tool trips; nothing else does.
See how it works
One row per call. Who asked, which AI, which account, what it did, whether it was allowed.
See how it works
Turn an AI off and its next call is refused. Every AI's access also has an end date.
See how it works
The jobs it knows how to run, on demand or on a schedule.
Every job on the shelf, with what each one does and needs. Read one, turn it on.
See how it works
One switch per skill on the workspace. On, it runs for everyone; off, it stops.
See how it works
Give a skill a time. It runs, writes what it found to the memory, and tells the thread.
See how it works
The room a team works in, and the server it runs on.
Everyone in the thread, everyone's messages, one assistant answering all of them.
See how it works
The steps appear as it takes them. Add a note mid-answer and it takes the note.
See how it works
A thread per piece of work, named. See which ones moved since you last looked.
See how it works
Hand it a job at night. Open the thread in the morning and the work is there.
See how it works
The memory and skills run on a machine of the workspace's own, wrapped and kept current by gbrain.io.
See how it works
The whole team gets in with the accounts they already have. There is nothing to reset.
See how it works
Members use every workspace in the organization. Admins invite, remove, and pay.
See how it works
Pick the model a workspace thinks with, and change it later. Everything else stays.
See how it works
