A full PDF editor, inside your own instance
A PDF opens like any other document: you annotate it, fill it, sign it, reorder its pages and convert it — without ever uploading it to a third-party conversion website. And every change becomes a version you can restore.
- 118 PDF operations
- The last 10 versions kept
- Internal e-signature
- OCR for scanned PDFs
A full PDF workshop, not three buttons
The figures below are counted from the operation catalogue that ships with the product — they are not estimates.
- 0
- PDF operations in the catalogue
- 0
- tool categories
- 0
- ways to run an operation: PDF workshop, open document, chat, automation
- 0
- versions kept per PDF, restorable in one click
Into PDF, and out of PDF
Every chip is one operation from the catalogue, executed by your instance's own PDF worker. One exception, and it is named: the conversions that go through an HTML rendering step fetch the images and stylesheets the source references — through a filter that refuses local files and internal addresses.
One catalogue, reachable from four places
Organize, convert, secure, annotate, fill, sign, clean up, validate: 118 operations across 19 categories. The list does not change depending on where you opened it from.
- 1Inside the open documentThe tool panel of an open PDF offers only the operations that produce a PDF: their result has to be able to become the document's next version. 75 of the 118 pass that filter; the ones that render something else — an archive, a spreadsheet — stay in the PDF workshop, which opens the whole catalogue. Same list, same queue, never a second tool.
- 2One queue, one progress barEvery run becomes a job you can follow end to end: live progress, status, and a sentence you can act on when something fails — never a raw code.
- 3Several steps, a single jobA chaining operation runs several treatments over the same file in one execution, so you get one version at the end rather than one per gesture.
- 4What is locked stays visibleAn operation that belongs to a higher plan is shown with a padlock and the plan it needs, instead of disappearing — unless your administrator has chosen to hide features the seat does not include.
Getting a document signed, from placement to evidence
Signature requests go to accounts in your own organization: external signers are not supported. Asking for a signature is a P3 plan capability; signing is not.
- 01
Place each signer's block
You pick the people, then drop each one's block on the page and at the spot you want. The rectangle is stored in PDF points, in the frame the editor displays — so the signature lands exactly where you put it, including on a page the scanner turned sideways.
- 02
Everyone is notified, and sees it in the app
An email goes out to each signer, and an “awaiting your signature” strip appears on the Documents home. The link opens the signing dialog directly, without requiring full access to the document.
- 03
The signing order is respected
Each signer carries a rank; two people on the same rank sign in parallel. The server decides whether it is your turn, never the interface — it only displays the answer.
- 04
Each signature is sealed over exact bytes
At the moment of signing, the document version and the SHA-256 of its exact bytes are recorded with the signer. The retention pruner is not allowed to delete a version that a signature cites.
- 05
Decline, cancel, document moved
A signer can decline with a reason; the requester can cancel the envelope. And if the document moves after it was sent, the envelope says so: it remembered the version and the hash the request was raised against.
Your PDFs stay in your instance, and the exceptions are named
The question is not only “can the tool merge two PDFs”. It is “where did the contract go, and who can prove it”.
A free PDF conversion website
- The file leaves your network and lands with a third party whose location and retention you do not control.
- No trace in your audit log: nobody can say who uploaded what, or when.
- No way back: the previous version no longer exists.
- A different website per operation — merge here, compress there, sign somewhere else.
The PDF editor in your instance
- The operation runs on your own instance's PDF worker. Three of them do call out, and here they are: vision-model OCR sends the pages to the configured model, certified timestamping asks an external time authority, and HTML rendering downloads the resources the source references.
- The result file is wiped from disk the moment it is downloaded, and the working directories are swept every five minutes.
- Every change becomes a dated version, labelled with the reason that produced it, restorable in one click.
- Editing a PDF and restoring a version are both written to the audit log.
- The permissions are the document's own, doubled by a licence: whoever may read it reads it, and applying a tool takes edit rights, a write licence, and the operation's own plan when it requires one.
Everything you open Acrobat to do
The rest of the workshop, where it belongs: inside the document, with no export and no second tool.
Comments and review
A highlight on a page is just a coloured rectangle: the comment's body, its author, its replies and its status live in a panel beside the document. You read the whole thread there, reply, change the status, delete — and each of those becomes a version of the file.
Organize pages
A thumbnail grid where you move, rotate, duplicate and delete pages. Nothing is applied until you confirm: the whole reorganization goes out as a single job, and all of it is reachable from the keyboard.
Edit the text already on the page
Fix a line directly on the page. The editor warns you before you commit if the document's font may not be able to write the characters you typed. P3 plan.
Design forms
Draw the fields somebody else will fill in: text, checkboxes, radio buttons, choice lists. Every field carries a name, because that is the key the answer will be stored under. P3 plan.
OCR for scanned PDFs
The editor recognizes a page with no text layer — a scan — and offers text recognition. That one runs locally inside your instance and adds a selectable text layer, with no AI budget spent. The catalogue carries a second one, handed to a vision model your administrator picks in the settings.
PDF/A and PDF/UA conformance, actually validated
Validation runs on veraPDF, the reference validator for those standards. And when it is not available, the report says “not checked” — never “valid”.
Document properties
Page geometry, fonts, attachments, form fields, whether a signature is present: all of it is read from inside the document, with no job to run. What only the server can settle is announced as such rather than guessed.
From chat, and from an automation
The same operations run in plain language on a chat attachment, or inside a scheduled automation. Same catalogue, same queue, same permissions.
The one-pager — read it here, or take it with you
Read the full sheet without downloading anything, fullscreen if you prefer. The PDF stays available to share internally.
Inside this sheet
- 1118 PDF operations
- 2Fill and sign without fields
- 3Internal e-signature
- 4Version history
- 5Comments and pages
- 6OCR for scanned documents
Open your first PDF
The PDF editor is part of HiloIntelligence: nothing to install, nothing to plug in. Create your cloud instance, or ask for private hosting installed and operated by Hilo Tech.