Focus attention faster
Conditions that need a decision are brought forward, so an operator does not scan a list of healthy devices to find the one that changed.
Device and network monitoring — one site or many
All your devices on one screen. Know where to look first.
Device Monitor watches your devices and networks — one location or dozens of branches — keeps their operational history in one place, and brings the conditions that need attention to the front — so your team spends its time resolving, not searching.
- Data separated per organisation
- Arabic and English, RTL and LTR
- Browser access over HTTPS
Central Branch
Reporting
East Branch
Needs attention
West Branch
Not reachable
The difference
Online and offline is a starting point, not an answer
A single status flag tells you that something changed. It does not tell you what to do about it.
Status only
A device is offline
You learn that something is down. Whether it is that one device, the branch link, or a restart that was expected is still an open question — and answering it usually means calling the branch.
- No indication whether one device or a whole branch is affected
- No record of whether the same thing happened last week
- Every case starts with a phone call
With operational context
A device is offline — and here is what surrounds it
Device Monitor keeps the resource readings, the branch reachability results and the alert history next to the status change, so the first questions your technician would ask are already answered.
- Whether other devices in the same branch are still reporting
- Whether the branch network still answers a probe
- Whether this device has a history of the same behaviour
- Which alerts fired, at what severity, and when
Why teams use it
Built for the operator on shift
Four things the platform is designed to do well.
Every branch, centrally
Regions, branches and devices form one hierarchy. Review the whole organisation, or open a single branch, without switching tools.
Context a technician can act on
Resource readings, connection history and past alerts stay with the device, so whoever picks up the case starts from the same picture.
Act before it spreads
Alerts carry a severity and a history, so a condition that keeps returning can be handled as a pattern instead of being closed one case at a time.
How it works
Monitor, identify what changed, act
Three steps, running continuously.
Monitor
An agent on your Windows devices, and probes running inside each branch, report device and network state continuously.
Identify what changed
Readings are kept over time, so a normal fluctuation can be told apart from a change in behaviour that is worth showing you.
Alert and act
A notable change raises an alert with a severity — visible in the dashboard, and as a push notification where it is enabled.
What it monitors
Two ways to cover a branch
Some devices can run software. Most of the ones in a branch cannot. Device Monitor covers both.
Device Agent
Installed on the device
A small Windows service runs on the device and reports its own state: connection, resource readings, operating-system events and restarts.
- Device-level detail without opening a session on the machine
- Keeps reporting through short network interruptions
- Updates itself, so the fleet does not drift apart
Branch probe
Nothing installed on the target
For printers, cameras, routers and anything else you cannot install software on, an agent inside the branch checks the address and reports whether it answers.
- Covers devices that cannot run an agent
- Checked from inside the branch, so the result reflects the local network
- One probe per branch, assigned by the platform
Inside the product
The operations view
One screen for everything you monitor: what is reporting, what needs attention, and what changed recently.
The operations view
Devices monitored
128
Reporting now
121
Need attention
5
Not reachable
2
Reporting devices, last 7 days
| Branch | Devices | State | Last change |
|---|---|---|---|
| Central Branch | 42 | All reporting | 2 min ago |
| North Branch | 31 | All reporting | 18 min ago |
| East Branch | 35 | Needs attention | 1 hr ago |
| West Branch | 20 | Not reachable | 3 hrs ago |
Sample data for illustration. No customer information is shown.
Operational analytics
Behaviour over time, not just the current reading
Readings are kept, so the platform can describe how a device or a branch has actually behaved — and point out what is worth a look.
Device Monitor describes what its data shows and highlights what deserves attention. It does not promise to predict a hardware failure, and it does not claim to identify a root cause on its own — any suggestion it offers is for your team to verify.
Trends across the estate
See how reporting, alert volume and reachability moved over a period, instead of judging from a single moment.
Recurring issues
When the same device or branch keeps producing the same condition, the occurrences are grouped so you can treat the cause rather than the repeat.
Device and branch context
A device is compared against its own history and against the rest of its branch, so an unusual reading is recognisable as unusual.
Where to look first
Items that need a decision are ordered, so a short review covers the ones that matter most.
Alerts and response
An alert you can actually work from
Alerts carry a severity and stay in a history you can review, resolve and dismiss.
Severity on every alert
Critical, warning and informational are distinguished, so triage is not a flat list.
A history that stays
Resolved and dismissed alerts remain on record, so you can look back at what a device has been doing.
In the dashboard, and on the phone
Alerts appear in the product, and can also arrive as a push notification where push is enabled and the browser supports it.
Per-user notification settings
Each user chooses which event types they want pushed to them.
Critical
Device stopped reporting — Central Branch
2 min ago
Warning
Repeated short disconnections — North Branch
18 min ago
Info
Device resumed reporting — East Branch
1 hr ago
Sample data for illustration. No customer information is shown.
Security and access
Access that stays inside your organisation
Four protections that are in place today — described specifically, without certifications we have not earned.
Customer data isolation
Each customer works inside their own separated space. Every request is scoped to the account that owns the data, so one customer can never read the devices, branches, alerts or history belonging to another — the separation is enforced on the server, not by the screen you are looking at.
Encrypted HTTPS connections
Every page, sign-in and payment hand-off travels over an encrypted HTTPS connection, and the monitoring agent cryptographically signs the data it reports so the server can reject anything it did not send. This protects data in transit.
Role-based access control
Every user is given a role within their own account, and that role decides which pages they can open and which actions they can take. You add people at the level of access they actually need, and change it later without moving their data.
Layered sign-in protection
Sign-in requests are protected against forged submissions, repeated attempts are rate limited, and one-time transfer codes are used when moving a signed-in user to their own account space. Sessions expire after a period of inactivity.
No system is completely secure. How data is processed, shared and retained is set out in full in the Privacy Policy. Read the Privacy Policy
Plans
Plans sized by devices, branches and users
The pricing page is the single source for current plans, limits and prices — so nothing quoted here can fall out of date.
- Monthly or yearly billing
- Limits listed per plan
- Payment handled by Moyasar
صُنع بعقول سعودية — Built by Saudi minds
Device Monitor is built in Saudi Arabia, Arabic first, for the way Saudi organisations actually run their branches.
Frequently asked questions
What exactly does Device Monitor monitor?
Two things. Windows devices running the agent report their own connection state, resource readings and operating-system events. Network addresses inside a branch — printers, cameras, routers and similar — are checked from a probe running in that same branch, which reports whether the address answers.
Do I have to install software on every device?
No. Devices that can run the agent report in detail. Everything else is covered by the branch probe, which needs nothing installed on the target device.
Can it cover more than one branch?
Yes. Regions, branches and devices form a single hierarchy, and you can review the whole organisation or open one branch at a time.
Is my data separated from other customers?
Yes. Each customer is a separate tenant and every query is scoped to it. Inside a tenant, what each user can see and change is controlled by their role.
Is the interface available in Arabic?
Yes. The interface is available in Arabic, right to left, and in English, left to right. Each user can switch at any time and the choice is remembered.
Will it catch every failure?
No monitoring system can promise that, and we do not. Detection depends on the device being reachable, the agent running, and the branch network and firewall allowing the check. Device Monitor is a monitoring aid, not a guarantee — this is stated in our Terms and Conditions. Read the Terms and Conditions
How do I subscribe?
Choose a plan on the pricing page and complete the checkout. Payment is processed by Moyasar: card details are entered on their hosted page and are never stored on our servers.
See which plan fits you
Plans are sized by devices, branches and users, so you only pay for what you monitor. The pricing page lists the current limits and prices.
View plans