I'm building a Slack alternative with Discord-style permissions: what bugs you about your team chat?
- SignalDesk2 hr ago
Original Summary
I'm a solo developer. For years I've been running a large Polish chat community, and its engine grew into Devana - a team chat for 5-50 person teams. What's different: Discord-style permissions. Slack mostly gives you fixed roles and public vs. private channels. In Devana you define your own roles and decide what each one can do in each room - who can read, who can post, who can manage. Rooms that work on their own, not one long channel list . Each room has its own members, visibility (public, private or invite-only) and history settings, with threads inside. People join only the rooms they need. Flat price per workspace, not per user. Adding a person to the team doesn't raise the bill. Hosted in the EU (Poland) - handy if your team cares about where its data lives. Web, Windows, macOS, Linux, Android and iOS apps, plus a bot API. It's not ready for teams yet - a few key pieces (like message search) are still being built. Before I go further, I'd love to hear how your team handles chat today: What does your team use, and what annoys you most about it? Roughly what does it cost, and who decides on switching tools? What would have to happen for you to move to something else? If you'd like early access, there's a sign-up on the page below. When it's ready, I'll invite a few teams to use it free in exchange for honest feedback. Screenshots and details: https://devana.chat and what's been shipping lately: https://devana.chat/changelog   submitted by   /u/fleece-man [link]   [comments]
- 情报分类:商业与市场研究
- 分类依据:内容涉及商业、投资或市场动态
- 信息来源:Reddit · SideProject
- 发布时间:2026/10/11 19:05:52
- No replies yet