You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aperio's UI is built for security analysts and operators. Two crucial audiences are unserved:
CISO ↔ board / executive team — needs monthly/quarterly digestible posture reports with trends, narratives, and "what we did". The operator console is the wrong surface for this.
Customer-facing security communications — every B2B buyer asks vendors for a Trust Center page ("show me your SOC 2 controls, your incident posture, your subprocessor list"). Today Aperio doesn't help its customers publish this; they hand-roll it elsewhere.
Both surfaces read from the same underlying posture data — they're presentation layers. Building both turns Aperio from a cost-center tool into a tool that executives can show offandsales teams can hand out.
Goals
Executive reports — auto-generated, narrative-rich PDF (and HTML email) reports, scheduled or on-demand, with KPIs + trends + summarized findings.
Custom KPI builder — operators define a few org-specific KPIs (mean time to remediate, MFA coverage, % findings in SLA, etc.) tracked over time.
Public Trust Center pages — customer-facing posture summary publishable at trust.<customer-domain> or hosted by Aperio at trust.aperio.io/<slug>.
Subprocessor + compliance list — first-class management of the artifacts buyers ask about.
Not building a full BI / dashboarding tool — KPIs are pre-defined templates with operator configurability, not a custom query builder.
Not white-labeling Aperio's product UI — the Trust Center is a separate, deliberately simplified surface.
Not handling customer security questionnaires (Vanta Trust, SafeBase territory) in v1 — Trust Center is read-only public posture, not response automation.
Proposed design
Executive report architecture
A new background job runs on the configured cadence per ExecutiveReportSubscription row:
Gather inputs for the period:
Findings opened, closed, current state (by severity).
The published Trust Center surface is its own Next.js route group (apps/web/app/trust/[slug]/) served separately from the operator console (no auth required for PUBLIC; signed URL for PRIVATE_LINK). Sections operators can toggle:
Problem
Aperio's UI is built for security analysts and operators. Two crucial audiences are unserved:
Both surfaces read from the same underlying posture data — they're presentation layers. Building both turns Aperio from a cost-center tool into a tool that executives can show off and sales teams can hand out.
Goals
trust.<customer-domain>or hosted by Aperio attrust.aperio.io/<slug>.Non-goals
Proposed design
Executive report architecture
A new background job runs on the configured cadence per
ExecutiveReportSubscriptionrow:chromiumheadless /weasyprint).ExecutiveReportartifact + deliver via Resend email or Slack.Trust Center
The published Trust Center surface is its own Next.js route group (
apps/web/app/trust/[slug]/) served separately from the operator console (no auth required forPUBLIC; signed URL forPRIVATE_LINK). Sections operators can toggle:#16baseline scores +#5framework scorecards)KPI templates
Ship built-in templates the operator can enable:
Each KPI is a small SQL/RPC + formatter that produces
{value, trend, baseline_label}.Phasing
/admin/reportsUIOpen questions
References
Organization, Resend email transport,RoleNamefor access control,SecurityFindingaggregates.