Original Pictures vs Truepic: a Technical Architecture Comparison
· Mahdi Kazempour, Founder, Original Pictures
Definition: This comparison maps the technical architecture of Original Pictures, a horizontal signing API, against Truepic, a controlled-capture provenance company, across signing, identity, watermark, anchor, and verification.
TL;DR: Truepic optimizes for controlled capture in verticals like insurance and lending. Original Pictures optimizes for API-scale signing across modalities with a three-layer bundle and an open verifier. The right choice depends on whether your problem is deep capture in one vertical or broad marking at scale.
Two starting points
Truepic started from controlled capture: prove an image was taken now, here, unaltered, and build verticals around that. Original Pictures started from the API: let any platform sign any output with a manifest, identity, watermark, and anchor in one call. The architectures reflect those origins.
Feature matrix
On signing, both produce C2PA-compatible provenance. On identity, Original Pictures leans on CAWG aggregation to name platform and creator together. On watermark, Original Pictures layers TrustMark and audio and video watermarks; on anchor, it adds OpenTimestamps to Bitcoin, which controlled-capture tools generally do not. On verification, Original Pictures ships an MIT open verifier to remove vendor dependency. On capture, Truepic is mature today; Original Pictures' capture app is on the Q3 2026 roadmap.
Honest trade-offs
If your need is a deep, vertical controlled-capture deployment right now, Truepic's focus is an advantage and the capture maturity matters. If your need is marking output across image, video, and voice at API scale, with an open verification path and a blockchain anchor, Original Pictures fits. Neither is strictly better; they are built for different shapes of problem.
FAQ
Are the latencies comparable?
Both add sub-second signing in typical configurations. Exact numbers depend on modality and deployment; benchmark on your own corpus rather than trusting a single published figure.
Where Original Pictures stands today
Original Pictures ships three things today: a Sign API, a Verify API, and the SDKs that wrap them. One POST /v1/sign attaches a C2PA-format manifest, an invisible TrustMark watermark, and an OpenTimestamps anchor. The open-source verifier checks any of it without calling us.
Two things are on the near roadmap, and we name them as roadmap, not as shipped: C2PA Conformance Program recognition (target Q3 2026, until then our manifests use the published C2PA v2.2 format and any C2PA-aware validator can read them, but third-party validators will show our signer as not-yet-listed), and a consumer capture app (Q3 2026). We do not sell a capture SDK, and we do not claim Trust-List membership we do not yet hold.
Bottom line: Truepic is the vertical capture specialist; Original Pictures is the horizontal signing API with a three-layer bundle and open verification. Choose by the shape of your problem, not by a feature checkbox alone.
Related
Original Pictures is progressing through the C2PA Conformance Program; our signing certificate is not yet on the official C2PA Trust List. Target: Q3 2026. We will not describe ourselves as "C2PA-certified" until it is true.
Original Pictures provides content-provenance infrastructure. It does not by itself constitute legal compliance with the EU AI Act or any other regime; compliance depends on how you deploy it, your disclosures, and your governance. Figures are drawn from public reporting, verify against primary sources before citing in regulated materials. Nothing here is legal advice.
Last verified 2026-05-25. Author: Mahdi Kazempour, Founder, Original Pictures.