Enterprise procurement
The first due diligence answers in one place
This pack exists for procurement, legal, CISO, architecture and pilot sponsors who need a clear path before a briefing. It is public-safe and intentionally does not claim certifications, outcomes or production access that have not been separately approved.
Audience procurement / legal / CISO / CTO
Mode public-safe due diligence
Purpose reduce enterprise friction
What Happens After Request Briefing
1. QualificationRaven confirms the environment, role, operational problem, data sensitivity and whether the request belongs in research, review, pilot or production discussion.
2. BoundaryThe customer receives a security, data and decision-boundary checklist before any operational data, account, connector or payment activation is requested.
3. Pilot pathA Pilot in 30 days can be scoped around historical, synthetic, anonymized or read-only evidence, with named success criteria and limitations.
4. ApprovalCommercial, legal, security, support and owner approval gates must be completed before production activation.
Procurement Checklist
Legal packTerms, Privacy, DPA path, retention, deletion, responsibility boundary and support scope must be reviewed before customer data processing.
Security packSecurity Overview, data boundary, audit trail, tenant isolation design, least privilege, sensitive credentials handling, incident response and rollback expectations.
Commercial packScope, package, billing model, credits, tax, payment terms, acceptance criteria and the condition that payment alone never activates production.
Delivery packPilot plan, data mode, support hours, escalation route, named owner, evidence labels and final pilot report format.
Support / SLASupport targets, severity classes, escalation route and any SLA language must be explicitly agreed before pilot activation or production use.
Public Control Map
Briefing requestCreates interest only. It does not create an account, activate a tenant, start a connector or send customer data into Raven.
Pilot intakeRequires scope, data class, DPA path, retention, file hash, malware scan state and human approval before processing.
Customer data room manifestBefore any customer data room opens, required, optional and excluded data classes, formats, size limits, retention, transfer channel and personal-data gates must be agreed. The public site does not open rooms or accept files.
Retention and deletion policyRetention category, retention days, deletion owner, deletion verification plan, DPA state, personal-data gate and legal-hold boundary must be explicit before intake. Public pages never execute deletion.
Pilot agreement acceptanceResearch review, free limited pilot and paid pilot paths require signed scope, DPA boundary, data boundary, support scope, rollback, human approval, legal review and owner review before activation.
Pilot activation release gateEven when a pilot is release-ready, activation, channel opening, upload, account creation, payment capture and notification require a separate executor release. Readiness is not activation.
Security reviewTenant isolation, RBAC, audit, rate limits, redaction, backup/restore and owner review are treated as activation gates, not marketing claims.
Admin Review QueueFuture review visibility can prioritize critical open gates and show required approver role, tenant scope, object reference, reason, audit reference and next action. It does not approve, assign, notify, read a database or load customer data.
API request envelopeFuture API requests require registered endpoint id, method match, auth context, tenant scope, allowed role, audit reference, idempotency where required, rate-limit reference and provider signature where required. No public page starts a listener.
API runtime guard stackBefore API activation, Raven must also verify endpoint release approval, closed runtime blockers, RBAC permission, rate-limit result, idempotency result and safe error mapping. Passing the guard does not execute the endpoint.
Customer portal sessionPortal session readiness requires account activation reference, auth context, owner approval, audit reference, CSRF reference, bounded TTL, identity verification, MFA, tenant scope, RBAC, terms acceptance and DPA readiness before release.
Customer activation release gateCustomer access release requires account activation readiness, approved customer-activation review, owner or admin release, audit reference, rollback reference and support scope. It creates no account from this public page.
No customer activation runtimeThe public site does not create accounts, create sessions, open tenant runtime, write a database, call providers or send activation notifications.
No portal runtimeThe public site does not create portal sessions, set cookies, call external auth, open tenant runtime or write a customer session database record.
Portal module entitlementCustomer modules require package depth, RBAC permission, portal-session-ready reference, audit reference and owner approval before release. Write-capable modules require write authority, and audit export requires export authority.
No module runtimeNo customer module is loaded, no tenant data is read, no write action is performed, no tenant runtime is opened and no external export is created from the public page.
Workspace read modelCustomer workspace visibility requires approved module snapshots, approved data mode, portal-session-ready reference, data snapshot reference, module entitlement references, audit reference and owner approval before release.
No workspace data fetchThe public site does not render a customer workspace, read a database, start live queries, open tenant runtime or load customer data.
Workspace export gateReport, dossier, audit, CSV, XLSX, JSON or PDF release requires approved export scope, approved format, held delivery mode, audit reference, owner approval, export authority, retention policy for non-synthetic data and DPA/redaction gates when personal data is present.
No export runtimeThe public site does not write files, create external exports, enable downloads, send notifications, read a database, load customer data or start delivery.
sensitive credentialssensitive credential values are never collected by the public website. Runtime binding requires reference-only records, approved storage, owner, rotation, emergency revoke and audit gate.
Quote approvalCommercial quote readiness requires scope, legal review, tax review, owner approval, valid-until date, audit reference and evidence-backed quote lines before customer send, checkout, invoice or activation.
Payments and creditsCheckout and credits require webhook verification, idempotency, ledger reconciliation, provider signature verification, event allowlist, payload-hash conflict handling and human activation before customer service starts. Provider event review uses provider signature verification, event allowlist, idempotency, payload-hash conflict handling and owner review for conflicts.
Credit ledger persistenceProvider-backed credit ledger entries require provider event readiness, idempotency, owner approval and owner release gate before persistence. A prepared ledger entry is not a persisted credit balance and does not make credits available.
Credit package catalogCredit package catalog is planning-only: 100, 200, 500 and 1000 Raven Decision Credits at EUR 15 net planning unit before quote-specific owner release and tax review. It does not create provider prices or checkout sessions.
Balance read modelCredit balance visibility requires tenant scope, account scope, credits:read permission and ledger_payload_hash_conflict handling. Available balance only counts ledger_entry_persisted_verified entries; pending credits are not usable credits.
Billing portalBilling portal readiness requires finance, owner or admin authorization, allowed portal scope, relative return path, owner approval and audit reference before any provider portal session can be created.
Invoice artifactsInvoice previews require finance, owner or admin authorization, reviewed currency and tax mode, line-item evidence, owner approval and audit reference. Public pages do not issue legal invoices or tax submissions.
Outbound mailTransactional mail remains held until registered template, suppression list, provider verification, bounce handling, dead-letter path and human release approval gates are closed. The mail boundary requires provider event ledger handling, bounce handling, dead-letter path and owner review before delivery, complaint or inbound status changes can inform recovery review. Public pages do not upload recipients, enable tracking or send mail.
Database migrationsSchema drafts are not applied. Migration promotion requires owner approval, rollback plan, backup/restore proof, schema review, tenant review, audit reference and synthetic test proof.
ProductionProduction requires a release runbook, sensitive credentials path, promoted migration plan, rollback, observability and named customer owner.
Security Review Snapshot
Data boundaryNo sensitive credentials, credentials, VPN access, private keys, raw customer personal data or production write permission are requested by the public site.
Human approvalRaven prepares decision packets. The customer remains responsible for approval, change control and operational execution.
Audit trailRaven separates known, estimated, assumed and unknown evidence, then preserves recommendation, approval and outcome review.
Certification boundaryPublic pages do not claim SOC 2, ISO 27001, HIPAA, PCI DSS or other certifications unless formally obtained and published later.
Deployment And Data Modes
SyntheticPublic-safe or synthetic scenarios can validate the decision surface before customer operational data is used.
HistoricalApproved CSV, XLSX, JSON, ticket or log exports can be reviewed offline when retention, deletion and transfer method are agreed.
Read-only pilotRaven may observe and prepare recommendations without executing customer operational actions.
ProductionProduction requires a separate tenant, RBAC, audit, support, rollback, legal, security and owner activation gate.
Support, SLA And Responsibility
SLANo public page creates an SLA. Pilot response targets and production severity classes must be written into a named agreement.
SupportSupport hours, escalation contacts, incident response route and recovery behavior are defined per pilot or production agreement.
Pilot targetsPilot support targets require agreement reference and owner approval; they do not create production SLA or production support activation.
Production supportProduction support scope requires agreement, owner approval, production activation reference, rollback plan and incident response reference before release.
Support boundaryRaven is not sold from the public page as emergency response, managed NOC, outsourced operations or customer incident command.
ResponsibilityRaven does not replace the customer's operational owner, security owner, change owner or procurement owner.
RollbackRecovery queue, rollback behavior, failed webhook handling and owner notification must be documented before live activation.
Questions Raven Expects From Enterprise
Can Raven work on-premise?Deployment model is selected during scope review. On-premise or restricted environments require separate architecture and security review.
Can Raven work air-gapped?Air-gapped or offline analysis is a deployment discussion, not a default public-site claim.
Who are subprocessors?Any production subprocessor list, data transfer route and region requirement must be reviewed before activation.
What is available before NDA?Public findings, public-safe architecture, pilot framework and methodology. Customer-specific detail requires approved scope and disclosure boundary.