Website guide updated 16 November 2026. Answers describe public release 0.7.3a4; the linked SDK reference retains its own review dates.
One clear starting point
- Run the release quickstart on Linux. The recommended Docker bundle produces a PNG and videos in all three profiles, with development credentials. Install and get the first result ↗
- Put marking after generation. Hand the final supported file to a reusable worker before your app returns or publishes it. Python integration ↗ · Node.js and mobile backends ↗
- Make the result checkable. Run the connected verifier and persistent registry, then inspect the signed reports. Deploy the kit ↗
Successful SDK exports embed signed C2PA in the file. Public manifest API access is a separate opt-in recovery feature. Inspect exact signed sample files and independent results ↗
The image playground demonstrates image watermarking. It is not a hosted production SDK service, a video demo or a substitute for a signed production export.
Twelve questions before you commit
01 Will it fit my files and backend?
The qualified media runtime is Linux x86-64 / Python 3.12 on CPU. Images: supported single-frame PNG/JPEG, 256–4096 pixels per side. Video: supported 8-bit SDR MP4, even dimensions 256–1920 pixels per side, up to five minutes / 18,000 frames; H.264 output. Read the full restrictions, including audio, color and track handling, before integrating. Native macOS/Windows media execution is not qualified.
02 What is under the hood?
Current image and video watermarking use Adobe TrustMark Q. The image path uses Python TrustMark; current video uses a Node/ONNX worker with fresh watermark computation on frames selected by the profile. C2PA supplies signed provenance. Ariadne connects export checks, records, verification and recovery. Meta VideoSeal is retained for legacy compatibility; it is not the default video encoder.
Video implementation and profiles ↗ · Component and model licences ↗
03 How much CPU time and memory will it use?
Versioned measurements cover a 1024 × 683 PNG and a ten-second 720p/30 fps synthetic video on a two-vCPU EC2 host. They separate the first job, resident repeats, export and verification. The current series also includes 1080p fixtures; it does not establish concurrent production capacity or production TSA latency. Use your own files to size the worker.
Timings, memory, raw data and method ↗ · Calculate your operating budget ↗
04 Which video profile should I try?
Economy5s is the default: 125 ms marking windows every five seconds. Economy2s uses the same windows every two seconds. Resilient computes a fresh mark on every frame. All three decode and re-encode the full video. Short excerpts can miss Economy windows; a profile name is not a legal approval.
05 What happens after editing or recompression?
Small published experiments cover ordinary recompression, excerpts, cropping and deliberate removal. They include failures: crops and removers can defeat recovery, and short excerpts may miss sparse windows. Qualification-test counts are not a population durability or false-positive score. Prepare each final rendition before marking, then test the actual file delivered by your app/CDN. Local codec tests do not establish what a named social platform preserves.
Transformation results and limitations ↗ · Final-rendition workflow ↗
06 What is in the watermark and what becomes public?
The watermark carries an opaque identifier linked to a provenance record, not an account name or arbitrary personal text. The signed record and optional registry map that identifier to product facts. The verifier uses reviewed public provider/system/version fields; full manifest publication is opt-in. Keep personal data out of public product fields. The playground's test-message lookup is a separate demo feature.
07 Who signs, and who supplies the credentials?
Your kit uses your provider identity. The current adapter reads a local ES256 PEM key and certificate; it does not expose a KMS/HSM remote signer. Ariadne does not enroll your product in C2PA conformance or obtain a certificate for it. Signature validity, issuer trust, product conformance and statutory compliance are separate questions.
08 Is production timestamping ready out of the box?
The SDK includes an authenticated TSA route; your production credentials still need onboarding. An optional short-lived loopback relay adds a bearer token from a private file and forwards the native RFC3161 request over verified HTTPS. Offline authorization, timestamp validation and failure cases are qualified. Configure your actual certificate, TSA credentials and trust roots, then verify a real production export. This is not live-provider enrollment or legal certification.
09 Who hosts verification and how does it scale?
You host the verifier and registry. The reference verifier has one inference slot, four upload slots and no queue; busy requests can return 429. The application upload ceiling is 512 MiB; the generated TLS edge defaults to 128 MiB. The registry is SQLite, with separate exporter-write and verifier-read roles. These are reference limits, not a promised request rate. Budget negative scans and test contention before adding workers.
HTTP interface, limits and persistence ↗ · Capacity planning ↗
10 Do files leave my infrastructure?
Inference runs on your infrastructure after explicit provisioning. Production signing may contact the TSA you configure. Temporary verifier uploads are removed after success/failure; you control proxy logs, retention, public disclosures and access. The public image playground has its own operator and privacy notice. It is separate from your self-hosted deployment.
11 What is free, and what must I install?
Project code is Apache-2.0, without an Ariadne per-export fee; third-party code and weights retain their own terms. Install from the pinned GitHub release using the documented Docker recipe or wheel. A ready-made hosted marking service is not included. Video-only setup omits Torch/NumPy/Python TrustMark. Budget compute, hosting, storage, signing, timestamps and maintenance; review bundled codec terms for your distribution model.
12 Which requirements does this help me implement?
Source-linked EU/California guides map marking, provenance, verification and remaining operator actions. Check your actual provider/deployer role, markets, media and dates. C2PA soft-binding identifiers used by Ariadne are provisional; use of a registered underlying method does not register this integration or certify compliance. Visible disclosure, product policies and other applicable duties still need your assessment.
Requirement → measure → evidence → owner ↗ · Visible labels and machine-readable marking ↗
From a pilot to production
- Prove the development flow. Export, verify, inspect receipts and recovery records. Keep this separate from a production-signing claim.
- Resolve signing and timestamp integration. Choose the actual operator/product, credential route and trust policy. Qualify the required TSA authentication and a real signed export before relying on the production path.
- Test your delivery. Use representative images and videos. Measure normal transforms, visual quality, retries and unsupported inputs. Check downloaded bytes from the real app/CDN.
- Operate what you publish. Provision verifier capacity, HTTPS, state persistence, backup/restore, key lifecycle and a public contact. Confirm applicable disclosures and record the open actions.
Detailed production setup ↗ · Keep an operator evidence record ↗
Support and release status
Public releases, source and known limits are available for inspection; no production SLA or response-time commitment is offered. Report a reproducible integration issue or contact ivan@griffonix.com about an evaluation. Include the version, supported input facts and sanitized logs; do not post private files or keys.