Home / Products / Teams & Service / Kolab Monitoring

Kolab Monitoring · Veyer In build

Know it broke before your customers do

Kolab Monitoring watches your website, your API, your backups and your till sync, and sends a WhatsApp the moment something you rely on actually breaks. Your customers get a branded status page that tells the truth: all services operational, your work is safe.

Book a walkthrough See pricing

Alarms fire only on observed impact from your own probes, never on rumour
A backup that did not run is an incident: heartbeat watching built in
WhatsApp alerts with quiet hours, because nobody reads email at 2 am
Branded status pages in three languages, on your own domain

Made for

Online stores and booking sitesMSPs and IT teamsRetail groups with till syncCold rooms and sensor gatewaysSchools and member portalsEvery Kolab vertical

Finding out from an angry customer is not monitoring

Most Mauritian businesses discover an outage the worst way: a customer calls, a sale is lost, or Monday reveals the backup quietly stopped running in March. The tools that solve this are priced in dollars, and their paid tiers cost more than the hosting they watch. So nobody watches, and the silence gets mistaken for health.

Veyer probes your things from the outside, the way a customer reaches them: the website, the API, the certificate about to expire, the nightly job that must check in or be declared missing. When something you rely on actually breaks, the right person gets a WhatsApp, an incident opens itself, and the first probe that sees recovery closes it. When nothing is broken, Veyer stays quiet, which is the harder discipline.

This is not a product imagined on a whiteboard. It is the monitoring NexOps already runs on its own infrastructure, and the service-status doctrine every Kolab product ships with, packaged so any business can point it at its own systems. Every Kolab vertical gets its status page powered by Veyer; your e-commerce site, office internet or fridge gateway can sit right beside them.

The watcher already works

Veyer is in build, but its two halves exist and run today: a live monitor on NexOps infrastructure and a written status doctrine shipped in every NexOps product.

The health-card monitor runs daily on the NexOps VM stack: systems roll up to cards, drill into individual checks, and alert on WhatsApp
Every NexOps product ships a service-status module with probes, incident history and maintenance mode, built on a written doctrine
Auto-incidents, flap debounce, deduplication and vendor-feed context are running code, not a roadmap
Kolab status pages move onto Veyer first: we are our own founding customer

Modules

Everything inside Kolab Monitoring

Every module is a brick. Start with what hurts most, snap on the rest when you are ready.

Uptime Probes

HTTP, ping, TLS expiry and keyword checks, run from the outside the way a customer arrives.

Heartbeats & Cron Watch

Dead-man switches for scheduled jobs. A backup that did not run is an incident, not a mystery.

Public Status Pages

Branded per product or per business, on your own domain, in English, French and Kreol Morisien.

Auto-incidents

Open on healthy-to-broken transitions, deduplicated, and closed by the first probe that sees recovery.

WhatsApp, SMS & Email Alerts

Per-contact routing and quiet hours, so the right person wakes up, once.

Maintenance Windows

Announced ahead, subscribers notified, tracked, and excluded from uptime honestly.

Vendor Feed Context

Cloud provider incidents shown as context: provider issue, you are not affected. Never your alarm.

Uptime & Response History

Honest percentages by month and response-time charts, the same numbers your customers see.

Multi-site Checks

Down for everyone, or just your office connection? Probes from more than one place settle it.

On-call Rotation Light

Who gets woken this week, visible to the whole team and fair by design.

Embedded Status Widgets

A live status dot inside any app or site you run, powered by the same probes.

Subscriber Updates

Customers subscribe to your status page and receive incident notices in their language.

A closer look

How Kolab Monitoring feels day to day

The checks

Every check, its true state, at a glance

Each thing you watch carries one of four states: ok, degraded, down or unknown, and unknown before a first run never alarms. One affected service turns the summary orange; two or more turn it red. No mystery colours, no guessing.

HTTP, ping, TLS expiry and keyword probes on your schedule
Heartbeat checks sit beside uptime checks in one list
One affected service shows orange, two or more show red

The 2 am alert

WhatsApp wakes you; recovery lets you sleep

When a real outage is confirmed, the on-call contact gets a WhatsApp with what broke, since when, and from how many probes. Acknowledge it, fix it, and the first probe that sees recovery closes the incident and says so, with the downtime on the record.

Per-contact routing: the right person, not the whole group
Quiet hours for the small stuff, never for a confirmed down
Recovery closes the incident automatically, with times logged

Honest incidents

Incidents open themselves, and only for real

A bad probe must persist for about 90 seconds before an incident is recorded, so a wobbly wifi moment never spams your history, though the status icon reacts instantly. One outage is one deduplicated incident, however many probes saw it.

Flap debounce: about 90 seconds of confirmed impact before history records it
Deduplication: one outage is one incident, not forty
Vendor incidents shown as context, never as your alarm

The status page

Reassurance with honesty, on your domain

A status page has one job: telling your customers the truth kindly. All services operational, and your work is safe. When something breaks, the incident appears with plain words, and when maintenance is planned, it is announced ahead and excluded from uptime.

Your logo, your domain, three languages
Maintenance announced ahead, subscribers notified, uptime excluded
Uptime percentages your customers see match the ones you see

Local by design

A watcher that knows the island

Outages here have local causes and local channels. Veyer treats cyclones, CEB cuts and WhatsApp as first-class citizens, not edge cases.

WhatsApp first

Nobody reads email at 2 am, but everyone hears WhatsApp. Alerts land where Mauritius already talks.

Cyclone aware

A Class III warning banner on your status page tells customers why deliveries pause, before they ask.

Power-cut context

Multi-site checks tell a CEB cut at your office from a real outage at your host, so you do not restart a server that was never down.

Three languages

Status pages and incident notices in English, French and Kreol Morisien, so every customer reads the truth comfortably.

Rupees, not dollars

The dollar tools charge more per month than a Mauritian SME pays for hosting. Veyer is priced in rupees, per organisation, with unlimited teammates.

Support that answers

A local team on local hours. When your monitoring confuses you at a bad moment, a human picks up.

Boost for ops teams, without pager pressure

Veyer never rewards closing incidents fast, because that rewards lying. Boost celebrates the quieter virtues: calm systems, honest write-ups and windows that end on time.

Incident-free streaks

Every service builds a visible streak of quiet days. The team that keeps things boring finally gets the credit for it.

Honest-postmortem badges

Writing the what-happened note earns points. Hiding it earns nothing. The record is the achievement, not the silence.

Estimate discipline

Maintenance windows that end when they said they would earn points. Customers learn your announcements can be trusted.

More about Kolab Boost

In the wild

What it looks like in real businesses

An online store in Quatre Bornes

Used to learn the site was down from an angry customer the next morning. Now a WhatsApp at 02:14 and a fix by 02:31, with 17 minutes on the record instead of a lost Saturday.

An MSP with 30 client sites

Runs thirty branded client status pages from one screen, and links each incident to its Kolab ITSM ticket. Clients stopped phoning to ask if it is just them.

A cold-room operator in Goodlands

The fridge gateway missed its heartbeat at 03:00 and Veyer said so. The technician arrived before sunrise, and the weekend stock survived.

Pricing

Kolab Monitoring pricing, in rupees

Indicative launch pricing, per organisation per month, VAT excluded. Unlimited teammates at every tier, and nothing is charged before general availability.

Veyer Solo

One business, watched properly.

Rs 490 / organisation / month

10 checks and 1 status page
HTTP, ping, TLS and keyword probes
WhatsApp and email alerts
Auto-incidents with honest history

Start watching

Founding rate

Veyer Biznes

Status pages your customers subscribe to.

Rs 1,490 / organisation / month

50 checks and 3 status pages
Heartbeats and cron watching
Maintenance windows, announced and excluded
Subscriber updates in three languages

Go Biznes

Veyer Group

Many systems, many pages, one watcher.

Rs 3,900 / organisation / month

Unlimited checks and status pages
Multi-site probes and on-call rotations
API and embedded status widgets
Priority support

Talk to us

Prices per person per month, VAT excluded. Annual billing takes two months off. Indicative pricing: nothing is charged before general availability, and pilot customers lock their launch price for two years.

Questions

Asked all the time

The status icon turned orange but no alert arrived. Why?

The icon reacts instantly, but an incident is only recorded once a bad probe persists for about 90 seconds. A wobbly wifi moment should not spam your history or your sleep. If it is real, the alert follows within two minutes.

Our cloud provider is having an incident. Will Veyer alarm?

Only if your own probes see impact. Vendor status feeds are shown as context: provider issue, you are not affected. Your alarm fires on what actually happened to your service, never on somebody else's dashboard.

Can the status page live on our own domain?

Yes. Branded per product or per business, on a custom domain, in English, French and Kreol Morisien. Customers subscribe and receive incident and maintenance notices in their language.

How is uptime calculated?

Honestly. Announced maintenance is excluded, unknown before a first run never counts against you, and the monthly percentage your customers see is the same one you see. No creative rounding.

What happens during a cyclone or a CEB cut?

A cyclone banner on your status page explains the pause to customers. Multi-site checks distinguish a power cut at your office from a real outage at your host, so the incident record stays truthful.

Do extra teammates cost more?

No. Every tier includes unlimited teammates; you pay for checks and status pages, not for people. Watching things should not get more expensive because more of you care.

Family

Let Veyer keep watch

Point it at your website, your backups and your till sync, and give your customers a status page that tells the truth. Founding customers lock the launch rate before general availability.

Book a demo See all products