Monitoring by medienakzent from Konstanz, Germany

Server and website monitoring. All in one place.

inping checks your websites from several locations, reads your servers through a read-only agent and tells you by email or webhook when something goes down, changes or is affected by a known vulnerability.

Start for free See pricing

On the Free plan: 1 project
Check interval on the Free plan: 60 seconds
Inbound ports: none

Example data

shop.example.com 99.94%184 ms

Now90 minutes ago

web-01.example.com Ubuntu 24.04

CPU34%

RAM11.4 of 16 GB

Disk /184 of 200 GB

Notifications

shop.example.com is not responding Email14:02

Disk / on web-01 above 90% Webhook13:47

shop.example.com is reachable again Email14:06

Vulnerabilities in shop.example.com

example/http-client 2.1.0 → 2.1.4 Critical

example-parser 1.8.2 → 1.8.5 High

PHP 8.1 → 8.4 End of Life

What does inping do? It checks websites, reads servers and reports outages, changes and vulnerabilities.
What can I use inping for? For client projects, your own applications, servers, Docker services and website content.
How do I add inping? Entering a URL is enough for uptime. For server values, add one command on the server.

Monitoring

What does inping do?

inping monitors seven things in one place: availability, servers, vulnerabilities, page changes, logs, status pages and notifications. Each project stands for one application with its own URLs, servers and rules.

Uptime

Runners request every URL over HTTP(S) at the interval you choose, every 60 seconds on the Free plan, and from several locations. You see the status code, response time, type of error such as DNS, TLS or timeout, and 90 days of history per URL.

shop.example.com 99.94%184 ms

Now90 minutes ago

Uptime monitoring in detail

Servers

The agent on the server reports CPU, memory, swap and disks, every 60 seconds by default, along with all installed packages and scheduled jobs. In Docker it adds CPU, memory, network and state for each service.

web-01.example.com Ubuntu 24.04

CPU34%

RAM11.4 of 16 GB

Disk /184 of 200 GB

What the agent measures on servers

Vulnerabilities

Runtimes, packages from lock files such as composer.lock or package-lock.json and the packages of the host are compared daily with OSV and endoflife.date. inping reports new findings once, with their severity.

Vulnerabilities in shop.example.com

example/http-client 2.1.0 → 2.1.4 Critical

example-parser 1.8.2 → 1.8.5 High

PHP 8.1 → 8.4 End of Life

How inping checks packages

Page changes

Pages are fetched at intervals from 5 minutes to one week, reduced to their text and compared. A change arrives as a line diff, and inping finds new pages through the sitemap.

/shipping changed 4 minutes ago

- Delivery time: 2 to 3 working days

+ Delivery time: 5 to 7 working days

+ New: we now also ship to Switzerland

How change detection works

Logs and errors

Applications send errors, logs and traces through the official Sentry SDKs, all it takes is the DSN of the project. If you want, the agent also reads the journal, files and Docker logs. inping has no connection with Sentry, the company.

Logs and errors last hour

SQLSTATE[HY000] Connection refused web · 12× Error

Queue job PaymentSync timed out worker · 3× Error

Slow query: 2.4 s on orders web · 14:01 Warning

Logs and errors at a glance

Status pages

Every project can publish a public page without login: with the client's logo and colour, on their own domain if you like, with 90 days of uptime and live updates. It never shows URLs, servers or people.

All systems operational status.example.com

Status pages for your projects

Notifications

Rules such as “disk above 90%” open an alert once and close it once. Every event goes by email to the team, to up to ten external addresses and contacts of the client, or as a signed webhook to your system.

Notifications

shop.example.com is not responding Email14:02

Disk / on web-01 above 90% Webhook13:47

shop.example.com is reachable again Email14:06

Alerts and notifications

Example data All tiles recreate the interface of the application, filled with invented example values. The vulnerability advisories inping checks against are public under security advisories.

How it works

How does the data get to inping?

Two small programs deliver the data. The runner checks websites from the outside, the agent reads the server from the inside. Both report to the platform, and the platform tells the right people.

Agent and runner only open outbound HTTPS connections, so no inbound port has to be opened on your server.

What the agent may do on your server

The agent only reads. It writes solely to its own directory, for its token and buffer.
The service runs as an unprivileged user, on Linux from kernel 5.13 also in a Landlock sandbox.
Nothing listens on the server, no inbound port has to be open.
Docker values come through a socket proxy that rejects every write and allows only read access under /containers.
If the platform cannot be reached, the agent buffers for 24 hours by default, configurable up to 168, and sends the data afterwards.

What can I use inping for?

For anything that has to keep running online and where you want to know before your customers do. Six typical cases, which can be combined in the same team.

Agencies with client projects

One team, one project per application. Add the client's contacts and give them a status page with their logo on their domain.

UptimeStatus pageClient contacts

Your own web applications

See known vulnerabilities in Composer, npm or Cargo packages early and read grouped errors from production instead of searching through log files.

VulnerabilitiesLogsWebhook

Servers in production

Notice full disks and sustained load before an outage. Every new server starts with four alert rules, and a silent agent is itself an alert.

AgentAlert rulesScheduled jobs

Docker stacks

The agent runs as an image in your Compose file and reports each service separately. If a service goes down, you get the message even when the website still responds.

DockerServicesMetrics

Internal systems and your own locations

Your own runner checks from your location. Web interfaces in a private network are possible too, if you allow it in the runner's configuration.

Own runnerUptime

Content of shops and websites

Notice when prices, delivery times or legal texts change, intended or not, and keep track of newly added pages.

Page changesSitemap

See all use cases of inping

Integration

How do I add inping?

In three steps. Uptime runs after the first step, with no installation. For server values, you add a single command on the server.

Create a project

Sign up for free, create a project and enter the URLs. From then on, the runners of inping check them at the interval you choose.
2
Start the agent on the server
```
curl -fsSL https://www.inping.io/install.sh | INPING_TOKEN=<token> sudo --preserve-env=INPING_TOKEN sh -s -- --project <project-id>=/srv/shop
```
The app shows the finished command with your token and project ID under Agents → Add agent. The token is valid for 24 hours and is shown once. The first values appear after one interval at most.
Set up notifications

Decide per project which event reaches whom: by email or as a signed webhook. Every new server comes with four alert rules, such as CPU above 90% for 5 minutes.

Guides for each system

No account yet?

This command searches a project directory for known vulnerabilities in its packages and shows a report without login. It exits with an error code when it finds any, so it also fits into a CI job.

curl -fsSL https://www.inping.io/scan.sh | sh -s -- .

Privacy

Run in the EU, by a company from Germany

The platform runs on servers in the European Union.
The operator is medienakzent from Konstanz, Germany.
A data processing agreement under Art. 28 GDPR is offered.
IP addresses in notices about new devices are only stored truncated (IPv4 /24, IPv6 /48).
We do not sell data.
Checks can run through runners on your own hardware.

Payment and invoicing go through the reseller Paddle, a company from the United Kingdom. You remain responsible for lawful use in your company: we say what we do and do not replace a legal review.

GDPR server monitoring Server monitoring in the EU Data processing

Pricing

Start for free, grow later

One price for the whole team, with as many team members as you like. The Free plan needs no payment details.

Free €0/ month

Projects: 1
URLs per project: 10
Agents: 2
Own runners: 1

Pro €10/ month

Projects: 5
URLs per project: 25
Agents: 5
Own runners: 2

Scale €79/ month

Projects: 50
URLs per project: 100
Agents: 40
Own runners: 15

Business €249/ month

Projects: 250
URLs per project: 250
Agents: 150
Own runners: 50

Prices exclude VAT. Beyond these, there are Custom plans from €249 a month. Compare all plans and prices. How inping differs from other tools is set out in the comparison with other monitoring services.

Questions

Frequently asked questions about inping

What is inping?

inping is a website and server monitoring service by medienakzent from Konstanz, Germany. It monitors websites and the servers behind them and tells you by email or webhook when a website goes down, a page changes, a package has a known vulnerability or a server runs out of resources.

Is inping free?

The Free plan is permanently free and needs no payment details: 1 project, 10 URLs per project, 2 agents and 1 own runner. Larger plans are listed on the pricing page.

Do I need an agent for uptime monitoring?

No. Uptime and page changes run through the runners of inping, so you install nothing for them. You only need the agent for server values, packages, scheduled jobs and logs from the host.

Can the agent change anything on my server?

The agent is built to only read. It writes solely to its own directory (token and buffer), runs as an unprivileged user and opens no inbound port.

Which systems are supported?

The agent runs on Linux, macOS, FreeBSD and Windows, each for amd64 and arm64, and as a Docker image in a Compose file. The runner is available for Linux with systemd and for Docker.

Does inping check by ping, port check or SNMP?

No. The uptime check is an HTTP(S) request that requires the expected status code within the timeout. inping does not offer pure ICMP, port or SNMP checks.

Where is the data processed?

The platform runs on servers in the EU, the operator is medienakzent in Germany, and a data processing agreement under Art. 28 GDPR is offered. Payment goes through the reseller Paddle, a company from the United Kingdom. You as the customer remain responsible for lawful use.

Can inping be connected to other tools?

Yes. There is an API with personal tokens and OpenAPI documentation, signed webhooks and MCP tools for AI assistants, which can query the status of a project and create new projects.

Your first URL is entered in a few minutes.

Start for free See integration

Server and website monitoring. All in one place.

What does inping do?

Uptime

Servers

Vulnerabilities

Page changes

Logs and errors

Status pages

Notifications

How does the data get to inping?

What the agent may do on your server

What can I use inping for?

Agencies with client projects

Your own web applications

Servers in production

Docker stacks

Internal systems and your own locations

Content of shops and websites

How do I add inping?

Create a project

Start the agent on the server

Set up notifications

Guides for each system

No account yet?

Run in the EU, by a company from Germany

Start for free, grow later

Frequently asked questions about inping

Your first URL is entered in a few minutes.