Use cases
What can I use inping for?
You can use inping wherever websites and servers should run reliably and someone needs to hear in time when they do not: for the customer projects of an agency, on your own servers, in an online shop, for a SaaS service, on a NAS, for an overview of security holes and for watching content.
The sections below are typical scenarios, not customer stories. They show the task, what inping does in it, where the limits are and where to go next.
Agency with customer projects
An agency looks after many customer projects
The task
Dozens of websites on different servers, and the customer should not be the first to notice that something is wrong. A single collective overview quickly blurs who is responsible for what.
What inping does
- Separates by customer: one account, one team per customer, one project per application, each team with its own runners, agents and plan limits.
- Informs the right people: your team, up to ten external addresses and the customer contacts of the project, with double opt-in.
- Gives the customer their own status page with their logo, their colour and, if they wish, their domain.
- Assigns roles: editors and viewers see only the projects you assign to them.
Read on
Features in this scenario
Internal IT and your own servers
An IT department runs its own servers
The task
Disks fill up, a service stops, a forgotten cron job runs under the wrong account. Problems like these usually surface only when someone calls.
What inping does
- The agent reports CPU, memory, swap, disks and accounts, on Linux, Windows, macOS and FreeBSD. It only reads and opens no port.
- Four default rules apply from the first report; you add your own per server. A silent agent is an alert of its own.
- All installed packages and scheduled jobs of the host are on one page.
- Your own runner in your own network checks internal applications.
Where the limit is
inping monitors servers and HTTP(S) services, not network devices over SNMP, and not individual ports or ICMP pings.
Read on
Example data, modelled on the view in the app.
Features in this scenario
Online shop
An online shop has to stay reachable and up to date
The task
When the shop is down, revenue stops at once. If shipping texts or prices on a page change unnoticed, or a plugin has a known hole, it usually comes out late.
What inping does
- Checks shop, checkout and API as individual URLs from several locations, also behind Basic Auth or with custom headers.
- Watches individual pages such as shipping or terms and reports changes with a line diff.
- Reads Composer and npm packages from the lock files and reports known vulnerabilities.
- Collects errors from backend and browser through the Sentry SDKs, grouped into issues.
Where the limit is
The uptime check requests a URL and checks the status code. It does not click through an order.
Read on
Example data, modelled on the view in the app.
Features in this scenario
SaaS with a status page
A SaaS provider wants to inform its users itself
The task
During an incident, support requests pile up and the current state is in several places. Users want to see whether the problem is on their side or with the service.
What inping does
- Publishes a status page on your own domain: only the public URLs with names, state, 90 days of uptime and open incidents.
- Updates the page live through WebSockets; with no JavaScript it stays readable as a document.
- Triggers signed webhooks to your own systems, for example a ticket system.
- Shows logs, traces and the slowest endpoints; errors that come back count as a regression.
Read on
Example data, modelled on the view in the app.
Features in this scenario
NAS and homelab
A NAS or homelab should run reliably
The task
In a homelab much of it runs behind the router, and no one checks it from outside. Containers stop or volumes fill up with no one noticing.
What inping does
- The agent runs on a Synology NAS as a Compose project in Container Manager (not tested by us on real hardware) and reports CPU, memory, disks and every container.
- Your own runner in Docker or on a Linux machine checks internal interfaces if you allow private networks in its configuration.
- The free plan is enough to begin with: 2 agents and 1 own runner.
Where the limit is
On a Synology the agent reads neither DSM packages nor packages in other containers. Vulnerabilities there relate to mounted project directories.
Read on
Security and patch overview
Security staff need a patch overview
The task
Which servers and projects use a vulnerable version? Are runtimes still running without support? With no inventory, that question starts from scratch with each new advisory.
What inping does
- Keeps an inventory of all host packages (dpkg, RPM, apk) and all project packages from the lock files.
- Compares daily with OSV and endoflife.date and reports new findings once, with severity and fixed version, until an update resolves them.
- Links each finding to a public page under security advisories.
- Checks dependencies in a CI job with the one-line scan, which exits with an error code on findings.
Where the limit is
The comparison relies on known entries in the databases. inping does not test your application for holes and does not replace a penetration test.
Read on
Vulnerabilities in shop.example.com
Example data, modelled on the view in the app.
Features in this scenario
Content and compliance
Legal texts and content should not change unnoticed
The task
An imprint, privacy policy, terms or price details can change through an update, a plugin error or an edit without the responsible person hearing of it. The same goes for newly published pages.
What inping does
- Watches exactly the pages that count, with a CSS selector even just the relevant part, at an interval from 5 minutes to one week.
- Reports every text change with a line diff by email or webhook to the responsible person.
- Reports pages that have been added, through the sitemap.
- Keeps 20 versions per page, so the previous text can be read again.
Where the limit is
inping reports that something has changed and does not assess it legally. With 20 versions per page it is neither a long-term archive nor proof.
Read on
- Delivery time: 2 to 3 working days
+ Delivery time: 5 to 7 working days
+ New: we now also ship to Switzerland
Example data, modelled on the view in the app.
Features in this scenario
Side by side
Which feature suits which scenario?
The main features per scenario at a glance. The other features are available too, within the limits of your plan.
| Scenario | Uptime | Page changes | Vulnerabilities | Servers | Docker | Alerts | Logs and errors | Status pages | API and MCP |
|---|---|---|---|---|---|---|---|---|---|
| Agency with customer projects | No | No | No | No | No | ||||
| Internal IT and your own servers | No | No | No | No | No | ||||
| Online shop | No | No | No | No | No | ||||
| SaaS with a status page | No | No | No | No | No | ||||
| NAS and homelab | No | No | No | No | No | No | |||
| Security and patch overview | No | No | No | No | No | ||||
| Content and compliance | No | No | No | No | No | No | No |
Frequently asked questions
Questions about where inping fits
Who is inping for?
For agencies and teams who run several web applications for themselves and their customers, and for anyone who wants to keep an eye on their own servers, a NAS or individual websites. Anyone can sign up for free.
Can I monitor internal services with no public address?
Yes, with your own runner in the same network. You allow private networks in the configuration of the runner; the platform releases them only to your own runners. The runner opens only outbound HTTPS connections to inping. Loopback, link-local and cloud metadata addresses stay blocked.
Can my customers see what inping reports?
Yes, in three ways: through a public status page, as recipients of emails through the customer contacts of the project with double opt-in, or as viewers with access to the projects assigned to them.
Do I have to use all the features?
No. For uptime and change detection an account, a project and a URL are enough. The agent, your own runner, the status page and the log connection are added only if you need them.