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
Nov 2026
1,688
+28
Oct 2026
1,660
-15
Sep 2026
1,675
-55
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
—
Infrastructure under management: 139 access points, 114 cameras & sensors, 100 switches, 31 gateways & routers, 20 door access, 19 wireless bridges, 9 other, 6 power distribution, 2 displays, 1 cellular backup, 1 network storage. Months marked est are modelled placeholders — combined recording began November 2026. They are replaced automatically as real snapshots accumulate.
Backup protection
Backup protection
1,937
Protected · 99% healthy
55
Servers & endpoints · 47 healthy
1,882
Microsoft 365 & Google users · 1,882 healthy
Protected systems and users, daily — Tue 20 Oct to Wed 18 Nov
Vertical axis starts at 1,800, not zero, to show the shape of the change.
Backup protection
Period
Protected
Change
Wed 18 Nov
1,937
0
Tue 17 Nov
1,937
0
Mon 16 Nov
1,937
-1
Sun 15 Nov
1,938
-109
Sat 14 Nov
2,047
-226
Fri 13 Nov
2,273
+335
Thu 12 Nov
1,938
0
Wed 11 Nov
1,938
0
Tue 10 Nov
1,938
0
Mon 9 Nov
1,938
-3
Sun 8 Nov
1,941
+1
Sat 7 Nov
1,940
-1
Fri 6 Nov
1,941
+16
Thu 5 Nov
1,925
+1
Wed 4 Nov
1,924
+18
Tue 3 Nov
1,906
+1
Mon 2 Nov
1,905
+1
Sun 1 Nov
1,904
0
Sat 31 Oct
1,904
+1
Fri 30 Oct
1,903
-39
Thu 29 Oct
1,942
+4
Wed 28 Oct
1,938
0
Tue 27 Oct
1,938
+2
Mon 26 Oct
1,936
0
Sun 25 Oct
1,936
+1
Sat 24 Oct
1,935
0
Fri 23 Oct
1,935
0
Thu 22 Oct
1,935
+1
Wed 21 Oct
1,934
+9
Tue 20 Oct
1,925
—
Last successful backup verification: Wed 18 Nov 2026, 12:23 PM — 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,188 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
83%
Critical-patch compliance
814 of 985
Computers fully patched
261
Offline · excluded from the figure
Critical-patch compliance, daily — Tue 20 Oct to Wed 18 Nov
Critical-patch compliance
Period
Compliance %
Change
Wed 18 Nov
83
-7
Tue 17 Nov
90
0
Mon 16 Nov
90
+1
Sun 15 Nov
89
0
Sat 14 Nov
89
+1
Fri 13 Nov
88
+1
Thu 12 Nov
87
0
Wed 11 Nov
87
+1
Tue 10 Nov
86
+4
Mon 9 Nov
82
0
Sun 8 Nov
82
0
Sat 7 Nov
82
0
Fri 6 Nov
82
+1
Thu 5 Nov
81
0
Wed 4 Nov
81
0
Tue 3 Nov
81
-1
Mon 2 Nov
82
-1
Sun 1 Nov
83
+1
Sat 31 Oct
82
0
Fri 30 Oct
82
0
Thu 29 Oct
82
-2
Wed 28 Oct
84
+2
Tue 27 Oct
82
0
Mon 26 Oct
82
+1
Sun 25 Oct
81
+1
Sat 24 Oct
80
0
Fri 23 Oct
80
+4
Thu 22 Oct
76
+7
Wed 21 Oct
69
+38
Tue 20 Oct
31
—
What this number means
Of the computers we could reach, 83% 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 (261 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.
593 individual critical updates are queued across the fleet. Most are within the deferral window described above.
Assets online
Assets online, last 24 hours
1,180
Online now · 70% of fleet
1,187
Daily peak
988
Overnight low
Endpoints seen within 15 minutes, plus network hardware reporting connected — sampled hourly, Tue 5 PM to Wed 4 PM
Vertical axis starts at 900, not zero, to show the shape of the change.
Assets online, last 24 hours
Period
Online
Change
Wed 4 PM
1,180
-3
Wed 3 PM
1,183
+1
Wed 2 PM
1,182
-5
Wed 1 PM
1,187
+11
Wed 12 PM
1,176
+13
Wed 11 AM
1,163
+6
Wed 10 AM
1,157
+64
Wed 9 AM
1,093
+69
Wed 8 AM
1,024
+7
Wed 7 AM
1,017
+20
Wed 6 AM
997
+6
Wed 5 AM
991
-1
Wed 4 AM
992
+4
Wed 3 AM
988
-11
Wed 2 AM
999
-7
Wed 1 AM
1,006
-2
Wed 12 AM
1,008
-10
Tue 11 PM
1,018
+4
Tue 10 PM
1,014
-8
Tue 9 PM
1,022
-5
Tue 8 PM
1,027
-18
Tue 7 PM
1,045
-19
Tue 6 PM
1,064
-64
Tue 5 PM
1,128
—
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.