Inside fileForensics: keep evidence separate from the verdict
A recent Product Hunt launch documents per-check results and review signals rather than making a completed run synonymous with trust.
Product Hunt's 4 November 2026 daily board placed fileForensics eighth with 119 points when checked on 5 November. This dated launch signal is not adoption, reliability or a final lifetime total.
Documented components, not a complete production inventory.
- File upload and stored-file API
- Confirmed interfaces to start checks and retrieve the newest result
- Per-check result states
- Confirmed separation of issues, information, skipped checks and errors
- Integrity questions
- Confirmed signal, no-signal and insufficient-evidence outputs; not an automatic fraud verdict
A recent product launch from an established provider
Product Hunt records fileForensics on its 4 November board at #8 with 119 points. fileAI had earlier launches; this is not a newly founded company. FreeStack reviewed current official documentation and pricing, but did not upload a file, call the service, test accuracy or assess customer outcomes.
Confirmed interfaces: upload, start and retrieve
The overview documents FILE_FORENSICS on POST /v1/files/upload, later checks through POST /v1/forensics and retrieval through GET /v1/forensics/files/{file_id}. Checks operate on the original file and report as they finish. These are confirmed API interfaces; the internal database, model vendors and hosting architecture are undisclosed.
A complete run can still contain an issue
The overview currently describes 55 checks and distinguishes none, issue, found, skip and error. Integrity questions can return insufficient_evidence. Completion does not establish authenticity. These are dated provider claims, not independently measured detection capabilities.
Known limitations matter more than a confident label
The overview marks AI text detection as not active, describes its attention heatmap as no verdict by itself and notes a password-protected Office-file skip. An unavailable or failed check must remain unresolved. FreeStack has not tested these behaviours.
Paid access stays outside the ongoing-free catalogue
Current official docs and pricing quote $0.05 per completed fileForensics run. No recurring free allowance was verified, so fileForensics is a source-checked build study rather than an ongoing-free catalogue addition. FreeStack does not infer free access from Product Hunt's Free Options label or describe a sandbox as an unlimited free production plan.
FreeStack editorial lesson and smaller learning route
The design lesson is to preserve per-check evidence and unresolved questions before making a decision. The linked guide uses VS Code, qpdf, pdfplumber and Git to review a harmless fictional PDF locally. These tools are FreeStack's suggested learning kit, not fileAI's production stack or a substitute for forensic analysis. Save the kit, then pay only for a specific volume, review, provenance or integration requirement.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.