We start with a full audit of your environment — security posture, infrastructure, and the day-to-day pain points your team actually feels.
02 / Harden
Lock it down, set it up
We close the gaps, standardize your tools, and put monitoring and backups in place so problems get caught before they spread.
03 / Manage
Keep it running
Round-the-clock monitoring, patching, and a help desk on a flat monthly rate. We handle the technology so you don't have to.
Why Sparx
Built for businesses that can't afford downtime.
You get a senior team that knows your setup, answers fast, and bills predictably — not a rotating cast of ticket numbers. We're based in Midtown and we pick up the phone.
Senior engineers, not a call centerFixed monthly pricingOn-site when you need itVendor-agnostic recommendations
Photo placeholder
Suggested: your team in the office, or the NYC skyline / Midtown location.
Let's talk
Let's harden your stack.
Book a free 30-minute consult. We'll review your current setup, flag the biggest risks, and show you exactly what a managed plan would cover.
Vertical axis starts at 1,400, not zero, to show the shape of the change.
Devices under management
Period
Devices
Change
Sep 2026
1,784
+54
Aug 2026
1,730
+71
Jul 2026
1,659
-20
Jun 2026 est
1,679
+24
May 2026 est
1,655
+18
Apr 2026 est
1,637
+24
Mar 2026 est
1,613
+27
Feb 2026 est
1,586
+24
Jan 2026 est
1,562
+22
Dec 2025 est
1,540
+24
Nov 2025 est
1,516
+21
Oct 2025 est
1,495
—
Infrastructure under management: 170 access points, 130 switches, 122 cameras & sensors, 41 door access, 38 gateways & routers, 16 wireless bridges, 9 other, 8 power distribution, 1 network storage, 1 cellular backup. Months marked est are modelled placeholders — combined recording began September 2026. They are replaced automatically as real snapshots accumulate.
Backup protection
Backup protection
1,915
Protected · 97% healthy
55
Servers & endpoints · 43 healthy
1,860
Microsoft 365 & Google users · 1,831 healthy
Protected systems and users, daily — Sat 22 Aug to Sun 20 Sep
Vertical axis starts at 1,880, not zero, to show the shape of the change.
Backup protection
Period
Protected
Change
Sun 20 Sep
1,915
0
Sat 19 Sep
1,915
+2
Fri 18 Sep
1,913
+2
Thu 17 Sep
1,911
+7
Wed 16 Sep
1,904
+4
Tue 15 Sep
1,900
0
Mon 14 Sep
1,900
0
Sun 13 Sep
1,900
0
Sat 12 Sep
1,900
0
Fri 11 Sep
1,900
0
Thu 10 Sep
1,900
+8
Wed 9 Sep
1,892
+1
Tue 8 Sep
1,891
0
Mon 7 Sep
1,891
0
Sun 6 Sep
1,891
0
Sat 5 Sep
1,891
+1
Fri 4 Sep
1,890
+1
Thu 3 Sep
1,889
0
Wed 2 Sep
1,889
0
Tue 1 Sep
1,889
-6
Mon 31 Aug
1,895
0
Sun 30 Aug
1,895
-1
Sat 29 Aug
1,896
+3
Fri 28 Aug
1,893
0
Thu 27 Aug
1,893
+2
Wed 26 Aug
1,891
+2
Tue 25 Aug
1,889
+1
Mon 24 Aug
1,888
0
Sun 23 Aug
1,888
0
Sat 22 Aug
1,888
—
Last successful backup verification: Sun 20 Sep 2026, 2:30 AM — a backup image booted and was screenshotted, confirming it would restore. Servers are counted per machine and Microsoft 365 per user, so the headline combines two units — the split above is the honest breakdown. Decommissioned systems are excluded from every figure. 1,129 further Microsoft 365 and Google accounts are selected for protection but cannot receive a backup — staff accounts since deactivated or deleted, and mailboxes with no licence covering them. They are excluded here rather than counted as failures.
Patch queue
Critical-patch compliance
82%
Critical-patch compliance
809 of 982
Computers fully patched
266
Offline · excluded from the figure
Critical-patch compliance, daily — Sat 22 Aug to Sun 20 Sep
Critical-patch compliance
Period
Compliance %
Change
Sun 20 Sep
82
0
Sat 19 Sep
82
+1
Fri 18 Sep
81
+5
Thu 17 Sep
76
+7
Wed 16 Sep
69
+43
Tue 15 Sep
26
-51
Mon 14 Sep
77
-5
Sun 13 Sep
82
-2
Sat 12 Sep
84
+2
Fri 11 Sep
82
-2
Thu 10 Sep
84
+1
Wed 9 Sep
83
+3
Tue 8 Sep
80
0
Mon 7 Sep
80
+1
Sun 6 Sep
79
-7
Sat 5 Sep
86
+1
Fri 4 Sep
85
-2
Thu 3 Sep
87
+2
Wed 2 Sep
85
+3
Tue 1 Sep
82
+4
Mon 31 Aug
78
-3
Sun 30 Aug
81
+3
Sat 29 Aug
78
-6
Fri 28 Aug
84
0
Thu 27 Aug
84
+1
Wed 26 Aug
83
-1
Tue 25 Aug
84
+1
Mon 24 Aug
83
0
Sun 23 Aug
83
+1
Sat 22 Aug
82
—
What this number means
Of the computers we could reach, 82% have no critical security update waiting to be installed. We count computers, not individual updates — a machine waiting on one update and a machine waiting on ten both count once.
Why it is never 100%, and should not be
Microsoft and other vendors release new critical updates constantly — monthly on schedule, and occasionally at a few hours’ notice. The moment one is released, every computer in the world counts as waiting for it until it installs. A fleet showing 100% would mean either nothing was released that month, or updates are being pushed out the instant they appear, untested. Neither is something to aim for.
We hold new patches back on purpose
A bad update can break more than the hole it closes — and it happens several times a year. We deliberately wait about two weeks before deploying, so that faults surface on someone else’s fleet rather than yours. During that window the affected machines are counted as waiting even though they are doing exactly what our policy intends. A large part of the gap below 100% is this deferral working as designed.
Restarts and switched-off machines
Many updates only finish installing after a restart, so a computer can sit as “waiting” until someone reboots it. Laptops that are off, travelling or on holiday cannot receive anything at all — we exclude any machine not seen for 14 days from this figure entirely (266 right now), because counting a switched-off spare against our patching would measure nothing anyone can act on.
What good looks like
A steadily maintained fleet sits in the 70–90% range and moves around as updates are released and then rolled out. What matters is the trend and that no machine stays behind for long — not the single number on any given day.
671 individual critical updates are queued across the fleet. Most are within the deferral window described above.
Assets online
Assets online, last 24 hours
1,048
Online now · 59% of fleet
1,092
Daily peak
1,041
Overnight low
Endpoints seen within 15 minutes, plus network hardware reporting connected — sampled hourly, Sat 5 AM to Sun 4 AM
Vertical axis starts at 1,020, not zero, to show the shape of the change.
Assets online, last 24 hours
Period
Online
Change
Sun 4 AM
1,048
+7
Sun 3 AM
1,041
-7
Sun 2 AM
1,048
0
Sun 1 AM
1,048
-7
Sun 12 AM
1,055
-5
Sat 11 PM
1,060
-1
Sat 10 PM
1,061
+3
Sat 9 PM
1,058
-8
Sat 8 PM
1,066
-2
Sat 7 PM
1,068
-1
Sat 6 PM
1,069
-2
Sat 5 PM
1,071
-5
Sat 4 PM
1,076
-6
Sat 3 PM
1,082
+3
Sat 2 PM
1,079
+3
Sat 1 PM
1,076
-10
Sat 12 PM
1,086
-6
Sat 11 AM
1,092
+5
Sat 10 AM
1,087
+12
Sat 9 AM
1,075
-3
Sat 8 AM
1,078
+21
Sat 7 AM
1,057
+1
Sat 6 AM
1,056
-12
Sat 5 AM
1,068
—
A fleet is never fully online — laptops sleep and desks power down after hours, so this curve dips overnight and recovers each morning. Network hardware stays up around the clock, which is why the overnight floor sits well above zero.
sparx://noc-overview
LIVE
