Context Gainer

The brain of your organisation.

Not a meeting archive, not a wiki. A living graph of your people, teams, projects, decisions, tasks, documents and cloud resources — built from what already happens in your organisation, kept current every day, and queryable by anyone whose assistant needs to know.

personteamprojectmeetingtaskdocumentcloud resource
Click a node to explore its links · drag to rearrange
Always current

Every meeting, every tool, every day.

Nothing here is a snapshot. The graph updates as calls happen, documents change and connectors sync, so a question asked this morning and the same question asked tonight can have different answers.

16
people across 4 teams
22
projects, auto-discovered
287
meetings and interviews indexed
1,240+
facts and relationships
Acme rollout launch moved to the 24th · decided in Weekly sync
Stalent integration blocked on sandbox keys · Rohit, 3 days
scribe-api new Lambda deployed · migration 0011 applied
Priya joined Platform team · owns diarization
Fed by every user's meetingsvoice interviewsConfluence & DriveJira & GitHubSlackEntra / Google Workspace directorycloud resource graph
How the brain learns

From meetings, from your tools, and by asking.

Nobody writes the wiki. Context Gainer builds itself from what already happens in the organisation, and when the graph has a gap it goes and asks the person who knows.

  • Every user's meetings and dictation. Decisions, owners, deadlines and disagreements are extracted from what was actually said, per person, across the whole org.
  • Your tools. Confluence and Drive documents, Jira and GitHub work, Slack channels, the Entra or Google directory, and the live cloud resource graph resolve into the same entities.
  • Voice interviews for the gaps. Who owns what, why a decision was made, how a system really works. A few minutes at a time, and the answers become facts and edges linked to the recording.
Context Gainer · interviewing Priya · 4 of 12 gaps
QuestionWho owns the Stalent integration, and what’s blocking it right now?
Priya · 00:41Rohit owns it since July. It’s blocked on Stalent’s sandbox keys — their API changed in v3 and we’re waiting on the new credentials.
OWNSRohit → Stalent integration (since Jul 2026)
BLOCKED_BYStalent integration → sandbox credentials (v3)
FACTStalent API changed in v3
Fed by your tools

20+ connectors resolve into the same graph.

A Jira ticket, a Confluence page, a Slack thread and a calendar invite about the same project become one node with edges to each other, not four disconnected records.

Gmail
Google Calendar
Google Drive
Google Docs
Google Sheets
Google Meet
Google Contacts
Outlook
Microsoft Teams
OneDrive
SharePoint
Entra ID
Azure
Jira
Confluence
Bitbucket
Slack
GitHub
Cloud Storage
BigQuery
Any MCP server
+ your own MCP servers
ReadRuns quietly

Calendar, mail, files and tickets are read to build your brief and answer questions. Nothing is changed.

WriteDrafted, then approved

Creating a ticket or editing a page is drafted first and shown to you. It happens only when you say so.

Send as youOff until you turn it on

Slack messages and email in your name stay off by default. You switch each one on yourself, per connector, in the app.

Enterprise

Your graph, in your cloud.

That second sentence isn't a sales position bolted onto an architecture — it's a constraint on the architecture. We run the software. We do not hold the data.

  • One deployment per organisation, inside your own AWS, Azure or GCP account
  • Meetings, embeddings, connector tokens and models never leave it
  • We operate and upgrade the deployment; you keep the data
AWSAzureGCP
Talk to us about enterprise
Free forever for dictation

Native on every desk and in every pocket.

Download Kept for free. No account required, no API key, no setup — just install and start talking.

Open the web dashboard

Open source · Sign in with Auth0 only when you want meetings synced, shared or asked about.