Workflow documentation showed sequential signing, certificates, audit logs, APIs, and self-hosting options. It could preserve locality, but would shift operation of a security-critical evidence platform and its assurance dependencies onto the development team.
- What worked
- The documented deployment and workflow flexibility made it a serious self-hosted alternative.
- What got in the way
- The operational burden around identity assurance, keys, timestamping, evidentiary validation, security updates, and availability outweighed avoiding an external processor.
