What exists, what is partial, and what is not ready

Current status

Proofline has experimental server and web-client work today. Production capture clients, hosted accounts, notifications, and decryption workflows are not ready.

Current

Experimental server

The server can handle authenticated account routes, receive already-encrypted evidence chunks, store metadata, enforce quotas and rate limits, and support private operator workflows.
Current

Web-client prototype

The web client is an experimental account and incident-review prototype. It is not a recording client, mobile app, public admin dashboard, or production safety workflow.
Partial

Trusted-contact metadata

Trusted-contact relationships, sharing grants, and wrapped-key metadata exist as authenticated backend data. They do not yet add production trusted-contact review, notification delivery, or decryption.
Partial

Deployment hardening

Optional PostgreSQL, S3-compatible storage, Valkey coordination, and relay primitives exist, but they do not make Proofline public-production infrastructure by themselves.
Planned

Product direction

Native capture clients, location and context capture, trusted-contact review, hosted accounts, billing, and stronger upload behavior are future work.
Not ready

Emergency reliance

There is no emergency-services integration, dispatch, staffed monitoring, guaranteed real-time response, or production mobile recording workflow.

Not implemented today

  • Production iOS or Android capture clients.
  • Trusted-contact SMS, email, push, or Messenger notifications.
  • Live location/context sharing as a production feature.
  • Browser, backend, or trusted-contact decryption workflows.
  • Raw server-held media keys, key escrow, or break-glass access.
  • Hosted-account billing, checkout, or active paid account creation.
  • Playable media export or legal-submission workflow.
  • Public production deployment hardening for broad API exposure.

Where detailed docs live

The public website is intentionally short. Developers and reviewers should use the GitHub repositories for implementation details, deployment boundaries, security models, and roadmap planning: open-proofline on GitHub .

Sources

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