Nexus joins every site, camera, and device you operate to the place it physically sits — from the whole world, down to a single rack unit. One picture, always current, that a duty manager and a network engineer can both read.
Cameras in one platform, endpoints in another, network gear in a third, and the floorplans in a filing cabinet. Every one of them describes the same building, and none of them knows about the others.
Alerts arrive without a place
A hostname went offline. Which room? Which cabinet? Is it near the other three that went down? The answer usually lives in somebody’s head, and that person is on leave.
Nobody can see the whole estate
With ninety locations, “how are we doing?” is a question that takes a morning and a spreadsheet to answer, by which time the answer has changed.
Silence looks like success
Most dashboards show green when nothing is reporting. The one state you most need to know about is the one they are worst at showing.
One descent, eight levels
Nexus is built as a single continuous zoom rather than a set of separate screens. The thing you click at the top is the thing you are standing inside at the bottom, and the state you saw on the globe is the same state you see on the device.
01World
02Country
03State
04City
05Site
06Site Reality
07Digital Twin
08Device
The surfaces
Seven ways of looking at the same estate. Which of them you use depends far more on your job than on your plan.
01
The Command Centre
Every site you run, on one planet, coloured by how it is doing.
Nexus opens on the world. Your sites are points of light on it, and the colour of each one is the honest state of the equipment underneath — teal for healthy, amber for something that needs looking at, red for something failing, and dark for something that has stopped reporting at all.
You do not search for a site. You fly to it. The view descends world to country to state to city, and the same picture carries all the way down, so the thing you clicked at the top of the descent is the thing you are standing in at the bottom.
For a customer with three sites this is a nicety. For one with ninety it is the difference between knowing and hoping.
SCREENSHOT PENDING
The portfolio view: a live estate on the globe, with the country roll-up showing site, camera and device counts.
/portfolio
The portfolio view: a live estate on the globe, with the country roll-up showing site, camera and device counts.
02
Site Reality
The building itself, in its actual street, under its actual weather.
Site Reality is the level where a site stops being a row in a list and becomes a place. The building is rendered in its real surroundings — the streets around it, the approaches, the shape of the block — so that somebody who has never visited can still orient themselves before they ever open a floorplan.
It is also where the outside world is allowed in. Current conditions, the forecast, air quality and local time come from Google's weather and geospatial services; traffic on the approaches comes from HERE. None of it is decoration: when you are deciding whether to send an engineer across a city this afternoon, the fact that it is about to be thirty-nine degrees and the M4 is stopped is part of the decision.
Every site has a Site Reality view from the day it is created, generated from what Nexus knows about it. Enterprise plans layer real Google-derived context over the top.
SCREENSHOT PENDING
Site Reality: the building in context, with live weather, air quality, local time and approach traffic.
/portfolio?site=<siteId>
Site Reality: the building in context, with live weather, air quality, local time and approach traffic.
03
The Digital Twin
The floorplate, with every device on it where it physically is.
Inside the building, Nexus draws the floor: zones, rooms, and every managed device sitting on the spot it actually occupies. Cameras, access control, network equipment, servers, environmental sensors — each one a marker on a plan rather than a hostname in a table.
Health is spatial here, and that changes what you notice. A list of twelve offline devices tells you twelve things are down. A floorplate showing those same twelve devices clustered in one corner of one level tells you a switch or a circuit has gone, which is one thing, and tells you which one.
You can bring your own floorplans. Upload a PDF, PNG or JPG of the real plan, draw the zones over it and place the assets where they belong; from that point the twin is your building rather than an approximation of it.
SCREENSHOT PENDING
The Digital Twin: zones, layers and device markers on a real floorplate, coloured by live health.
/portfolio?site=<siteId>&floor=<floorId>
The Digital Twin: zones, layers and device markers on a real floorplate, coloured by live health.
04
The Rack View
Open a cabinet and see the front of it, rack unit by rack unit.
The descent does not stop at the floor. Select a communications cabinet on the twin and Nexus opens its elevation — the physical front of the rack, drawn to the millimetre from a library of real faceplates, with each piece of equipment in the rack unit it actually occupies.
This is the level where a remote problem becomes an actionable instruction. Instead of telling somebody on site to 'find the switch that's down', you can tell them the cabinet, the rack unit and what the panel in front of them looks like.
It is also the answer to the question every incoming IT manager asks and nobody can ever answer: what is actually in that room?
SCREENSHOT PENDING
The rack elevation: cabinet contents by rack unit, drawn from a millimetre-accurate faceplate library.
The rack elevation: cabinet contents by rack unit, drawn from a millimetre-accurate faceplate library.
05
The Digital Dashboard
The whole site as one readable board, for people who are not looking for a picture.
Not everybody wants to fly a globe. A duty manager at seven in the morning wants one screen that says whether anything needs them, and the Digital Dashboard is that screen: what is under management, what is healthy, what has been offline longest, and what — if anything — needs attention right now.
It breaks the site down the two ways people actually think about it: by area, so you can see that Ward Level 1 is fine and the loading dock is not, and by layer, so you can see that every camera is up but half the access control is not.
When nothing is wrong it says so plainly, which is a deliberate design decision. A board that only ever shows problems teaches people to distrust silence.
SCREENSHOT PENDING
The site status board: everything under management, broken down by area and by equipment layer, with an explicit all-clear.
/sites/<siteId>/board
The site status board: everything under management, broken down by area and by equipment layer, with an explicit all-clear.
06
The Estate Table
Ninety sites, ranked worst first, on one page.
For a multi-site customer the globe is the story and the table is the work. The estate view lists every site you are responsible for, sorted so the thing that needs you most is at the top — by severity first, then by how much of the site is affected.
It is the surface a regional manager lives in: no navigation, no descent, just the list and the ability to jump straight into any site that needs a closer look.
SCREENSHOT PENDING
The estate table: every site ranked by severity and blast radius, with region filtering.
/estate
The estate table: every site ranked by severity and blast radius, with region filtering.
07
Wall Mode
The board, on the screen on the wall, running all day.
Security teams put a screen on a wall and leave it on. Wall mode is the status board reformatted for that screen — larger type, no controls, readable across a room — with an explicit freshness indicator so that a frozen display announces itself rather than quietly showing yesterday.
It is designed around how those screens are actually logged in: a shared read-only account, which is exactly what the Viewer role is for. Enterprise plans add rotation, so one screen can cycle a region rather than showing a single site.
SCREENSHOT PENDING
Wall mode: the board at across-the-room scale, with a live freshness indicator.
/sites/<siteId>/board?wall=1
Wall mode: the board at across-the-room scale, with a live freshness indicator.
What it connects to
Nexus does not replace your stack. It joins what each part of it already knows to the building the whole thing lives in.
NinjaOne
Device inventory, health and telemetry. Nexus syncs the devices NinjaOne manages and joins them to the places they physically sit, so an alert arrives with a floor and a cabinet attached rather than just a hostname.
CrowdStrike
Endpoint protection posture, resold and managed by Alphalogix. Shows which managed endpoints are protected — and, more usefully, which are not.
Dropsuite
Backup protection, resold and managed by Alphalogix. The same question asked of your data rather than your endpoints.
Google geospatial and weather
Building context, places, current conditions, forecast, air quality and local time for each site.
HERE traffic
Live flow on the roads around a site, which is what turns 'someone needs to go there' into 'someone needs to leave now'.
NinjaOne, CrowdStrike, Dropsuite, Google and HERE are trademarks of their respective owners. Nexus is powered by NinjaOne.
Who uses it
Access is scoped by role and by site, so the person on the loading dock and the person running the region see the same truth at different reach.
VIEWER
The screen on the wall
Read-only, scoped to one site. Built for the shared account a control room leaves logged in on a wall display — it can see everything about that site and change nothing about it.
SITE USER
The site operator
Works the twin day to day: layers, device detail, analytics, tag highlighting. Scoped to their own site, and cannot alter its structure.
SITE ADMIN
The site manager
Owns the shape of one site — floors, floorplans, zones, tags and where the assets sit. Does not manage who else gets in.
ORG ADMIN
The regional manager or internal IT
Sees every site in the organisation and controls access to them: inviting people, assigning roles, scoping them to sites, and reading the audit trail.
ORG OWNER
The account owner
Everything an organisation admin can do, plus subscription, billing and ownership transfer. Usually one or two people.
Plans
Three plans, each including everything in the one before it. Features you do not have are absent rather than dangled — no upgrade prompts sitting over the product.
A single site, or a handful.
Foundation
Everything needed to see a site properly: the descent, the twin, the status board, device detail and basic analytics.
INCLUDES
Portfolio Command CentreYour whole estate on the globe, and the descent from world to city.
Geographic NavigationNavigate by country, state and city rather than by searching a list.
Site Reality (Synthetic)Every site gets a Site Reality view from the day it is created.
Digital Twin (View)The floorplate: zones, layers, assets and the floor selector, read-only.
Site Status BoardThe site status board — what is under management, and what needs you.
Device DetailOpen any device for its detail, state and history.
Basic AnalyticsAnalytics on a device across 24 hours to a year.
Multi-site, with a team.
Professional
Adds your own floorplans, editing, tagging, the estate table, wall displays, user management and the audit trail.
ADDS
Upload FloorplansUpload your real floorplans as PDF, PNG or JPG.
Digital Twin Edit ModeDraw your own zones and manage the structure of each floor.
Asset PlacementPlace and move devices to where they physically sit.
TagsTag assets, then highlight or dim the twin by tag.
Estate TableEvery site in one table, ranked worst first.
Wall DisplayWall displays for the control room, readable across a room.
Invite UsersInvite your people into the organisation.
Role AssignmentAssign roles and scope each person to the sites they run.
Audit LogThe audit trail of who was granted what, and when.
A regional or national estate.
Enterprise
Adds live external context, deeper analytics, rotating wall displays, and the security and backup layers Alphalogix manages for you.
ADDS
Rotating Wall DisplayWall displays that rotate a region, resting on whatever needs attention.
Advanced AnalyticsLonger analytics ranges and additional instruments.
Site Reality Place ContextReal-world building and place context layered into Site Reality.
Weather & Traffic ContextLive conditions, forecast, air quality and approach traffic per site.
NinjaOne NormalisationYour NinjaOne devices joined to the places they sit, with their real state.
CrowdStrike Endpoint ProtectionEndpoint protection posture, resold and managed by Alphalogix.
Dropsuite BackupBackup protection, resold and managed by Alphalogix.
Manage IntegrationsConfigure your organisation's integrations yourself.
Pricing depends on sites and devices under management. Alphalogix quotes against your actual estate.
Questions
THE BASICS
What is Nexus, in one sentence?
Nexus is a live, spatial view of everything your organisation runs — every site, every camera, every device — joined to the place it physically sits, from the whole world down to a single rack unit.
Is this a monitoring tool, or a security tool?
Both, and the point is that it refuses to treat them as separate. Your cameras, access control, network equipment, servers and endpoints are all things that live in the same building and fail for the same reasons. Nexus puts them on one picture because a power event in a comms room is simultaneously an IT incident and a security incident, and the two teams currently find out about it in two different systems at two different times.
How is this different from the dashboards my RMM already gives me?
An RMM tells you a device is down. Nexus tells you where it is, what else is near it, what else went down with it, and what the person you send will be looking at when they get there.
The practical difference is diagnosis. Twelve offline devices in a list is twelve problems. The same twelve on a floorplate, clustered around one cabinet, is one problem — and you can see which one.
Does Nexus replace my existing tools?
No, and it is not trying to. NinjaOne stays your RMM, CrowdStrike stays your endpoint protection, your VMS stays your VMS. Nexus is the layer that joins what they each know to the physical world they are all describing, and shows it in one place.
What does 'digital twin' actually mean here?
Something narrower and more useful than the term usually implies. It does not mean a physics simulation of your building. It means a floorplate with your real zones on it and your real devices placed where they really are, showing their real current state.
GETTING STARTED
How long does it take to see our own estate in it?
A site exists in Nexus as soon as it is created, and it has a Site Reality view immediately — generated from what Nexus knows about the address. You will see something on day one.
Getting to a twin you would trust in an incident takes longer, because it means your floorplans, your zones and your devices placed on them. That work is proportional to how many sites you have and how good your existing plans are, and it is the part worth doing properly.
Do we need floorplans?
Not to start. Every site generates a schematic that is clearly labelled as generated, so nobody mistakes it for the real thing. Uploading real plans is a Professional feature, and it is the single biggest upgrade in usefulness the product has.
What formats can we upload?
PDF, PNG and JPG. You then draw zones over the plan and place assets on it.
We have ninety locations. Is this going to be ninety manual builds?
The device side is not manual: sites and devices come in from NinjaOne rather than being typed. The spatial side — plans, zones, placement — is per site, and is the honest cost of the product being spatial at all.
In practice estates roll out in waves, usually starting with the sites that generate the most callouts, because those are where the payback is fastest.
ACCESS AND SECURITY
How do people sign in?
Customers sign in with their work email and a six-digit code. There is no password, which means there is no password to reuse, phish, leak or reset.
Staff and organisations with their own identity provider sign in through SSO instead.
There is no 'forgot password' link. Is that a bug?
It is the design. There are no passwords in the customer sign-in path, so there is nothing to forget and nothing for an attacker to reset. Access to your email is access to Nexus, which is the same trust boundary your single sign-on already runs on.
Can we restrict people to a single site?
Yes, and it is the normal case. Roles are scoped: a site operator or site manager sees their own site and nothing else, while organisation admins see the whole estate. One person can hold different roles at different sites.
What about the screen we leave logged in on the wall?
That is what the Viewer role exists for: read-only, scoped to one site, safe to leave on a shared account because it cannot change anything.
It is still a session, so it still times out on inactivity — a display left on a wall for a year is exactly the credential nobody thinks about until it matters.
Is there an audit trail?
Yes, from Professional upwards. It records the things an auditor and an incident review both ask about: who was invited into the organisation, who granted them access, what role and which sites they were scoped to, and when any of that changed.
It is visible to organisation admins and owners rather than to site-level roles, on the same principle as everything else — you can see the governance of the estate you are responsible for, and not somebody else's.
Where does our data live?
Nexus runs on Microsoft Azure. Alphalogix can confirm region and retention specifics for your organisation as part of a procurement conversation, including backup retention and recovery objectives.
WHAT IT SHOWS, AND HOW HONESTLY
If a device stops reporting, does it show as healthy?
No. This is close to a founding rule of the product: nothing is ever green because we did not hear anything. A device that has stopped reporting is drawn dark and counted as offline, and a site with no data says so instead of showing a comfortable zero.
What do the colours mean?
Teal is healthy. Amber needs attention. Red is failing. Dark grey means the thing has stopped reporting and we do not know. Blue is only ever selection — it never means a state.
Is anything on the screens made up?
Generated content exists in two places and both announce themselves. A site without uploaded plans gets a schematic labelled as a Nexus-generated demonstration schematic. Demonstration environments carry a synthetic-data badge on every surface that shows figures.
Real device state is never generated. If Nexus does not know, it says it does not know.
How current is what I am looking at?
Device state comes from your management stack as it arrives. Weather, air quality and traffic are pulled per site and cached briefly, because those services bill per call and a page that re-fetched the forecast on every mouse move would be expensive and no more accurate.
Wall displays carry an explicit freshness indicator so a stalled screen shows as stalled instead of quietly displaying yesterday.
PLANS AND COMMERCIALS
How are the plans structured?
Three: Foundation, Professional and Enterprise, each including everything below it. Broadly — Foundation is seeing a site properly, Professional is making it yours and running a team on it, Enterprise is running an estate with live external context and managed security layers.
What happens if we are on a lower plan and open something we do not have?
It is not there. Features you do not have are absent rather than displayed with an upgrade prompt over them — a product that constantly advertises what you have not bought is tiring to use, and it also leaks what other customers are doing.
Are CrowdStrike and Dropsuite included?
They are resold and managed by Alphalogix and appear in Nexus on Enterprise. Whether they are the right fit is a conversation about your existing contracts, not a checkbox.
What does it cost?
Pricing depends on the number of sites and devices under management and which plan fits. Alphalogix will quote against your actual estate rather than a list price that would be wrong for almost everybody.
THE ROAD AHEAD
What is coming next?
The near-term work is depth rather than breadth: richer analytics, more of the estate reachable without leaving the board, and tighter ticketing so an alert becomes a job without being retyped.
Alphalogix will talk openly about the roadmap in a demo, including what is not built yet. Anything described on this page is something the product does today.
Can Nexus integrate with something we already run that is not listed?
Possibly, and it is worth asking. The joining model — devices, places and events sharing one spatial index — is deliberately not specific to any one vendor.
See it against your own estate
A demonstration environment is a nice picture. A walkthrough using your sites, your devices and your floorplans is a decision. Alphalogix will do the second one.
