Contents
#Why Poche exists
Hey there,
I built Poche because I was tired of losing great links shared in Slack. You know the feeling. Someone drops an amazing article in a channel, you think “I'll read this later,” and it disappears into the void of endless messages.
Traditional bookmarking tools felt disconnected from where teams actually collaborate. We needed something that lived in our workflow, understood context, and could surface knowledge when we needed it most.
Poche captures the institutional knowledge flowing through your Slack channels and turns it into a searchable, organized library that grows with your team.
Hope it serves your team as well as it's served mine.
Xiao Du
#Questions
- Who builds Poche?
- Poche is made by Dine, a small studio. It started as an internal tool for our own Slack and grew from there.
- Can other teams see our links?
- No. Only your team's members can see your team's links. Explore shows recommendations from teams that opted in to sharing publicly. Details in the privacy policy.
- Which AI model does it use?
- Google's Gemini models, via OpenRouter, with prompts your team can customize. We've opted out of training on your data. See AI usage.
- What does it cost?
- Nothing during public beta. See pricing.
#Stack
React and Tailwind on the front end, Convex for the database, scheduling and real-time sync, deployed on Vercel.
#Contact us
Email support@poche.app. You can also find us on X at @dinehq, or say hello at dinehq.com.