server

gotify/server

A simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui)

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 11, 2026
today
Ship score
82/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 16,004 → 16,036 (Sep 29 – Oct 6, 2026)
History starts 2026-09-29, the first weekly sample after this repo joined the directory.

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
16.1K
Forks
892
Open issues
87
Watchers
121
Primary language
Go
License
Other
Created
Jan 15, 2018
Owner
gotify · Organization

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

Topics

#api#cloud#free-software#golang#gotify#hosting#javascript#notifications#privacy#react#self-hosted#self-hosting#selfhosted

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 34% (self-hostable 88%, hosted offering 33%). 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. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Joined the directory 2026-09-22, added by hand. 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-10-11This is the badge for gotify/server, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/gotify/server.svg)](https://ossean.com/gotify/server)

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.