Case study · 01
DripYap
A messenger the organisation actually owns.
0personal numbers shared
100%on your own server
- Problem
- Team and client conversations live on personal phone numbers, inside someone else's cloud.
- System
- A Kotlin messenger on your own server. Members join by invite code; bot accounts wired to n8n post announcements, reminders and answers.
- Outcome
- Branded rooms the organisation owns. Nobody hands over a personal number, and nobody is the product.
Who it is for
Enterprises that will not put internal talk in someone else's cloud, businesses that want one branded channel to their customers, and individuals who would rather not be the product.
How it works
Members join a room with an invite code, so a student, a client or a new hire never has to hand over a phone number. Stickers, GIFs and voice notes work the way people expect. Bot accounts are wired to n8n, so announcements, reminders and routine answers post themselves.
Where it runs
On a server the organisation controls. There is no vendor cloud in the middle, and an MCP server lets AI agents read and post in rooms under the same permissions as a person.
Kotlin · Jetpack ComposeSelf-hostedInvite-code onboardingn8n botsMCP server for agents