Build, collaborate, and never lose context again.
Tamarind keeps the reasoning behind your team's work attached to the work itself. Conversations turn into knowledge you can return to, instead of messages you have to dig through.
Tamarind is in active development. Access for testing is available on request.
The problem
Organizations forget faster than people do
Every day, teams produce a remarkable amount of knowledge through written conversation. Ideas are discussed, problems are solved, decisions are made and lessons are learned.
Almost none of it survives. It dilutes across thousands of messages, and within weeks nobody can find the thread that explains why things ended up the way they are.
So the same questions are asked again. The same investigations are repeated. The same mistakes are rediscovered. Not because people forget, but because organizations do.
- Chat apps
- Optimized for communication. Built to move quickly, and to forget just as quickly.
- Documentation apps
- Optimized for storage. Static content that depends 100% on your will to keep it updated.
- Tamarind
- Optimized for context. Knowledge is preserved as part of the conversation itself.
Highlights
What Tamarind does today
Built for focused team work
A split view interface lets you create on one side and coordinate on the other, with familiar design patterns, light and dark themes and a command palette.
Find anything, by keyword or meaning
A hybrid search system that helps you find what you are looking for, even when you no longer remember exactly what it was.
Memory that builds itself
A semantic minimap helps you remember what each conversation was about, and smart suggestions surface what you need before you think to ask for it, so nobody reinvents the wheel.
Philosophy
Documentation should emerge from conversation
Conversation is the richest source of knowledge a team has. Documentation should not have to compete with it for attention, and people should not be asked to reconstruct their reasoning days after the fact.
Tamarind is not a messaging application, a documentation platform or a knowledge base. It borrows from all three, and adds the one thing none of them keep: the context in which a decision made sense.
The current product is a starting point. The direction being worked toward is a single place where conversations, decisions and historical context sit together, and where knowledge becomes easier to discover and reuse the longer a team works.
Knowledge should compound. Not disappear.
Interested in trying it?
Tamarind is in testing, and I am speaking directly with the teams who want to use it. Get in touch and I will walk you through where the product stands today and which features are coming next.
The journey
Follow the development
I write about the decisions behind Tamarind as they are made: what is being built, which milestones have been reached and what turned out to be harder than expected. Notes and follow-ups are published on the blog.