Questions before the first meeting
Enterprise FAQ
This page answers the questions a CTO, CISO, procurement lead or executive sponsor should ask before giving Raven access to anything sensitive.
Audience enterprise buyers
Tone direct answers
Boundary no overclaim
Technical And Security
Does Raven need production access to start?No. The first serious step can be an offline review or replay pilot using approved exports.
Does Raven replace monitoring?No. Monitoring may be a source. Raven prepares the decision packet that follows the signal.
Can Raven work on-premise / On-prem?Potentially, after architecture and security review. The public site does not activate that model.
Can Raven work air-gapped / Air-gapped?Potentially as a separate enterprise model with offline packaging, update and evidence-transfer design.
What about tenant isolation?Tenant context, evidence references, role scope, retention rules and audit logs must not mix customer states.
What about sensitive credentials?Public materials use reference identifiers only. sensitive credential values require approved vault/provider storage, owner, rotation policy, emergency revoke path and audit reference.
Is the API active?No. API request envelope and API runtime guard stack are preflight contracts only. The public site does not start a listener, execute endpoints, write database records, call providers, accept customer data or activate runtime.
What is the current API boundary?No. API request envelope is a preflight contract only. The public site does not start a listener, write database records, call providers, accept customer data or activate runtime.
What must an API request pass later?Endpoint contract, endpoint release approval, closed blockers, auth where required, tenant validation, RBAC, audit reference, idempotency, rate limit, provider signature and safe error mapping.
Is customer portal sign-in active?No. Portal session readiness is a boundary contract only. The public site does not create sessions, set cookies, call external auth, open tenant runtime or write customer session records.
Are portal modules active?No. Modules are entitlement previews only. Package depth, RBAC permission, session readiness, audit reference and owner approval are required before release, and the public site loads no tenant data.
Is workspace data active?No. Workspace read model is a pre-release contract only. It can be prepared only from approved module snapshots and approved data modes, and the public site does not read a database, start live queries or load customer data.
Can workspace data be exported?Not from the public site. Report, dossier, audit, CSV, XLSX, JSON or PDF export requires approved scope, format, held delivery, retention, owner approval, audit reference, export authority and DPA/redaction gates when personal data is present. The public site does not write files, enable downloads, send notifications or start delivery.
Can Raven generate a pilot package from this site?No. Pilot evidence packages require scope, evidence register, model register, limitation statement, audit reference, export gate and owner approval. Customer-data modes also require upload, workspace and retention gates. The public site does not generate packages or deliver reports.
What happens before a customer data room opens?A Customer data room manifest must define required, optional and excluded data, allowed formats, size limits, transfer channel, retention, DPA state and personal-data gates. The public site does not open rooms or accept files.
Does a release-ready pilot start automatically?No. Pilot activation release gate means activation is still blocked until a separate controlled executor is approved for channel opening, upload, account creation, payment capture or notification.
Pilot And Governance
How long does a pilot take?It depends on scope and data readiness. The first gate is defining one bounded incident class and success criteria.
What data is required?Minimum approved evidence: incident/ticket/export history, service context, timeline, owner and cost assumptions where available.
Who makes decisions?Raven recommends. Mira frames financial/commercial exposure. A human owner approves action.
Is there an Admin Review Queue?Yes as a readiness surface. It can show pending gates by tenant, severity, approver role, reason and audit reference. It does not approve, assign, notify, read a database, load customer data or mutate production.
Is ROI validated?No. Public pages can show models and hypotheses. Pilot data is required before customer-specific claims.
Can procurement review before pilot?Yes. Scope, support, exclusions, data handling, commercial path and activation gates are visible before pilot.
What happens after pilot?The client receives evidence, limitations, decision exposure findings and a recommendation for stop, extend or production-readiness review.
What must happen before the pilot report exists?Raven must complete the pilot package manifest and owner review. Unsupported claims, missing evidence, missing retention or unresolved personal-data gates block the package.
What pilot paths exist?Research review, free limited pilot and paid pilot paths can be evaluated separately. Each path requires agreement acceptance before customer data, account access or operational activation.
When is retention agreed?Before intake. Retention category, retention days, deletion owner, deletion verification and legal-hold boundary must be explicit before customer-data processing.
Procurement And Legal
Is this page an offer?No. Public pages explain scope and boundaries. A final quote requires scope, package depth, support assumptions, legal terms and human commercial approval.
What must happen before a quote is sent?Scope, legal review, tax review, owner approval, valid-until date, audit reference and evidence-backed quote lines must be ready. Quote readiness does not create checkout, invoice, payment or activation.
Is there an SLA?Not from the public page. Pilot response targets and production severity classes must be written into a named agreement.
What is the support boundary?Pre-contract support creates no SLA. Pilot targets require owner-approved agreement. Production support requires activation, rollback and incident-response references before release.
Is Raven emergency response or managed NOC?No. Raven is not sold from the public page as emergency response, managed NOC, outsourced operations or replacement for customer incident command.
Are credit package prices final public prices?No. The current planning catalog uses 100, 200, 500 and 1000 credits at EUR 15 net per Raven Decision Credit before quote-specific approval and tax review. Provider prices and checkout sessions require separate release.
When do purchased credits become usable?Only after provider event readiness, idempotency, owner approval, credit ledger persistence and owner release gate. A payment event alone does not make credits available or activate service.
Can payment or signup activate a customer?No. Customer activation requires account readiness, approved customer-activation review, owner or admin release, audit reference, rollback reference and support scope. The public site creates no account, session, tenant runtime or activation notice.
How is the balance shown?Available balance counts only ledger_entry_persisted_verified entries. Pending credits, low-credit warnings and Mira notices remain review-only until the relevant release gate is closed.
Can customers open billing portal from the public site?No. Billing portal session creation requires role authorization, allowed scope, owner approval and provider release. The public site does not issue portal redirects or change payment methods.
Does the public site issue invoices?No. Invoice artifacts are draft previews until owner release. Legal invoice issue, provider invoice creation, tax document issue, KSeF submission and payment collection require separate controlled gates.
Is a DPA required?Yes when customer data or personal-data-relevant evidence is processed. Data class, retention, deletion and transfer channel must be approved first.
What leaves the client environment?Only approved exports or agreed evidence references for the selected review mode. Live production data requires a separate gate.
What stays with the client?Credentials, sensitive credentials, production change control, legal responsibility, operational authority and final approval remain with the customer.
Who carries responsibility?Raven prepares evidence-bound decision packets. The customer-approved human owner remains final authority for operational action.
What is not bought?Emergency response, managed NOC, outsourced operations, unsupported savings claims and unrestricted access to Raven implementation are not included.
Can procurement review first?Yes. Commercial process, support model, deployment models, data requirements and security boundary can be reviewed before pilot data is transferred.