Questions

You can, and if documents are your product it may be right. For most teams they are a means to an end: a renderer, page breaks, fonts, a template editor, versions, hosting, access links, retries, storage and security reviews, all kept running after the first release. Pressfox does that work full time, so your engineers stay on what your customers pay you for.

What Pressfox runs for you Link to this answer

A first test report takes one request, so you see a real result on the day you sign up. Connecting production means mapping your data to the template's fields. Each published template comes with its field list, and test mode lets you try every case without using your allowance or reaching your customers.

Read the quickstart Link to this answer

Yes. The Playground in the app sends a real test request to a published template. Pick the version and language, edit the example data (checked as you type), press Send, and open the page and the PDF. Test reports are watermarked, free on every plan and deleted after 24 hours. When it looks right, copy the request as curl, Node or Python for your developer.

Ways to connect, with and without code Link to this answer

No. Upload a PDF of a report you make today and Pressfox builds a draft template with the same sections, wording and fields. You improve it and publish. The PDF is deleted within 24 hours. Only its text goes to our AI provider, never its pictures. Scanned PDFs are not supported: export the report as a PDF from the program that makes it.

Start from your report Link to this answer

Yes, in beta on the Pro and Enterprise plans. Upload a fillable PDF form and Pressfox copies it exactly: the original page is kept behind the fields, and its blanks become fields your data fills, by API, by hand or from a spreadsheet. A form can be split between people: your part filled and locked, the rest left for them to complete. Pressfox fills the form you uploaded; whether a filled form is accepted is the requester's rule, not ours.

Plans and prices Link to this answer

Not to start. Anyone can design templates in the browser, and editors can create real reports by filling in a form in the app, with the same checks, page and PDF as a report from your system. A developer connects your system with one request when you want reports to go out on their own. After that, the people who own the layout publish changes without a release.

The product tour Link to this answer

Nothing. Every new workspace starts with 14 days of Standard, without a card. After that the Free plan includes 50 report units a month, plus unlimited test reports while you build.

Plans and prices Link to this answer

No report is created. Every field is checked against the template first, and the answer names the field to fix, for example that $.vessel.imo is missing. A half-filled report never reaches a customer.

The error catalogue Link to this answer

Nothing. Publishing creates a new version and never overwrites the old one. Reports already made keep the version, the link and the PDF they were made with. New reports use the new version, unless the system sending them pins an earlier one.

How versions work Link to this answer

Yes. Every publish is a new numbered version. A system can pin the version it was built for (inspection@1) and keep using it while you publish version 2, then move when it is ready. Each version keeps its own field list. Made a mistake? Make an earlier version current again in one click, and retire old versions once nothing needs them.

Versions in the API Link to this answer

Yes. Each report is pinned to the template version and the data that produced it, and keeps its own link and PDF. Nothing about it changes when your templates do.

Quality, backed by how it works Link to this answer

In the EU. The data you send, the report pages and the PDFs are encrypted with your workspace's own key and kept apart from every other customer by the database itself. Each report has its own access rule: an open link, a password or an expiry date, and on Pro a signed or private link. From Standard, the PDF itself can also open only with a password your reader knows.

Security in full Link to this answer

Yes, from Standard. Set a password per report, or take it from the report's data, such as a date of birth or the last 4 digits of an account. Readers can print and copy once it is open. We never keep the password, so we cannot recover it.

How report access works Link to this answer

From Standard, every live PDF is recorded when it is made, and prints where to check it once you have your own report address. Anyone drops the file on the verify page and sees who issued it and when, and whether it was replaced or revoked. The file never leaves their browser. A changed or re-saved file is not found.

Verifying a document Link to this answer

No. Every plan, Free included, gets the same encryption, the same isolation between workspaces and the same EU hosting. Higher plans add control, not safety: zero-retention mode, a downloadable audit log and two years of audit history on Pro, and on Enterprise, on request, storage set apart for you.

What every plan gets Link to this answer

On Pro and Enterprise, yes: zero-retention mode. The data you send is deleted once the report is ready, and the report itself a set time later, from 5 minutes to 24 hours. You collect it in that window by webhook and the API. Sharing by email, AI translation and summaries are off in this mode. While we render the report we still process its data, under the DPA.

How zero-retention works Link to this answer

Text only, never images, and only what the feature needs: a template's text for translation drafts, or the fields you marked in one report. It goes to Anthropic in the United States; reports, payloads and PDFs stay in the EU. Nothing is sent when a report is printed, AI features are off for health workspaces, and your content is not used to train models.

What the AI sees, feature by feature Link to this answer

Yes. Ask for a Markdown version when you create a report, or turn it on for the whole workspace. It has the same content as the PDF, in reading order, with tables and labels intact. Code builds it, not AI, so the same report always gives the same text. Assistants connected through our MCP server can create a report and read its Markdown.

AI-ready output and MCP Link to this answer

Not yet, and we will not suggest otherwise. The security page lists every control that runs today, the subprocessors we use and what is still planned.

Certifications and what is planned Link to this answer

Yes. Photos print whole, never cropped, and each is sent at the resolution it actually prints, so a report with a hundred photos renders in seconds. Turn on the photo appendix and every photo gets a number, a full-size page and a link to the online version, where it opens in a lightbox.

Inspection reports and other use cases Link to this answer

Yes. Every plan uses your logo, colours and fonts, and paid plans remove the Pressfox watermark. Standard holds 3 brands, more at $10 a month each, and report links on your own domain; Pro has a brand for every customer.

Brands and domains Link to this answer

One unit is a live report of up to 50 pages; test reports never count. Overage, caps and worked examples are on the pricing page.

How units work Link to this answer

That is Enterprise: a custom SLA, invoice billing, a named contact and a data processing agreement with your redlines. Every other plan includes the standard DPA.

Compare plans Link to this answer