Pilot sandbox workspace
What a customer can inspect before real data is connected
This page is a public-safe preview of the controlled pilot workspace. It shows the structure of a Raven pilot tenant without customer data, production login, live collectors or external write.
Tenant synthetic
Data no customer data
Runtime preview only
Workspace Surface
IncidentsCandidate incident timeline, critical point, decision window, affected service and current human decision state.
Decision packetsProblem, evidence, options, Raven recommendation, Mira cost frame, unknowns and human approval boundary.
TechniciansAvailable team, thinking state, accept or decline, ETA, repair estimate, field note and completion state.
ReportsIncident, executive, daily, weekly, post-incident and review reports grouped by package and environment type.
AuditWho saw what, what was known, what was estimated, what was assumed, what remained unknown and who approved.
Role Views
OwnerBusiness outcome, pilot value, credit state, package fit, executive reports and production decision boundary.
NOC ManagerIncident, evidence, technician flow, operational recommendation and dispatch decision.
CISOData boundary, tenant separation, audit trail, access model, retention and activation gates.
ProcurementPilot scope, commercial boundary, SLA dependency, support model, DPA path and package evidence.
30-Day Pilot Workspace Path
Week 1Briefing, scope, success criteria, data class, security contact and decision owner.
Week 2Historical, synthetic, anonymized or read-only approved evidence review. No live write access.
Week 3Decision packets, report repository, technician workflow and package fit review.
Week 4Executive pilot report: observed value, limitations, confidence, unknowns and production readiness gaps.
What Is Not Active Here
No accountThis preview does not create a customer account, session, tenant, cookie or production login.
No backend writeNo database, audit writer, payment provider, mail provider, collector or external API is called from this page.
No customer dataNo logs, exports, credentials, VPN access, GPS location or operational files are requested.
No activationProduction activation requires identity, MFA, tenant binding, audit writer, support scope, legal boundary and owner approval.