Offline Mode

Raven's dashboard, engagement records, imports, findings, notes, and basic reports work without an internet connection once Raven and its required tools are installed. AI is optional: you can use a manual prompt, a saved BYO provider, or Chamber Door's managed service.

There's no offline mode to toggle and no license heartbeat to keep alive. A compatible local model can provide native BYO analysis without internet access if its API endpoint is reachable from the Raven server. Raven does not bundle a model or download one for you.

What works offline

Capability	Without internet	Connection needed
Web dashboard, local REPL commands, engagement records and notes	✓	Access to the Raven server
Importing existing scan data; templates, exports and basic markdown/PDF reports	✓	Local files and installed dependencies
Running modules: scans, enumeration and checks	Depends on the module	Access to the target, agent or jumpbox; some tools also need external APIs or internet resources
Generating a manual prompt and restoring a pasted response	✓	Your chosen model may need a connection when you use it
Native BYO engagement analysis with a compatible local model	✓	A running model and compatible API reachable from Raven
Native BYO analysis with a hosted provider		Internet access to the saved provider
Managed advisor, chat and AI report writing		Internet access to Chamber Door, a paired account and managed AI credits

No internet access does not mean no network access. A scan still needs a reachable in-scope target, and a remote agent or jumpbox needs its own connection. Install tools and obtain required data before entering an isolated network.

Choosing an AI path

• Manual prompt and response: generate and inspect the prompt in AI Analysis, copy it to your chosen model, and paste its text response back into Raven. Raven makes no provider request for this exchange. No pairing, saved API key or Chamber Door credits are needed; the AI app you use may have its own connectivity and billing requirements.
• Native BYO analysis: save OpenAI, Claude, Gemini, or a local/other compatible API server in Settings → AI & privacy. Native BYO analyzes an engagement snapshot in the individual web dashboard. A compatible local endpoint can work on an isolated network; hosted providers need internet access. Provider costs are separate from Chamber Door credits.
• Managed AI: advisor, chat, tool-use loops, finding drafts, report writing, and the existing REPL AI commands use the Chamber Door path. Pairing and available managed credits are required for these features. Saving a BYO provider does not redirect them.

Saving BYO settings sends no provider request. Test provider connection sends a small request without engagement data and may incur provider charges. Direct analysis requires Prepare anonymized request, review of the prompt and destination, and an explicit send. See AI Analysis for supported API formats and review limits.

On an air-gapped network without a reachable model, you can still produce a client deliverable: the basic report renders scope, methodology, inventory and findings to markdown or PDF locally. You can generate a manual prompt and use it later on a permitted connected system.

Review the context before sharing

Raven replaces known identifiers with placeholders on the Raven host and redacts recognized credential formats. The reversible identifier mapping stays locally with the engagement; recognized response placeholders are restored there. Redacted secrets cannot be restored. These checks minimize identifying content but do not guarantee perfect anonymity: unregistered names, unusual secret formats, and identifying technical context may remain. Inspect the outgoing prompt and follow the engagement's data-handling rules, including when using a local model. See AI Analysis.

Working on a disconnected network

A typical disconnected engagement:

1. Before you disconnect: install the tools you need. If using local AI, provision the model separately and save its compatible endpoint. Optionally pair with raven-server auth login if you plan to use managed AI when internet access returns.
2. On the isolated network: create the engagement, define scope, run modules whose required connections are available, import scans, and capture findings and notes. Use basic reports, manual prompts, or native BYO analysis with the reachable local endpoint as needed.
3. When a permitted connection is available: open the engagement and choose hosted BYO analysis or paired managed AI. Prepare and review a fresh outgoing request before sending it.

Your engagement data is stored under pentests/. Back it up or transfer it according to the engagement's data-handling rules; it includes sensitive records and local identifier mappings. Pairing state lives separately in ~/.raven/auth.json. Preserve the separate database encryption key when backing up encrypted credentials; see Credential Encryption.

When the account is unreachable or suspended

If Chamber Door can't be reached, or the account is suspended/lapsed:

• The server keeps running and local engagement work remains available, subject to the tools and target connections it needs.
• Managed requests return a connectivity or account error; exhausted credits produce 402 BUDGET_EXHAUSTED. See Troubleshooting.
• Native BYO and manual workflows remain separate from managed availability and billing. Raven does not automatically switch providers after a failed request.

An unavailable AI service does not prevent local findings, imports, exports or basic reports.