01 / HEALTH & DEVICE CONTEXT
The endpoint, at a glance.
See health, critical findings, device details and management status together. Keep each computer in its own workspace, with a clear next step when something needs attention.
Explore the workspace
PRODUCT PREVIEWS SAMPLE DATA
02 / FINDINGS & RECOMMENDATIONS
Find the cause behind the finding.
Move from a flagged issue to its diagnosis and recommended action. Review the evidence, follow related findings and copy a report to keep the support conversation clear.
03 / SAVED SNAPSHOTS & PATTERNS
See the pattern across computers.
Bring saved computer snapshots together to spot common findings, unusual issues and the endpoints that need attention first. Compare the fleet overview in light and dark themes.
04 / SYSTEM & MANAGEMENT PANELS
Familiar tools. The same workspace.
Inspect software, processes, events, updates, network settings and hardware without losing the endpoint you are working on. Open Software Center and Company Portal alongside the system panels.
05 / COMMANDS, OUTPUT & HISTORY
Know what runs. See what happened.
Browse support actions by category, inspect the command and follow its output. Read-only checks are distinguished from changes to the endpoint, with the execution record kept in Logs & history.
06 / POWERSHELL & CMD
Room for the command line.
Use PowerShell or CMD when an investigation needs a closer look. Choose SYSTEM or logged-on user context, review the target and keep a record of the commands and their output.
Illustrative product previews with fictional data. The development build may differ. Open any preview to explore all seven images.
THE GAP VERITY CLOSES
Two answers to the same question.
Software Center is stuck. The last inventory and a direct check of the computer can tell different stories.
Management console
Example inventory from 41 hours ago
- Client
- Active
- Client version
- 5.00.9122.1000
- Last policy request
- 2 days ago
- Deployments
- 3 in progress
- Free space C:
- Not collected
Verity
Example findings from a new analysis
- CcmExec
- Stopped
- root\ccm
- Invalid namespace
- ccmsetup exit code
- 0x80004005
- BITS jobs
- 4 in TransientError
- Free space C:
- 6 GB of 476 GB
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 DATAHOW IT REACHES THE ENDPOINT
Three mechanisms. No dedicated agent.
WinRM, with your credentials.
Diagnostics use a remote PowerShell session to read the endpoint directly. Inspect client health, policies, deployments and Windows system state.
SYSTEM, through a scheduled task.
Actions that need machine rights can run in SYSTEM context through a temporary scheduled task. Inspect the command and its impact before running it.
A record of the work.
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
Six sections.
All the context.
Open several computers as independent tabs. Each keeps its own diagnosis, tools and results.
Verdict and snapshot.
A health score, severity counts and a snapshot of the system, user, hardware, management and network.
Findings and fix plans.
Filter by severity, review the evidence and recommendation, then open the tool linked to the finding.
The system, in detail.
Software, events, processes, printers, drivers, disks, network settings, Windows Update and management panels.
Checks and repair commands.
Support actions grouped by area, including SCCM, Intune, WMI, Office and networking. Commands that change state are marked.
A command line on the endpoint.
PowerShell or CMD in SYSTEM or logged-on user context, with execution output and history in the same workspace.
What happened, in order.
Keep analyses, operations and saved snapshots. Organise cases and export reports so the investigation can continue.
LOCAL ROOT-CAUSE ANALYSIS
Connect the findings.
Understand the fault.
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
An isolated issue,
or a recurring pattern?
The fleet overview brings saved computer snapshots together. See which findings recur and which endpoints need attention first.
Explore fleet healthHealth distribution
Group snapshots into healthy, watch and critical bands.
Common findings
See the issues that appear across multiple computers.
Outliers first
Spot unusual findings and computers below the fleet average.
DEPLOYMENT
What it needs.
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.
- Your workstation
- 64-bit Windows, .NET Framework 4.8 and administrator rights. Run the application with its supplied dependencies.
- The endpoint
- WinRM enabled and reachable, with the permissions required for the selected operation. No dedicated Verity agent.
- Credentials
- Use your Windows identity or a credential profile. Saved profile passwords are encrypted with Windows DPAPI for the current Windows user.
- Configuration
- The first successful ConfigMgr analysis can fill empty site-code and management-point settings. Repair source paths and optional provider settings are configured separately.
- Analysis & records
- Root-cause correlation runs locally. Saved snapshots, cases and operation history stay with the operator's workspace.
PRODUCT STATUS
Built in support.
Preparing for what comes next.
Version 0.95.0 — in development
Verity grew out of an internal support tool. It is now being prepared for commercial release, with work on configuration across different environments, interface translations and validation.
A public release date has not been announced.
BLACKPILLAR LABS / CONTACT
Let’s talk about Verity.
We are looking for companies interested in testing Verity and working with us on pilot deployments. Get in touch to discuss your environment or arrange a demo.
Explore the pilot programme