Prepare to operate AuditFetch Local

Assign a technical owner before evaluation. Use the instructions and requirements in your signed package. This guide explains the operating commitment; it does not replace version-specific installation commands.

Confirm the supported host platform, CPU architecture, memory and disk capacity with us. AI models and browser capture need additional resources.
Use Docker Engine 28 or newer for the documented localhost network boundary. The qualified 0.1.55 default binds web and API ports to loopback. Configure HTTPS before sharing access across your network.
Prepare authorized read-only source access. Declare the intended organization, account and repositories. Check the capability limits and provider-specific instructions.
Verify the signed installer using the release instructions. Compare its checksum and independent signing trust before startup.
Choose secure backup storage. Protect configuration and encryption keys separately from the host. Do not put secrets in source-scope fields or support messages.

Understand the connections

Evidence and credentials

Stored in your configured Local database, evidence store and secret store. Source records can contain sensitive information. Review scope and redaction.

Source APIs

Configured read-only connections send authenticated requests to the selected provider and receive records. Local storage does not make a cloud source offline.

Release downloads and update checks

Downloading software contacts the release service. Optional signed-channel checks are off by default and on demand. The service sees the channel and source IP; the check sends no evidence or installed-version details and does not install updates.

Licensing

A signed Local license is verified locally. Separate cloud activation or renewal features, when enabled, have their own documented metadata exchange. Confirm the mode in your package.

AI assistance

Readiness calculations do not require an external AI provider. For optional external AI assistance, review the inputs, destination and provider terms first. Local model options need their own resources.

Telemetry

Optional Local telemetry is off by default. It is separate from website consent and provider requests. Confirm package settings before enabling it.

Exports, sync and support

Downloads go to your device. Optional sync sends selected records to that destination. You choose support attachments; do not send credentials, patient data or raw sensitive evidence.

External immutable audit checkpoints need an independently configured Object Lock bucket, signing secret and worker. They are not implied by installing the default Local package.

Keep the deployment recoverable

Back up the database, evidence store, required configuration and keys. An exported packet is not a full installation backup.
Test a restore into an isolated environment. Confirm that expected evidence can be read and its hashes verified.
Monitor free disk space and collection failures. Retention settings do not provide vendor-hosted storage or make physical capacity unlimited.
Before updates, read the signed release notes, migration path and backup requirements. A prior container image does not reverse a database migration.
Keep exported packets and their trusted comparison hashes according to your retention policy. Confirm source, time period and review before sharing.

Finish the evaluation deliberately

The standard evaluation starts when the license is issued. Export useful records before expiry; expired evaluations restrict views and exports. Previously downloaded files remain readable. Stop disposable services and remove test credentials when you finish. Decide which records and backups to retain before deleting a workspace.

For paid plans, use the published cancellation process to stop future renewals. Cancellation and data deletion are separate actions. Follow your license and subscription terms.