What does Zendrock actually check?

Health, SLO burn, open incidents, change windows, and any policy you define. The check either passes or it does not — with the evidence attached.

Do we have to replace our observability stack?

No. Zendrock reads from the systems you already run: Datadog, Grafana, Prometheus, PagerDuty, GitHub, GitLab, Kubernetes. We do not ask you to send traffic through us.

How long does a trial take to set up?

Most teams connect a source control provider and one observability backend in under an hour. The first verified release is usually the same day.

Can we run checks in CI?

Yes. Growth and Enterprise expose a status check and a CLI. Starter can gate on GitHub/GitLab checks for a single repository.

Where is data stored?

US by default. Enterprise can pin residency to the EU or to a private network you control.

Where does it actually run?

On your own server — that is the point of self-hosted uptime monitoring. It is a PHP application with a database, a cron entry that fires the check dispatcher every minute, a queue worker that performs the checks, and a WebSocket process for the live updates. A modest VPS handles it comfortably, and every check result stays in your database.

What exactly does it check?

HTTP endpoints. For each URL you choose the method (HEAD, GET or POST), the status code that counts as healthy, a timeout in seconds, and an interval of 1, 5, 15, 30 or 60 minutes. If the status matches it is up; if it matches but takes more than two seconds it is degraded; a timeout, connection error or wrong status code is down — after up to three internal retries.

How do alerts work, and who gets them?

When an endpoint changes state, an incident is opened or resolved and notifications go to the project owner and every invited member of that project. Each person controls their own channels — email, in-app, both or neither — in their settings. Certificate expiry alerts follow the same rules, firing once per threshold band at 30, 14 and 7 days and again on expiry.

Can I monitor internal services behind our firewall?

Yes, and it is one of the better reasons to run an internal uptime dashboard rather than a hosted service. Because the checks originate from your own server, anything that server can reach can be monitored — internal hostnames, private IP addresses, staging boxes. Self-signed certificates still report an expiry date, since the certificate read does not enforce chain verification.

How is this different from a hosted monitoring service?

Three practical differences. The data lives on your server rather than someone else's; you are billed in rupees rather than dollars; and there is no per-check or per-monitor metering, so you can point it at every client site you run instead of rationing endpoints. The trade-off is honest: checks come from one location you control, so it will not tell you whether a site is unreachable from Frankfurt specifically.

How many endpoints can I add?

There is no limit in the software. The real constraint is your server: each check is a queued HTTP request, so a few hundred endpoints on one-to-five-minute intervals is unremarkable for a small VPS with a queue worker or two. You can safely run multiple workers — the check job is unique per endpoint, so the same endpoint is never probed twice at once.

What about team access?

Every project has one Owner and any number of invited members. Owners manage the project and the team, Editors add and change applications and endpoints, and Viewers are strictly read-only — which is what you give a client or a manager. Invitations go out by email and must be accepted from that exact address. If you own several projects, Team access lets you invite one person to many of them at once.

Do I need a devops person to run it?

To install it, someone who is comfortable with a Linux server, a cron entry and a supervised background process — an afternoon's work for most developers, and the deployment notes cover it. To use it afterwards, no: adding endpoints and reading the dashboard is ordinary web application work. If nobody on your team wants to own the server side, the Supported and Hosted tiers exist precisely for that.

Uptime & health monitoring

Know it is down before the client does.

YupItsUp is self-hosted uptime monitoring you run on your own server. Group services into projects and applications, attach the URLs you care about, and a scheduler checks them around the clock. The dashboard updates live over WebSockets, and email lands the moment something goes down, recovers, or is about to lose its certificate.

Book a demo

See pricing

Runs on your server — the check data never leaves it: Self-hosted
Shortest check interval, per endpoint: 1 min
Projects, applications and endpoints — no per-check metering: Unlimited

The problem

The client finds out first, and then you find out from the client.

Most small software teams have no uptime monitoring at all. The site is up because nobody has said otherwise. A WhatsApp message at 11 at night — 'site down?' — is the alerting system, and by the time it arrives the thing has usually been down for hours.

You hear about downtime from the person paying you

Every minute between the outage and that message is a minute you could have been fixing it. Instead you spend the first ten explaining why you did not know.

An agency with forty client sites cannot tell you which are healthy

There is no single screen. Checking means opening forty tabs, which nobody does, so in practice nobody checks anything until a client complains.

Certificates expire quietly and take the site with them

Nothing warns you at thirty days. The renewal cron broke in March, nobody looked, and the browser warning is the first anyone hears of it — usually on a Sunday.

Internal systems have no owner watching them

The HR portal, the inventory API, the staging box. Not customer-facing, so nothing is monitored, and then it has been down for three days and someone's month-end is ruined.

Hosted monitoring is priced in dollars and metered per check

Fifteen or thirty dollars a month is a real line item from Karachi or Lahore, and the pricing page makes you ration checks and endpoints instead of monitoring everything you own.

You cannot prove the uptime you promised

A client says the site was down 'all last week'. You believe it was not. Neither of you has a record, so the argument is settled by whoever is more insistent.

How YupItsUp works

Add a URL. The scheduler does the rest, forever.

There is no agent to install on the monitored machine and nothing to configure on the client's side. You point it at URLs over HTTP, and everything after that — checking, retrying, opening incidents, alerting the right people — happens on its own.

Group services into projects and applications

A project is usually one client or one product line. Inside it, applications are the logical services — marketing site, REST API, admin panel — and endpoints are the actual URLs underneath.

Attach the endpoints you care about

Full URL, method (HEAD, GET or POST), the status code that means healthy, a timeout and how often to check: every 1, 5, 15, 30 or 60 minutes. Health-check routes work as well as homepages.

The scheduler checks, retries, then decides

A dispatcher runs every minute and queues whatever is due. Transient failures are retried up to three times before anything is called down, so a single dropped packet does not wake you up.

You get told, and the screen is already right

A status change opens an incident and emails the project owner and every team member on it. The dashboard, project pages and endpoint pages update live over WebSockets — nobody refreshes anything.

What you get

Everything YupItsUp does, in one place.

Scheduled HTTP checks

GET, HEAD or POST against any URL, with your own expected status code, timeout and interval down to one minute. HEAD is the cheapest and usually enough.

Up, down, degraded, unknown

Degraded means the response was correct but slow — over two seconds. It is the state that tells you something is going wrong before it actually goes down.

Live over WebSockets

Status badges, uptime cards, the response-time chart and the incident list all update the moment a check completes. Leave the dashboard on a screen in the office and it stays true.

SSL certificate expiry tracking

Every check on an HTTPS endpoint reads the leaf certificate and shows expiry, days remaining and issuer. You are alerted at 30, 14 and 7 days, and again if it expires.

Automatic incident history

An incident opens the moment an endpoint goes down and closes when it recovers, with start time, resolve time and duration in minutes. That is the record the client argument needs.

Uptime and response-time stats

Uptime percentage over 7 and 30 days, average response time, a 24-hour chart with one bar per check coloured by status, and a paginated list of every probe.

Email and in-app alerts

Down, recovered and certificate-expiry notifications go to the project owner and every invited member — each person choosing their own channels in their settings.

Roles and invitations

Owners run the project and the team. Editors manage applications and endpoints. Viewers read only. Invite by email, or bulk-invite one person across every project you own.

Pause without deleting

Untick Active on an endpoint and checks stop, history stays. For the staging box you take down deliberately, or the client whose renewal is still being discussed.

Who it's for

One system. Every person it has to serve.

Software houses and agencies

One screen for every client site and API you are responsible for, with a project per client and a record of what happened.

A project per client, endpoints grouped by service underneath
Incident history with durations when a client questions uptime
Certificate expiry warnings across the whole client book
No per-endpoint pricing, so you can monitor every client site

In-house IT teams

The internal systems nobody watches — HR portal, ERP, intranet, the reporting job — finally have something checking them.

Runs inside your own network, on hardware you control
Internal hostnames and IPs work as long as the server can reach them
Self-signed certificates still report an expiry date
Read-only access for managers who just want the dashboard

Product teams

Production and staging in the same place, with the degraded state catching slow responses before users start complaining.

Separate projects for production, staging and internal tooling
Per-endpoint response time charts over the last 24 hours
Editors can add endpoints without touching project settings
Live dashboard for the wall screen during a release

Solo builders

The side project you do not check daily, watched properly, without a monthly subscription in dollars.

Self-host it next to whatever you are already running
Unlimited endpoints on the free self-hosted tier
Email when it goes down and when it comes back
Certificate expiry alerts before the browser warning

Managed service providers

Prove the service you bill for, and spot the problem on a customer's system before the ticket arrives.

One project per customer with its own team members
Invite the customer as a Viewer on their own project
Uptime percentages you can quote in a review meeting
Bulk-invite an engineer across every customer project at once

Why it pays for itself

The case you can take to whoever signs the cheque.

You are the one who reports the outage

The alert reaches you before the client's message does, and the conversation changes from explaining why you did not know to telling them it is already being fixed.

Expired certificates stop being a surprise

Thirty days, fourteen, seven, and then expiry — for every HTTPS endpoint you monitor. The renewal that quietly stopped working gets caught a month before anyone sees a browser warning.

Monitoring stops being a foreign-currency bill

It runs on a server you already pay for, priced in rupees, with no per-check metering. Monitoring one more client site costs nothing, so you actually monitor all of them.

Where it runs

Web dashboard

Everything lives here: projects, applications, endpoints, incidents, charts, team and settings. Works on a laptop and on a phone browser when you are away from one.

Your own server

PHP and a database, with a cron entry, a queue worker and a WebSocket process. Deploy it on a VPS, on shared infrastructure, or on a box inside your office network.

Email and in-app alerts

Notifications go out through your own mail transport to owners and team members, and are also stored in the app for an in-app feed.

Subscription

Priced in rupees, for how Pakistani organisations actually buy.

Monthly subscription, no setup fee, and we build your data with you in the first session. Cancel whenever — we would rather keep you because it works.

Self-hosted

Freeforever

You run it on your own server and look after it yourself. The whole application, no endpoint limits, no licence key.

Unlimited projects, applications and endpoints
Live dashboard, incidents, SSL expiry and team roles
Documentation and deployment notes
Community support — no response-time commitment

Talk to us

Most chosen

Supported

Rs 9,000/ month

The same self-hosted install on your infrastructure, with us keeping it healthy — upgrades, queue and scheduler supervision, and someone to call when it misbehaves.

We install and configure it on your server, free
Upgrades applied for you as they ship
Scheduler, queue worker and WebSocket process monitored
WhatsApp and phone support in Urdu or English
Unlimited endpoints and unlimited team members

Talk to us

Hosted by Zendrock

Rs 15,000/ month

For teams with nowhere to put it. We run a dedicated instance on our infrastructure in your name — your data on your own instance, not a shared pool.

Dedicated instance, not a shared multi-tenant account
Server, backups and certificate renewal handled
Mail transport configured and tested
Move to your own server later, with the data
Free setup and endpoint import

Talk to us

Questions we actually get asked

YupItsUp, answered.

See it running on your own operation.

We will walk you through YupItsUp with your routes, your roster, your numbers — not a canned demo. If it is not a fit, we will tell you.

Book a demo

See every product