Structured from the first field.
Justification, controls, evidence, attestation, and ownership context stay connected.
Product preview · Active development
Vulnerability exceptions,governed with intent.
VEXA brings requests, evidence, approvals, ownership, lifecycle enforcement, and auditability into one controlled governance layer.
- 01Controlled workflow
- 02Server-side authorization
- 03Auditable lifecycle
Governance record
Lifecycle enforced
Created by VueLogic Studio, LLCVulnerability Exception Management
What VEXA solves
One governance record.
Not six disconnected systems.
Vulnerability exceptions often move through forms, inboxes, spreadsheets, evidence files, approval threads, and expiration calendars. VEXA connects that process without pretending to be the vulnerability scanner.
Request formsIntake
Email threadsReview
SpreadsheetsTracking
Evidence filesContext
ApprovalsDecisions
CalendarsExpiration
Governance layer
Request · Review · Approval
Ownership · Evidence · Lifecycle
Governance in VEXA≠VM platform implementation
Exception lifecycle
A controlled path from
request to closure.
Every primary state has a clear purpose. Denied and cancelled requests branch cleanly without disrupting the governed lifecycle.
01SubmittedRequest entered
02In ReviewVM assessment
03ApprovedGovernance decision
04ActiveException in force
05ExpiredApproved period ended
06ClosedLifecycle complete
DDeniedReturned during review or approval
CCancelledWithdrawn or ended before completion
Governance & workflow
Keep every decision
explicit.
VEXA separates authentication, authorization, ownership, internal approval, exception lifecycle, and VM implementation—because those are different governance concepts.
Request→Review→Decision→Implementation
Review. Return. Resubmit.
Revision is part of the workflow—not an email side channel.
Internal approval stays distinct.
A governance requirement, never a lifecycle shortcut.
Track follow-through separately.
Approval does not imply the exception already exists in the VM platform.
Users, teams & RBAC
Authorization built around
real operating roles.
Users, teams, roles, permissions, and exception ownership remain separate. Authorization is designed to be enforced server-side.
UUsers→
TTeams→
RRoles→
PPermissions→
OOwnership
Requester
VM Engineer
VM Manager
Administrator
Viewer / Auditor
Executive
Accountability & evidence
Audit TrailAppend-oriented events
The record should explain
what happened.
Important workflow changes, approval activity, administrative actions, and security-relevant events are designed to remain attributable.
- 01Lifecycle historyState changes and disposition
- 02Approval activityDecisions and accountability
- 03Administrative eventsSecurity-relevant changes
- 04Evidence handlingControlled uploads with malware scanning
Inside VEXA
Clarity for every
operating perspective.
Executive visibility, daily workspace operations, exception detail, and secure administration live in one browser-based product.
Designed export capabilities
PDFExcelCSVJSONPrint
Subject to role-based access controlVEXA Health
Operational visibility
into the platform itself.
VEXA Health is designed to surface the condition of critical services without exposing unnecessary implementation detail in routine views.
VEXAHealthOperational visibility
ApplicationService visibility
PostgreSQLDatabase health
StorageCapacity & evidence
BackupsRecovery posture
AuthenticationIdentity services
TLSTransport security
Malware scanningEvidence inspection
Recovery / keysContinuity health
Security & recovery
Security is part of the
architecture.
VEXA is being designed around defense in depth, least privilege, secure authentication, MFA capability, encryption, server-side authorization, controlled evidence handling, auditing, and recovery.
Identity
Authentication · MFA capability · authorization
Data
PostgreSQL · integrity protections · evidence controls
Audit
Lifecycle history · security-relevant events
Recovery
Backups · verification · Recovery Kit architecture
Browser-based applicationPostgreSQL operational databaseMulti-user designConcurrency & integrity protectionsDesigned for Windows-native deploymentCross-platform portability requirement
The right boundary
VEXA governs the exception.
Your VM platform manages the finding.
Tenable, Qualys, Wiz, and similar tools remain the systems that surface and manage findings.
+
Requests, review, approvals, evidence, ownership, lifecycle, implementation tracking, and accountability.
No partnership or direct platform integration is implied.
Coming soon
Govern vulnerability
exceptions with intent.
VEXA is currently in active development by VueLogic Studio, LLC.
Register your interest No release date or pricing has been announced.Register your interest
Start a conversation
about VEXA.
Tell VueLogic Studio what you would like to explore—product previews, deployment conversations, or future availability.