chat

tinode/chat

Instant messaging platform. Backend in Go. Clients: Swift iOS, Java Android, JS webapp, scriptable command line; chatbots

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Sep 27, 2026
5 days ago
Ship score
76/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,458 → 13,522 (Aug 18 – Sep 29, 2026)
+48 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
13.5K
Forks
2.1K
Open issues
41
Watchers
302
Primary language
Go
Created
Nov 14, 2014
Owner
tinode · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#chat#chat-application#chatapp#chatbots#chatserver#collaboration#go#golang#instant-messaging#messaging#messaging-api#messenger#telegram#video-call#video-chat#video-conferencing#webchat-server#webrtc#whatsapp#xmpp

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 63%, self-hostable 79%, hosted offering 40%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-09-27This is the badge for tinode/chat, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/tinode/chat.svg)](https://ossean.com/tinode/chat)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.