Skip to content

Roadmap

This roadmap highlights the next capability areas we expect to document and expand in the C2PA Signing Service project.

It is a public-facing view of the direction of the docs and service surface, not a dated delivery plan. The topics below are intentionally unordered and should be read as planned capability areas rather than release commitments.

Current Scope

Today, the docs cover the current service surface, runtime configuration, local operation, S3-backed operation.

The roadmap extends that foundation into eleven areas where the current docs and public surface are intentionally incomplete:

  • Softbinding Insertion: move from placeholder watermark endpoints toward a documented softbinding insertion capability
  • Softbinding Manifest Storage: describe how durable manifest storage could support lookup, retrieval, and operational workflows
  • C2PA Orchestration: document how higher-level orchestration could shape multi-step C2PA flows beyond the current request-processing model
  • Multi-Cloud Deployment Guides: extend the current local and S3-backed operational guidance into broader deployment patterns
  • C2PA Image Signing: extend the current authenticity story beyond video and fragmented media into image-oriented signing workflows
  • Authentication And Authorization: describe how access control and caller identity could shape protected service usage
  • Job Completion Webhooks: document a callback-driven alternative to polling for async job completion
  • Expanded Resolvers And Sinks: describe broader cloud and database-oriented input and output integration paths
  • Persistent Job Storage: explain how durable SQLite/PostgreSQL-backed job state could replace in-memory-only lifecycle tracking
  • Live DASH Streaming: extend the packaging roadmap toward live DASH-oriented workflows beyond today’s batch processing model
  • MXF Reference Implementation: describes how the Security4Media authenticity group could contribute to a C2PA-in-MXF reference implementation for broadcast workflows

How To Read This Section

Each roadmap page follows the same format:

  • a short note on the current repo or docs state
  • the planned outcome
  • why the area matters
  • what likely needs to be in place first
  • the main open questions still shaping the final docs