Pinned comments
Comments on a point of an image or PDF page, or at a video frame, with markup and replies.
Feedback on the exact frame, approval on the exact version
Share designs, PDFs and videos with clients, collect comments on the exact spot, and get each version approved.
Each proof (title, project, client, deadline) holds versions v1, v2 and on: images (PNG, JPG, WebP, SVG up to 40 MB), PDFs (up to 60 MB, shown page by page in the browser) and MP4 or WebM videos (up to 95 MB) in R2, checked by extension and first bytes with a SHA-256, or a video link; files can also come in from a Creatives or Drive link. Comments are pinned at a point on an image or PDF page, or at a video time with frame stepping, with box, arrow and freehand markup, threaded replies, resolve and reopen, and @mentions. Two image versions compare side by side or with a slider. Reviewers open /p/<token> in the domain's brand with their name and email (and an email code when the proof asks for one), comment and draw on the current version, and approve or request changes; each decision records who, which version and its file SHA-256. Comment emails go out in batches every 15 minutes, with deadline reminders daily at 10:00 IST. Claude turns open comments into a numbered change list and proofreads the visible text of an image or PDF. "Record in Approvals" (optional) sends a version to Approvals; POST/GET /api/v1/proofs and webhooks.
What Proofs does for you.
Comments on a point of an image or PDF page, or at a video frame, with markup and replies.
v1, v2 and on, with side-by-side and slider compare for images.
Reviewers approve or request changes, recorded with the version and its file fingerprint.
A suggested path for Proofs. What you can do depends on your access in the app.
An image, PDF or video, or a link from Creatives or Drive.
Clients comment in the brand's look, with an email code if you want one.
Approve or request changes per version, with reminders before the deadline.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each proof (title, project, client, deadline) holds versions v1, v2 and on: images (PNG, JPG, WebP, SVG up to 40 MB), PDFs (up to 60 MB, shown page by page in the browser) and MP4 or WebM videos (up to 95 MB) in R2, checked by extension and first bytes with a SHA-256, or a video link; files can also come in from a Creatives or Drive link. Comments are pinned at a point on an image or PDF page, or at a video time with frame stepping, with box, arrow and freehand markup, threaded replies, resolve and reopen, and @mentions. Two image versions compare side by side or with a slider. Reviewers open /p/<token> in the domain's brand with their name and email (and an email code when the proof asks for one), comment and draw on the current version, and approve or request changes; each decision records who, which version and its file SHA-256. Comment emails go out in batches every 15 minutes, with deadline reminders daily at 10:00 IST. Claude turns open comments into a numbered change list and proofreads the visible text of an image or PDF. "Record in Approvals" (optional) sends a version to Approvals; POST/GET /api/v1/proofs and webhooks.
Making the design belongs to Creatives; storing files belongs to Drive; generic sign-offs belong to Approvals.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
proofs.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.