Launching today

TeamBrain
One brain for your whole team
8 followers
One brain for your whole team
8 followers
TeamBrain is one shared brain for your whole team. Every decision, answer, and bit of context lives in one place — instantly searchable. Ask it anything in plain language and get an answer in seconds, sourced from your team's own knowledge. Capture context automatically, onboard new hires in days, not weeks, and stop losing what your team knows every time someone logs off. Teams should get smarter over time, not start from zero every week. Give your team a memory that never forgets.



A "decision audit trail" view would be huge for us - being able to see not just what was decided but who weighed in, what alternatives were considered, and why a particular path was chosen. That kind of context gets lost even in great wikis. Would love that added to the knowledge graph.
@kbrambmj This is the comment I was hoping someone would leave.
The reason it resonates: TeamBrain already generates this data and then throws it away. Every memory goes in as a pull request — proposer, reviewers, the back-and-forth, the approval. That's a decision audit trail sitting in git history that we currently discard after merge.
So the feature is less "build a new subsystem" and more "stop discarding what the governed loop already produces." A decision memory type with derived provenance, alternatives-considered as a first-class field, and supersession links when something gets revisited. The retrieval piece I'm most interested in: indexing the rejected alternatives, so when an agent proposes an approach your team already ruled out, it gets told — and told why. Wikis structurally can't do that.
One honest caveat: TeamBrain is markdown + git with typed links, not a graph database. You'd get lineage and provenance, not Cypher queries. If that's still useful to you, I'd love to talk — this is exactly the kind of thing I want a design partner shaping before I write the schema.
Finally tried TeamBrain with my small team and the onboarding piece actually held up. Asked it a question about a client from three months back and it pulled the answer with the source. That part felt genuinely useful instead of gimmicky.
honestly this looks super useful, especially the auto-capture part. one thing i'd love to see is a way to flag or tag stuff that's outdated so it doesn't keep getting surfaced in answers. basically a freshness indicator on each source would help a lot, you know?