Migrate

Migrate from Freshping to Quietbeat

Quietbeat gives you checks, heartbeats, a status page and on-call in one flat plan, free to start. It has no Freshping importer, so this page does not offer one. It is a guide to rebuilding the checks here: what to recreate, how each concept maps, which bulk paths exist, and how to set up alerts and a status page.

Start monitoring, free Compare the alternatives

What you get in its place.

Checks, heartbeats, a status page and paging in one plan. Quietbeat runs the HTTP, TCP and DNS checks and the heartbeats, and opens the incident that pages your team. A start ping opens a run, a fail ping carries the job's exit code, and the output you send travels with the beat.
On-call and escalation in every paid plan. Rotations, overrides and escalation ladders from Solo at $9 a month, with 1 schedule on Solo and unlimited from Team. A rotation emails the person on call; ladder pages to chat channels and webhooks repeat up to 20 rounds until acknowledged, with nothing billed per message.
One flat price with no seat charges. Team is $19 a month billed monthly, or $190 a year, for 200 monitors and 5 pageable people, with unlimited teammates.
An API, an MCP server and monitoring as code on every plan. Open to code and to agents on every plan, Hobby included: a REST API with an OpenAPI 3.1 spec, a write-capable MCP server, and a sync manifest for monitoring as code.
Hosting in Germany by an EU company. Hosted in Germany, in the EU, by an EU company.

What happened to Freshping.

From Freshworks' own deprecation FAQ, as of 2026-10-16.

Free Freshping accounts were disabled on 6 March 2026. (source, 16 Oct 2026)
Paid plans were not renewed on or after that date; a plan kept working until it expired and was then disabled, with no upgrades or plan changes. (source, 16 Oct 2026)
Freshworks said data would be retained for 90 days after an account was disabled and then permanently deleted. (source, 16 Oct 2026)
Export: free-tier accounts could export until 4 June 2026; paid accounts for 90 days after the subscription ended. Only owners and admins could export, and a download link stayed valid for 60 days. (source, 16 Oct 2026)

There is no Freshping importer in Quietbeat. Whether the deletion Freshworks announced has taken place is not something this page can confirm, and a paid plan may still be running until it expires. If you still hold an export, it is your checklist; if not, the steps below rebuild the list from your own systems.

1. Make the list.

From an export, if you have one. Every URL, host and interval you had is a row to recreate below.
From a domain scan. Type your domain at /monitors/scan, signed in. Quietbeat reads the site the way a crawler would: the front page, robots.txt, the sitemap, the usual health paths and the subdomains in certificate transparency logs. It returns a checklist of up to 25 suggestions, with the site, its health endpoints and live subdomains ticked and sitemap pages listed but unticked. Nothing is created until you say so.
From your own configuration. Your DNS zone, your deploy manifests and your crontabs name every host, URL and scheduled job you were watching.

2. Map each check.

The monitor form offers HTTP, TCP, DNS, certificate and heartbeat checks. This is how a check from elsewhere lands on them.

If you had	In Quietbeat
A check that fetched a URL	An HTTP monitor. It can also watch for a keyword and alert when the keyword goes missing.
A check on a host and port	A TCP monitor on `host:port`.
A check on a DNS name	A DNS monitor.
A ping (ICMP) check	No equivalent: Quietbeat has no ICMP check. Watch the service on the host as a TCP or HTTP monitor instead.
A scheduled job you wanted to hear about when it stopped	A heartbeat monitor: the job calls its ping URL at the end of each run, and a missed window opens an incident.
A check interval	`interval_seconds`: 60 seconds at the fastest on Hobby and Solo, 30 seconds from Team.
A public status page	A status page at `/pages`, on every plan, with badges; your own domain from Solo.
Email, chat or webhook alerts	Email is on from the first monitor. Chat and webhook channels are set at `/alert_channels` from Solo.

3. Create them in bulk.

Three paths exist. The scan above is one. The second is a manifest: declare the monitors in YAML and send it to POST /api/v1/sync. Monitors are keyed by name, so the sync creates what is missing and updates what drifted, and ?dry_run=true plans without writing. The example below ends with prune: true, which deletes monitors the manifest no longer names; leave that line out while you are still building the list.

quietbeat.yml

# quietbeat.yml
monitors:
  - name: prod site
    kind: http
    url: https://example.com/health
    interval_seconds: 300
  - name: nightly backup
    kind: heartbeat
    interval_seconds: 86400
    grace_seconds: 3600
prune: true

request

curl -sf -X POST "https://quietbeat.dev/api/v1/sync?dry_run=true" \
  -H "Authorization: Bearer qb_YOUR_TOKEN" \
  -H "Content-Type: text/yaml" \
  --data-binary @quietbeat.yml

The third is your coding agent: Quietbeat's MCP server has a create_monitor tool, so an agent that can read your old list can create the monitors one call each. How to connect one.

Each heartbeat has its own ping URL. Through MCP, create_monitor returns it in its response. Through the sync API, the heartbeat's monitor page shows the URL once if you open it within a minute of the sync; after that, choose New address there to get one. A scan creates HTTP checks only, never heartbeats. One line at the end of the job is enough:

crontab

0 3 * * *  ./backup.sh && curl -fsS https://quietbeat.dev/b/YOUR_TOKEN

4. Alerts and the status page.

Alerts. Email reaches you from the first monitor on every plan. From Solo, add chat or webhook channels at /alert_channels, and a schedule at /oncall that repeats a page up to 20 rounds until someone acknowledges.
Status page. Create one at /pages, add the monitors, and share the link or the badge. From Solo it can live on your own domain.
A free start. Hobby is 10 monitors every 60 seconds with 90 days of history, no card. Every plan.

Questions people ask.

What does Quietbeat give me in place of Freshping?

Checks, heartbeats, a status page and paging in one plan; on-call and escalation in every paid plan; one flat price with no seat charges; an API, an MCP server and monitoring as code on every plan; and hosting in Germany by an EU company.

Can Quietbeat import my Freshping checks?

No. Quietbeat has no Freshping importer, and this page does not pretend to one. The checks are recreated: one at a time, from a domain scan, from a sync manifest, or by your agent over MCP.

What happened to Freshping?

Free Freshping accounts were disabled on 6 March 2026. Paid plans were not renewed on or after that date; a plan kept working until it expired and was then disabled, with no upgrades or plan changes.

Can I still get my Freshping data?

Freshworks said data would be retained for 90 days after an account was disabled and then permanently deleted. Export: free-tier accounts could export until 4 June 2026; paid accounts for 90 days after the subscription ended. Only owners and admins could export, and a download link stayed valid for 60 days. Whether the deletion has happened is not something Quietbeat can confirm.

How do I recreate many checks at once?

Scan your domain at /monitors/scan to get a ticked checklist, or declare the monitors in a YAML manifest and send it to POST /api/v1/sync, which creates what is missing and updates what drifted. An agent connected over MCP can create them one call each.