Exploit availability
Public capability
Example row showing how proof-of-concept, module, or detection artifacts would be separated from exploitation evidence.
artifact typesource qualityfirst-seen window
Platform
Prepared for secure authenticated intelligence workflows
Phase 1 establishes the shell, navigation, locked states, empty states, loading states, and error states without connecting private intelligence data.
Pulse
Intelligence command center
Designed to show current priority, recent activity, observed exploitation, exploit availability, Early Alerts, emerging clusters, watch signals, IOC movement, and vendor/product movement.
Limited preview
No private API connection
Live intelligence preview
A bounded presentation state showing the intelligence categories Hidden Intel can surface after authenticated access is connected.
browser → authenticated server layer → product API
LatestHotEmergingZero-daysExploitedEarly signals
Observed exploitation
Authority-backed
Example row for exploitation evidence such as canonical exploited-in-the-wild reporting or KEV-style authority signals.
confirmed sourceaffected producttimeline
Early Alert
Pre-canonical signal
Example row for security activity that may form before a complete CVE record exists.
velocitycorroborationnovelty
Locked by entitlement
Premium feeds, API access, and custom webhooks show upgrade states instead of failing silently.
No exposure selected
Customer assets are sensitive and are not represented with fabricated inventory in this phase.
Loading state
Connection unavailable
A production integration error should preserve context and provide a safe retry path.
Why this appears
source qualitycorroborationvelocityrelevance
Do not merge
exploit availabilityobserved exploitationzero-day statuswatch state
Action states
monitortriagebriefpolicy alert
Platform
Designed for a secure commercial deployment
Phase 1 establishes the product surface while leaving production APIs, authentication, billing, and entitlements for later server-side integration.
Server-side API boundary
Permanent product API credentials and sync secrets must stay out of browser code, HTML, storage, logs, and source maps.
Organization-scoped SaaS state
Authenticated customer state is designed around organizations, membership, profiles, billing mirrors, and default-deny access.
Entitlement-aware UX
Available, locked, upgrade-required, trialing, active, past-due, suspended, and canceled states are represented without relying only on hidden navigation.
Future billing integration
Checkout, billing portal, subscription lifecycle, and entitlement synchronization are reserved for the billing phase.