Coming soon. Not open to the public yet.
Your systems talk. Your team hears it, on their phones.
PingLoom turns events from your servers, scripts, AI agents and the tools you already use into a push on your phone, or your whole team's, and one shared inbox. One person taps "I've got this", and everyone knows it is handled.
Why PingLoom
Plenty of tools can send a notification. These are the things they usually cannot do.
No integration skill needed
Tell your AI coding agent one sentence. It wires PingLoom in and sends a test.
Answer from the alert
Add 2 to 5 buttons you write, like Deploy now, Wait or Roll back. Your code gets the answer.
One person owns it
"I've got this" tells everyone it is handled. No more five people fixing the same thing.
It notices silence
Heartbeats tell you when a job stops running, not only when it fails.
You control the noise
Per source: ignore it, alert, save it for later or ask, and only after it happens a few times.
Safe approvals
Ask for more than one vote, confirm twice, or require a phone unlock on risky choices.
Never loses an alert
Every event is saved before we answer, and sending is retried if it fails.
Status you can trust
You see exactly where each alert got to. We never claim a phone showed it when we cannot know.
Private lock screen
A locked phone shows only the channel and the priority. Details open after you sign in.
Many apps, one inbox
Every app gets its own project and channel, and everything lands in one place.
Plugs into anything
One web request from any language, 20+ ready-made templates, and n8n, Zapier and Make.
For one builder or a whole team
One person with ten side projects, a team with one product, or an agency with fifty clients. Everything pings one inbox.
Solo developers
All your side projects, scripts and servers in one place, on your own phone.
Many small apps
Each app gets its own project and channel. One inbox shows them all.
Many AI agents and servers
Every agent and every server can ping you, and ask before it does something risky.
Teams and agencies
Shared alerts, one person takes each one, and clients stay in their own workspaces.
You do not need to know how to integrate it
In the age of AI coding, tell your coding agent what you want in one sentence. It reads our docs, wires PingLoom into each app and sends a test. Ten apps take ten sentences.
Anything sends in. Your whole team hears it.
PingLoom sits between the things you run and the people who look after them.
What can send to PingLoom
- Your servers and scriptsOne web request from any language, any machine
- Uptime and server checksUptime Kuma, Prometheus, Grafana and your own checks
- Code and deploysGitHub, GitLab, Sentry, Vercel and more
- Jobs that check inA heartbeat URL for backups and cron
- AI agentsAsk a person before acting
- Home and hardwareHome Assistant, OctoPrint, any sensor
- n8n, Zapier and MakeThousands more apps, no code
PingLoom
- Stores every event safely
- Applies your rules
- Watches your heartbeats
- Waits for decisions
Where it reaches people
- Android phonesA push for everyone on the channel
- Shared team inboxOne history the whole team sees
- Slack, Discord, TelegramA copy in the chat you already use
- Back to your codeThe decision, by webhook or API
- iPhone (after launch)After Android
The life of one alert
Here is what happens in the seconds after a disk check on your server sees trouble.
- Step 1
Something happens
Your disk check sees web-1 at 92% and sends one web request.
- Step 2
It is stored first
We save it before we answer, so a crash cannot lose it.
- Step 3
Your rules sort it
Alert now, save for later, ignore, or ask for a decision.
- Step 4
Your team hears it
Phones buzz, the inbox updates, the chat gets a copy.
- Step 5
One person takes it
Priya taps "I've got this". Everyone else can relax.
- Step 6
Your code gets the answer
If it was a question, like "clear old logs?", your script reads the answer and carries on.
What you get at launch
All of this is built and in testing now.
Alerts on every phone
Send one web request from anything you run. Everyone on that channel gets a push on Android.
A shared team inbox
Every event lands in one history the whole team sees. Read and unread stay personal to you.
"I've got this" for the team
One person acknowledges, and everyone sees who took it. No more five people fixing the same thing.
Heartbeats for jobs that go quiet
Your backup or cron job pings a URL when it runs. If the ping does not come, you get an alert, then an all-clear when it is back.
Decisions from the alert
"Deploy to production?" Pick an answer on your phone. Your script reads the answer and carries on.
Safe decisions
Choose who may decide, ask for more than one vote, confirm twice, add a note or ask for the phone unlock on risky choices.
Your rules
Per source, choose to ignore, alert, ask for a decision or save for later, and only after it happens a number of times.
Save for later
Not urgent? Keep it in a list and deal with it when you sit down.
Ready-made webhook templates
Point GitHub, Sentry, Grafana, Uptime Kuma, Home Assistant and more at PingLoom. We turn their webhooks into clear alerts.
n8n, Zapier and Make
Send alerts and ask for decisions from your automations, without writing code. Thousands of apps, one step.
Slack, Discord and Telegram too
Copy important events to the chat your team already uses.
Private on the lock screen
The push shows only the channel and the priority. The details open in the app after you sign in.
Honest status
See where each event got to: accepted, sent to Google's push service, or failed. We never claim a phone showed it unless the app says so.
Almost infinite use cases
Pick a thing, what happens to it, and who should know. Mix them any way you like: there is no fixed list, and no limit.
Something you run 12
- A server
- A website
- A backup job
- A cron job
- A deploy
- A database
- An AI agent
- A 3D printer
- A sensor
- An online store
- A contact form
- A sign-in
Something happens 10
- fails
- goes down
- goes quiet
- gets slow
- crosses a limit
- needs approval
- finishes
- comes back up
- looks suspicious
- waits too long
Someone should know 6
- me
- the on-call person
- the whole team
- the founder
- support
- the client
Servers and uptime
- web-1 has been down for 2 minutes
- CPU on db-2 above 90% for 10 minutes
- The SSL certificate expires in 7 days
- 5,000 jobs are waiting in the queue
Developers and ops
- Deploy to production is waiting for approval
- The nightly backup did not check in
- Errors jumped in Sentry
- The build failed on main
AI agents
- The agent wants to send 200 emails. Allow?
- A tool call failed three times
- The research run finished
- The agent went over its budget
Shops and leads
- A big order came in on your store
- Stock is down to the last 5 items
- A new lead filled in your form
- A demo was booked for tomorrow
Home and makers
- Print finished on printer 2
- The greenhouse dropped below 10 °C
- The garage door opened at 2 am
- The power went out at the office
Teams
- Customer call in 10 minutes. Who is taking it?
- The weekly report is ready
- Someone signed in from a new country
- A new teammate accepted the invite
Your idea
Anything that can call a URL: a script, a webhook, a sensor, a spreadsheet, an agent.
Tell your AI agent. It connects PingLoom for you.
We all build with AI now. You do not have to learn another API: describe the alert in one sentence to Claude Code, Cursor, Codex or any coding agent. It reads PingLoom's docs for agents, adds the code to your project and sends a test, so your phone buzzes in a minute.
Add PingLoom alerts to this project. Ping the on-call channel when the nightly backup fails, warn me when the disk is over 90%, and ask me before the deploy script pushes to production. Docs: pingloom.dev/llms.txt
Your agent does
- Reads the PingLoom docs written for agents
- Adds three alerts and one decision to your code
- Keeps the API key in an environment variable on your server
- Sends a test alert so you can see it on your phone
Thousands of use cases, one sentence each. Docs for AI agents
Connects to the tools you already use
Paste a PingLoom URL into a tool's webhook settings, or add PingLoom as a step in n8n, Zapier or Make. No code on your side. For anything else, send one web request.
- 20+
- ready-made webhook templates
- 3
- chat apps: Slack, Discord, Telegram
- 1
- web request connects anything else
- 1000s
- more apps through n8n, Zapier and Make
Code and deploys
- GitHub
- GitLab
- Sentry
- Vercel
- Linear
- Jira
Monitoring and uptime
- Grafana
- Prometheus Alertmanager
- Uptime Kuma
No-code automation
- n8n
- Zapier
- Make
Home, hardware and forms
- Home Assistant
- OctoPrint
- WooCommerce
- Typeform
- Tally
- Cal.com
Logos and names are trademarks of their owners, shown only to say PingLoom works with these tools. PingLoom is not affiliated with them.
Coming after launch
Built already, released a little later.
iPhone app
Android comes first. iOS follows.
Python, Node, CLI and GitHub Action
Packages are written and tested. They are published after launch. Until then, one curl does everything.
Questions people ask before joining
Short answers about what PingLoom is, what it costs, and what happens after you join the waitlist.
Still wondering about something? The docs explain the API, webhooks and heartbeats in detail. Read the docs
The waitlist
When does PingLoom launch?
We have not set a date. Everything on this page is built and being tested now. People on the waitlist get an email before anyone else, in the order of the list.
What do I get for joining early?
An invite before the public launch, and a 30-day free trial of the Team plan instead of the usual 14 days. You do not need a card for the trial.
How do I move up the list?
Your welcome email has your own share link. Every friend who joins with it and verifies their email moves you up five places.
What do you do with my email?
We use it only for your welcome email, updates as we build, and your invite. Every email has an unsubscribe link, and we never sell the list.
The product
What is PingLoom?
PingLoom is a notification API and a shared team inbox. Your scripts, servers and tools send it an event with one web request, and it sends a push to your team's Android phones, keeps the event in an inbox everyone can see, and lets one person take it with a tap.
How do I send a push notification from my server or script?
Send one HTTPS POST request to the PingLoom API with your project key, a title and an optional body. It works from any language, a cron job, a shell script or a CI pipeline. No SDK is needed.
Can PingLoom alert me when a cron job or backup stops running?
Yes. Create a heartbeat and have your job call its URL each time it runs. If the call does not arrive on time, PingLoom alerts your team, and sends an all-clear when the job is back.
Does it work with GitHub, Sentry, Grafana and other tools?
Yes. There are more than 20 ready-made webhook templates, including GitHub, GitLab, Sentry, Grafana, Prometheus, Uptime Kuma and Home Assistant, plus apps for n8n, Zapier and Make. Anything else can send one web request.
Can my AI coding agent set it up for me?
Yes. PingLoom publishes docs written for AI agents. Describe the alert you want to Claude Code, Cursor, Codex or another coding agent, point it at pingloom.dev/llms.txt, and it adds the code and sends a test alert.
Can my script or AI agent ask a person to approve something?
Yes. An alert can carry a decision with two to five answers, such as Approve or Reject. Someone picks an answer on their phone, and your code reads it back from the API or receives it by a signed webhook.
Is there an iPhone app?
Android comes first. The iPhone app follows after launch.
Price and trust
What will it cost?
There will be a free plan, and paid plans in Indian rupees and US dollars for teams that need more. Final prices are announced at launch.
Is PingLoom an on-call paging service?
No. PingLoom does not promise delivery times, and Android may delay a push. It shows you exactly where each alert got to, and the inbox always has the event.
Is my data safe?
API keys are stored only as a hash and stay on your server. The lock screen shows only the channel and the priority, and the details open in the app after you sign in.