VERSION 0.99.6 03 OCT 2026
01 / HEALTH & DEVICE CONTEXT
See device details, health indicators and priority findings together. Check the system, user and management context, then use the recommended next steps to decide where to investigate first.
02 / FINDINGS & RECOMMENDATIONS
Filter findings by severity and category, then inspect the evidence and recommendation behind each one. Built-in rules connect related signals into likely causes and practical next steps. Application and update states help you investigate stalled deployments.
03 / SAVED SNAPSHOTS & PATTERNS
Compare saved endpoint snapshots to spot recurring findings, health differences and computers that need attention first. Use the snapshot dates to put each result in context. Fleet health summarises saved analyses; it is not continuous monitoring.
04 / SYSTEM & MANAGEMENT PANELS
Inspect the selected endpoint through Task Manager-style process views and grouped Windows panels, without opening those windows on the user’s desktop. Investigate Software Center and Company Portal alongside system details. When Software Center cannot retrieve part of its data, available results remain visible and the missing data is identified.
05 / PROCESSES & OWNERSHIP
Inspect the full returned process list with owners, session IDs, CPU and memory working set. Filter by user and session, or group related processes while keeping different users separate. Sample times and unavailable values make the limits of each reading clear.
06 / USERS & SESSIONS
View Windows user sessions, including active and disconnected states, with process counts and available CPU and memory totals. Inspect session data without taking over the desktop. The Users view does not sign anyone out or disconnect their session.
07 / COMMANDS, OUTPUT & HISTORY
Choose a diagnostic check or repair tool, inspect its command and execution context, then review the recorded output. State-changing actions are labelled, and stable tool identifiers make it easier to refer to the same operation in a support case.
08 / POWERSHELL & CMD
Run PowerShell or CMD on the endpoint as SYSTEM, or in an available logged-on user session. Keep the target, execution context and output in view while you work. The screenshot contains a fictional demonstration transcript; no remote command was run for this capture.
These screenshots show the Verity 0.99.6 development interface, captured on 3 October 2026 with fictional demo data. Computer names, users, servers and domains are invented. The Task Manager previews use fictional processes and sessions; no endpoint was queried for these captures. Open any screenshot to browse all eight views, then choose Actual size to read the details.
THE GAP VERITY CLOSES
Software Center is stuck. The last inventory and a direct check of the computer can tell different stories.
Example inventory from 41 hours ago
Example findings from a new analysis
A failed client may stop reporting before the management database reflects the problem. A direct check gives the engineer another source of evidence.
ILLUSTRATIVE SUPPORT CASE · FICTIONAL DATASUPPORT IN THE BACKGROUND
Check the endpoint and perform supported repairs without taking over the screen or asking the user to leave their session. Verity brings remote Windows data into familiar support views on the engineer’s workstation.
Routine checks and many support actions run in the background. Actions that restart a service, close an application or reboot the computer can interrupt work, so review their impact before running them.
Diagnostics use a remote PowerShell session to read the endpoint directly. Inspect client health, policies, deployments and Windows system state.
Actions that need machine rights can run in SYSTEM context through a temporary scheduled task. Inspect the command and its impact before running it.
Keep the command, target, execution context and output alongside the investigation. Review the history and export the evidence for the next engineer.
ONE WORKSPACE PER COMPUTER
Open several computers as independent tabs. Each keeps its own diagnosis, tools and results.
A health score, severity counts and a snapshot of the system, user, hardware, management and processes, with recently viewed computers and next steps
Review findings by severity, inspect their evidence and recommendations, and follow the client’s application and update states.
Software, events, processes, printers, drivers, disks, network settings, Windows Update and management panels
Checks and repairs grouped by area, with stable identifiers, state-change labels and a preview of the command before it runs
PowerShell or CMD as SYSTEM or in an available logged-on user session, with execution output and history in the same workspace
Keep analyses, operations and saved snapshots. Organise cases and export reports so the investigation can continue.
LOCAL ROOT-CAUSE ANALYSIS
A stopped service, a missing WMI namespace and a failed installer can be symptoms of the same problem.
Verity correlates findings across categories and proposes ranked root-cause hypotheses, each with supporting evidence and a fix plan. The deterministic rule engine runs locally, without an AI service.
Rules use stable finding codes, keeping the correlations independent of the interface language.
Explore the diagnosis viewACROSS THE FLEET
The fleet overview brings saved computer snapshots together. See which findings recur and which endpoints need attention first.
Explore fleet healthGroup snapshots into healthy, watch and critical bands.
See the issues that appear across multiple computers.
Spot unusual findings and computers below the fleet average.
DEPLOYMENT
A native Windows application that fits into your existing remoting environment
SCCM / ConfigMgr, Microsoft Intune and co-managed devices
Interface options: English, Polish and German
PRODUCT STATUS
Version 0.99.6 — in development
Built by Łukasz Stańczyk from day-to-day endpoint support experience. Verity is in active development, with current work focused on reliable diagnostics, controlled repairs and validation across different environments.
We are inviting IT support teams to a 30-day pilot: evaluate Verity in your environment, bring real support cases and help shape the next release.
BLACKPILLAR LABS / CONTACT
Supporting Windows devices with SCCM, Intune or co-management? Tell us about your environment and the incidents your team handles. We can discuss a demo or a 30-day pilot with a scope agreed together.
Apply for a 30-day pilot