Show HN: Peeng – like Pingdom, but the other way around and simpler

For the last few weeks we’ve been building Peeng and can now share our beta with you: https://www.peeng.sh. Peeng is the easiest and quickest “heartbeat” architecture we could think of. Just pick a subdomain (e.g. x.peeng.sh), configure an interval, an endpoint, and a payload, and hit that subdomain every It’s Pingdom/Cronitor/heartbeat.sh free alternative (but the other way around and A LOT simpler, with a lot more capabilities), suitable for developers, system administrators, DevOps, and individuals with complex networking situations (think “onprem” or K8s clusters with no inbound). Instead of inbound heartbeat checks — Peeng presents outbound heartbeat checks!

Quick demo: https://youtu.be/ZX5mrnMRCwU

Why we built this:

- We needed an easy way to let Keep (https://github.com/keephq/keep) customers behind closed networks monitor their Keep instance - We needed an easy & quick way to setup monitoring for our cronjobs - We wanted to give people with complex networking situations (e.g. behind a firewall) an easy way to monitor their services/processes

The beta version lets you:

- Create 5 endpoints for free - Configure the endpoint and the payload to be sent when the subdomain is not hit - See the visits (every HTTP GET request to your subdomain) and requests (every HTTP POST sent to your configured endpoint) - Secret header (x-peeng-secret) that confirms requests are made by you

What’s next:

- A status page that displays your subdomains and their health together with embeddable status blocks that allow you to display the status of an endpoint in your web page (you can also send query params when sending the GET requests that will be included) - Rest API (for subdomain creation, beats retrieval, etc., imagine curl -X POST peeng.sh/subdomain -H API_KEY —json {”subdomain”: “hn”, “endpoint”: “https://xn--ivg, “payload”: {…}}) - Hierarchy-based subdomains that allow you to create a nested heartbeat solution (i.e. dynamically create a heartbeat subdomain under x.peeng.sh → y.x.peeng.sh, z.x.peeng.sh)

This is still very early, so we’d love to hear your feedback and opinions. We’re open to any feature request, so just reach out via Intercom :)

Show HN: Peeng – like Pingdom, but the other way around and simpler
peeng.sh

The blog also contains a bunch of useful information and guides around the topic, including various unusual configurations (arduino/esp8266) as well as information on self-hosting.

It's not really clear how this is different to heartbeat monitoring, is it because it uses a subdomain instead of a URL path?

The next things we gonna ship are going to be different though - we are going to add status page + nested subdomains so you'll have x.y.peeng.sh so all devices that reports to x.y.peeng.sh will be aggregated to y.peeng.sh status page.

Tech aside, I’m compelled to say that I don’t like the name. It is one letter off from a bodily function, and the pronunciation is even closer.

Edit: the menu button on the landing page doesn’t work for me on iOS.