Current and planned repository split

Repositories

Proofline is split by component. The server and web client exist today; iOS, Android, and protocol repositories are planned.

Experimental · Not an emergency service

Proofline is experimental and does not contact emergency services. Read the safety boundaries.

Current

open-proofline/server

Go backend for authenticated main API routes, local account/session auth, private admin surfaces, read-only viewer, encrypted chunk ingest, owner-scoped metadata, storage, releases, deployment docs, and backend reference documentation.

Open server repository

Current

open-proofline/web-client

React account portal and incident-review prototype for account UI, registration and verification flows, incident metadata review, contact metadata, sharing grants, and wrapped-key metadata.

Open web-client repository

Planned

open-proofline/ios-client

Future native iOS incident capture, encrypted local staging, upload, local account flows, and platform-specific recording behavior.

Planned

open-proofline/android-client

Future native Android incident capture, encrypted local staging, upload, local account flows, and platform-specific recording behavior.

Planned

open-proofline/protocol

Future shared API specs, encryption envelope specs, bundle manifests, compatibility matrix, and conformance tests.

Scope

Separate components

Server, web-client, mobile client, and protocol work are kept in separate repositories so each component has a clear home.

Project docs

The repository docs linked below provide the detailed implementation and security context behind this website’s shorter overview.

Sources

These project documents provide more detail about the current implementation, planned work, and security limits.