Deployment without premature activation
Deployment Models
Different organizations require different levels of access. Raven should start with the least invasive model that can prove or disprove decision exposure.
Principle least invasive first
Production separate gate
Access approved only
Available Models
Public-safe briefingNo customer data. Used to understand category, findings, boundaries and pilot process.
Offline reviewCSV, XLSX, JSON, logs or incident exports can be reviewed without live access after legal/data approval.
Replay pilotHistorical events are replayed to test whether Raven would have identified a decision window.
Read-only pilotApproved read-only sources can be used when security, tenant and audit boundaries are accepted.
Production modeProduction integration is allowed only after scope, security, rollback, tenant, support, audit and owner activation gates.
Enterprise Variants
Cloud-assistedSuitable when approved by the customer security process and data boundary.
On-premiseA possible deployment direction for controlled environments after architecture review.
Air-gappedA separate enterprise model requiring offline packaging, update, support and evidence-transfer design.
HybridOften suitable for pilots: public-safe website, offline evidence, read-only validation and human-approved reports.
Database And Migration Boundary
Draft schemaSchema drafts are not migrations. They cannot be applied until promoted, reviewed, versioned and reversible.
Promotion gateMigration promotion requires owner approval, rollback plan, backup/restore proof, schema review, tenant review, audit reference and synthetic test proof.
Production gateProduction migration requires a separate production runbook and remains blocked until the customer owner and Raven owner approve execution.
No live database hereThe public website does not connect to a customer database, run migrations, apply schema changes or persist customer operational data.