Self hosted push notification server versus a hosted endpoint

Where the queue lives, who patches TLS and which one survives an audit are the three differences that matter.

·3 min read

Choosing between a self hosted push notification server and a hosted endpoint is not a feature comparison. Both send a short message to a phone from a script, and both accept an HTTP request. The decision is about where the queue lives, who patches the server, and what happens to a message that names an internal hostname.

The two architectures

Layer Gotify AyePing
Sender Your script POSTs to your server Your script POSTs to ayeping.com
Transport Your TLS certificate and public route Managed HTTPS
Queue Your database AyePing's service
Receiver Gotify client app AyePing iPhone and Android app
Failure mode Your server or tunnel is down The service is down, or your allowance is spent

Everything else follows from that table. A self-hosted design keeps data inside your perimeter and puts every failure on your own pager. A hosted design inverts both.

What Gotify's documentation promises

The project is refreshingly specific. A client is a device that receives messages and manages applications and clients. An application can only send. A message carries content, title, creation date, application id and priority.

That last attribute is the one teams miss when they move. Priority is how you mark an alert as genuinely urgent rather than routine, and a hosted service that models severity only through color has to be checked against the docs before you migrate.

What AyePing's documentation promises

The request shape is small. A POST to https://ayeping.com/@username, or /ping/@username for tooling that rejects a leading @, with an Authorization: Bearer header. The body takes an optional JSON object with a required title of 1 to 100 single-line characters, a Markdown message up to 2,000 characters, and a label with text up to 20 characters and a color from a fixed list.

Responses are honest about what happened: 202 with an id, or a JSON error code for an invalid body, a bad token, an exhausted quota, a paused token, a rate limit or an oversized body. There is no delivery receipt, which the docs do not pretend otherwise.

Retries are handled by an Idempotency-Key header of up to 255 characters. A repeat with the same key and token returns the original id and is neither delivered nor charged twice.

Operational differences that bite later

Rate limits. AyePing caps each token at 1 to 3,600 requests an hour, 60 by default, and returns RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset on accepted pings. A one-minute cron sits exactly on the default.

Retention. Free keeps pings 90 days, and paid plans keep them a year. Self-hosted retention is whatever your database allows.

Cost. As of November 2026, Free includes 5 pings and 3 tokens with no card, Hobby is $8 a month or $49 a year for 120,000 pings, and Pro is $20 a month or $120 a year for 1,200,000. Unused pings do not carry over.

Which one survives an audit

If a rule says alert content cannot cross a network boundary, self-hosting is not a preference, it is the requirement, and Gotify satisfies it with a small surface. If the requirement is merely "someone must be told within a minute", a hosted endpoint is the cheaper way to meet it, because you are not also maintaining a server, a certificate and a backup.

A migration path that is not all-or-nothing

Point one script at the hosted endpoint. Keep the rest on your server. After a month, count which one produced the alerts you actually acted on, and which one woke you up with a maintenance failure. That comparison decides the rest better than any feature table.

FAQ

Does AyePing offer priority levels like Gotify?

Its documented body has a title, a message and a colored label. If delivery priority is a hard requirement, confirm against the current docs before changing anything.

Can a hosted endpoint reach a machine with no public IP?

Yes. The sender only needs outbound HTTPS, so a laptop behind NAT can send a ping.

What happens when the allowance runs out?

The API answers 402 quota_exhausted, and the app sends at most one push a day telling you so.