Free for individuals, fully hosted
Monitoring for the things that fail quietly.
For developers and SREs tired of finding out a cron job, backup or CI pipeline died days ago. LastPing watches for expected signals and pages you when they stop arriving.
Free for individuals, no lock-in, no infra to run.
What LastPing is
Most monitoring tools watch for things that happen. LastPing watches for things that stop happening: the heartbeat that never checked in, the backup that didn't phone home, the CI job that ran in silence and failed.
- Absence-based detection. Each monitor has a durable deadline; a ping resets it, and an overdue deadline opens an incident. Either the signal arrived or it didn't.
- Three monitor types. Heartbeat (a dead man's switch), CI/CD signals from GitHub Actions, GitLab CI and Jenkins, and active HTTP probes.
- Honest alerting. Incidents, not raw notifications: no duplicate pages for the same problem. Nine channels attach through a routing matrix, with custom message templates.
Who uses it
Anyone who has been surprised by a silent failure.
Teams shipping software
Know when a pipeline silently fails, a deploy goes quiet, or a scheduled task misses its window.
Infrastructure teams
An incident when the job that should have run at 03:00 didn't show up by 03:05.
Side projects to production
The same silent-failure detection large ops teams use, with no monitor cap or feature gate.
The ethos
Resilience tooling should be trustworthy, accessible, and free from hidden incentives.
Free for individuals
No credit card, no feature gate, no "free up to N monitors."
Follow the project on GitHub
File issues and follow what's coming next at github.com/lastping-dev/lastping-app.
No bait-and-switch
A paid team tier may come later. If it does, individual accounts get advance notice of anything that affects them.
Built by one engineer
LastPing is built and operated by Tedo Patsatsia, a systems engineer working in DevOps: someone who has been on the receiving end of a job that stopped running three weeks before anyone noticed.
- The open-source CLI and MCP server: github.com/lastping-dev/lastping-app.
- The Terraform provider: lastping-dev/terraform-provider-lastping.
- Reach the project at hello@lastping.dev.
It is also listed on AlternativeTo, beside the tools people most often weigh it against.
Your data, and how long we keep it
LastPing stores only what it needs to monitor your jobs: your monitors' configuration, the check-in timestamps they receive, the incidents and event history those produce, your alert destinations, and your account details.
Retention
Monitor configuration is kept while your account is active. Check-ins expire after 90 days, closed incidents after a year (the full table is in the privacy policy).
Deletion
Delete a monitor and its check-in and incident history is removed with it. To close your account and delete all of its data, email us and we'll take care of it.
Delivery safety
Email destinations use confirmed opt-in, and outbound alert delivery is SSRF-guarded. Infrastructure runs in the EU (Frankfurt).
Questions about your data? hello@lastping.dev.
Start monitoring in minutes
Free for individuals. One URL to ping, or let your AI assistant set it up.