Documentation

Build your record with confidence.

Technical guides, API references, and operational procedures for the Evident platform.

Start here Try the demo

Quickstart

From account creation to your first export — the essential path.

1

Create your account

Sign up at /signup/ . All new accounts start on the Free tier — enough to verify the pipeline works on your evidence. No credit card required.

Guest Visitor
2

Upload your first file

Upload video, audio, or document files through the dashboard. Each file is hashed on upload (SHA-256) and stored immutably. The original is never modified.

Starter+
3

Select pipeline stages

Choose processing stages: transcription, OCR, audio events, object detection, legal analysis. Available stages depend on your tier. The pipeline records every parameter for reproducibility.

Starter Core Complete
4

Review and export

Review results in the dashboard. Export court-ready packages that include the original evidence hash, processing provenance, and audit trail in a single verifiable bundle.

Core+

First Upload

Use your first upload to establish an immutable baseline before deeper analysis.

Objective: Create a traceable starting record for a case with one file, one verified hash, and one custody trail entry.

  • 1. Create or select a case: Open your dashboard and pick the case shell that should receive the file.
  • 2. Upload one source file: Video, audio, image, or document. The platform computes SHA-256 at intake and stores the original immutably.
  • 3. Verify intake result: Confirm evidence ID, filename, and intake hash before running any processing stages.
  • 4. Start a minimal pipeline pass: Run only the stages needed to confirm workflow behavior for your matter.
  • 5. Check custody log entry: Ensure actor, timestamp, action, and target are present in append-only audit history.

The first upload is the anchor for every derivative and export generated afterward.

Open Upload Pipeline Practice in Demo

Architecture

System design, data flows, and component boundaries.

Frontend

Static site generated by Eleventy (11ty) and served via CDN. The frontend handles presentation only — all forensic logic runs server-side. This separation ensures that UI changes cannot affect evidence processing.

API Layer

Express.js REST API handles authentication, file upload, pipeline orchestration, and result retrieval. Tier gating is enforced at the API layer before any processing begins.

Processing Pipeline

Evidence passes through configurable stages: audio extraction, dual-pass transcription, vision analysis, and report generation. Each stage records its parameters, model version, and output hash.

Storage & Audit

Original evidence is stored immutably. Derivatives are stored separately and linked to the original by hash. The append-only audit log records every action with cryptographic chaining.

Security Model

How evidence is protected at rest, in transit, and during processing.

Encryption at Rest

Evidence storage supports AES-256 encryption at rest in production configuration, with key material managed separately from storage objects. Review active environment and agreement controls before relying on this for regulated workflows.

Encryption in Transit

Transport encryption is enforced over HTTPS/TLS for platform and API traffic. See the current deployment configuration and policy references in security posture .

Hash Verification

SHA-256 is computed at intake and used to validate source and derivative integrity through processing and export workflows.

Access Control

Role-based access control with tier-gated features. Every access attempt is logged. Failed authentication attempts trigger rate limiting and monitoring alerts.

Audit Logs

Append-only logging for forensic traceability.

Every action in Evident is recorded in an append-only audit log. Each entry includes:

  • Timestamp: ISO 8601 UTC timestamp with millisecond precision
  • Actor: User ID, role, and tier at time of action
  • Action: Type of operation (upload, process, export, access)
  • Target: Evidence ID, case ID, or resource affected
  • Hash Chain: SHA-256 of previous log entry for tamper detection

Audit logs are immutable — entries cannot be modified or deleted. This keeps the record traceable and verifiable under scrutiny.

API Reference

REST API endpoints for programmatic access (Complete tier and above).

Endpoint Method Description
/api/upload/ POST Upload evidence file. Returns SHA-256 hash and evidence ID.
/api/cases/ GET List your cases with status, file counts, and updated timestamps.
/api/pipeline/run POST Start pipeline processing for an uploaded file.
/api/pipeline/result/{fileId} GET Retrieve pipeline status and stage outputs for a file.
/api/custody/{fileId}/verify GET Verify chain-of-custody integrity and hash lineage for a file.
/api/export/pdf/{fileId} GET Generate court-ready export package.

Authentication: All API requests require a Bearer token in the Authorization header. Tokens are managed from the account dashboard. API access requires the Complete tier or above.

Need help finding something?

Use the sidebar navigation to browse by topic, or reach out to support for guidance.

Browse FAQ Contact Support

What Evident does not replace

Important boundaries for responsible use.

Evident ICU is a technology platform for organizing, processing, and exporting evidence records. It is not a law firm and does not provide legal advice, legal representation, or attorney services.

  • No attorney–client relationship is formed by using this platform.
  • AI analysis supports review — it does not replace professional legal judgment.
  • Export packets are structured for attorney review, not a substitute for it.
  • Users remain responsible for evaluating the suitability of any output for their legal matter.
  • Consult a licensed attorney in your jurisdiction for legal advice.