ComplianceAide Platform Overview

A clear walkthrough of ComplianceAide from public trial to workspace, evidence capture, assessment, dashboards, reports, policies, and MSP workshop follow-up.

Platform Overview

ComplianceAide turns evidence into assessments, dashboards, and action plans.

Start from the public trial page, open a guided workspace, upload or capture evidence, run a framework assessment, and generate the outputs an MSP or security team needs to move work forward.

Start trial Evidence workshop Return to home
1
TrialCompany name and work email create the secure starting point.
2
WorkspaceScope note and customer context shape the AI assistance.
3
EvidenceUpload files or capture visible screens with Eyes.
4
AssessmentMap evidence to frameworks and identify gaps.
5
OutputsGenerate dashboards, reports, policies, and action plans.

1. Start from the public trial page

The fastest entry point is ai.complianceaideai.com/trial. A new user chooses the setup, enters a company name and work email, and receives a secure sign-in link.

  • No implementation project is required to start.
  • MSPs can begin with their own internal workspace or a customer workspace.
  • The first useful outcome is evidence organization, not a perfect compliance score.
ComplianceAide public trial page with company and work email fields
The public trial flow begins with company name and work email, then uses a secure sign-in link.
ComplianceAide create workspace form with scope note
A scope note gives the assistant the business context before evidence is uploaded.

2. Create a workspace with real scope

Each workspace should map to a client, business unit, assessment project, or focused initiative. The scope note is the first place to say what the team is trying to assess.

Customer: Example Manufacturing Goal: run a NIST CSF 2.0 readiness assessment from a small evidence packet. Include: policies, asset inventory, identity/MFA exports, vulnerability summary, backups, tickets, and screenshots captured with Eyes. Treat missing evidence as a gap, not as compliance.

3. Let the Guide keep the user moving

The Guide keeps the workflow readable. It surfaces status, next actions, and useful shortcuts while evidence is being reviewed or an assessment is running.

  • Ask the assistant what to do next.
  • Use Guide actions for status, policy generation, summaries, and follow-up.
  • Keep the workspace open while long-running work completes.
ComplianceAide Guide card with next actions
The Guide reduces the need to memorize the product. It tells the user where to go next.
ComplianceAide paperclip upload control and evidence count
The paperclip is the evidence entry point. The count and warning badge tell the user what needs attention.

4. Upload evidence before running the assessment

ComplianceAide works best when the user gives it evidence first: policies, spreadsheets, exports, screenshots, diagrams, backup status, tickets, and identity or endpoint data.

  • Upload individual files rather than expecting compressed archives to be parsed automatically.
  • Read unsupported-file warnings before running the assessment.
  • Ask the assistant to summarize what the evidence proves and what is still missing.

5. Use Eyes when evidence is visual

Some evidence lives in a dashboard, remote tool, CSV viewer, VDI session, or screenshot. Eyes lets the user capture what is visible and turn it into workspace context.

  • Open the evidence on screen.
  • Click Eyes, Start, choose the screen or window, then stop after capture.
  • Ask the assistant to summarize what Eyes saw before relying on it in the assessment.
ComplianceAide Eyes control and Shoulder Coach panel
Eyes is a practical path for evidence that is visible but not easy to export cleanly.
ComplianceAide assessment preview with executive summary and gaps
Assessments convert evidence into framework-specific readiness, gaps, and next actions.

6. Run the framework assessment

Pick the framework that matches the customer conversation. For many MSP readiness sessions, NIST CSF 2.0 is a good first pass because it produces broad security-program coverage without over-specializing too early.

  • Large assessments can take 15-40 minutes depending on evidence and framework size.
  • Use partial previews carefully while the full result finishes.
  • Turn top gaps into owners, dates, and evidence requests.

7. Generate visual outputs and customer-ready follow-up

After evidence is in the workspace, ComplianceAide can create dashboards, summaries, reports, policies, and remediation plans that make the findings easier to discuss.

DashboardsNetwork diagrams, readiness maps, asset views, identity maps.
ReportsExecutive summaries, evidence checklists, gap lists, next actions.
PoliciesDraft policies and runbooks grounded in workspace context.
ComplianceAide security dashboard gallery
Dashboards help translate assessment work into a visual customer conversation.

Need a hands-on version?

The evidence-to-assessment workshop is the companion exercise: it gives MSPs a fictional evidence pack and a 60-minute runbook for practicing this flow.

Open workshop

When to use this page vs. the workshop

Use this overviewFor a first conversation, website menu item, or broad product walk-through.
Use the workshopFor a live MSP enablement session where attendees actually upload evidence and run a test assessment.
Use both togetherSend the overview before a meeting and the workshop after the demo as the hands-on follow-up.