How DocHive files documents on your own server | DocHive

How it works

On premise document filing, from new scan to filed contract

Four steps, a queue you control, and a plain list of what leaves your network. If you are here to find the catch, this is the page.

The pipeline

Watch, read, propose, approve.

  1. Watch

    You name the places documents arrive: a scan folder, a shared drive, a mailbox like rechnungen@ or vertraege@. DocHive watches them and picks up anything new.

    In plain terms: a folder listener and an IMAP connection. Nothing is copied out of the source.

  2. Read

    Printed or scanned, the document becomes text. Then it is read for what it is: contract, policy, invoice, quote, and for the details: parties, dates, amounts, notice periods.

    Text recognition and the model that reads it both run on premise, in your office.

  3. Propose

    Your naming pattern is applied and a destination picked from folders that already exist. The result is a proposal, not an action.

    Rules are set up with you on site and can be changed at any time.

  4. You approve

    Approve, and the file is renamed and moved. Edit, and your version is used. Reject, and nothing happens.

    Until then the document sits untouched where it arrived.

The review queue

Nothing moves until you approve it.

The whole product in one screen: one card per document, with what was read out of it and where it would go.

Awaiting review 3

Picked up 09:12 from Scans / Inbox

Page 1 of 6 · scanned at 300 dpi · text recognised

Suggested filename

2026-07-20_AcmeCorp_Contract_Maintenance.pdf

Suggested folder (existing)

Contracts Maintenance Acme Corp AG

Counterparty

Acme Corp AG

Start date

01.08.2026

Notice period

3 months, to term end

Annual value

CHF 18,400

High confidence Notice period read from clause 8.2, the one field worth a glance.

An audit log, not a mystery

Every proposal, edit, approval and rejection is recorded with the user, the timestamp, the old name and the new one. Exportable, and readable by anyone you give the right to read it.

Undo in one click

A filed document can be put back exactly where it was, under its original name. Approving is a decision you can reverse, which is the point of approving at all.

Your folders only

DocHive files into the structure you already have. It does not create folders, restructure your drive, or introduce a parallel archive with its own logic.

Deadlines

The dates come out of the text.

Term, renewal date and notice period are read when the document is filed, and confirmed by you in the review card. The reminder is then counted back from the deadline by the notice period, not by a fixed number of days.

Reminders go by email to the people you name, with a link to the document and the clause the date came from. An ambiguous date is flagged, not guessed.

Next dates

  • 30.09.2026Cleaning contract, Bühler AGNotice must be given by 30.09 for 31.12, 2 months
  • 31.10.2026Liability policy, HelvetiaRenews automatically for one year
  • 31.12.2026Software licence, Nexo GmbHTerm ends, no automatic renewal
  • UnclearStorage lease, Meier ImmobilienTwo conflicting end dates in the document, flagged for a person

Search

Ask it the way you would ask a colleague.

You type

what did we agree with Meier about the roof

You get back

  • 2024-03-11_MeierBau_Contract_RoofRenovation.pdf

    Clause 4: guarantee of five years on the sealing layer, from handover.

  • 2024-02-02_MeierBau_Quote_RoofRenovation_v3.pdf

    The version that was signed, v1 and v2 are listed underneath.

  • 2024-01-24_Minutes_BuildingCommittee.pdf

    Where the scope was decided, with who was in the room.

Results respect the access rights already set on the folders. If you cannot open a document in your drive, it does not appear here.

How it gets better

It does not improve on its own.

Nothing learns quietly in the background. Accuracy improves in three ways, all of them visible to you.

Your corrections

When you change a name or a folder, that example is kept locally and used for the next document of the same kind.

Rules we tune

At the annual review we look at what you kept correcting and change the rules so you stop having to.

New model versions

Better models arrive in updates, tested by us first. Included, never billed separately.

Where it runs

Two places to put it. One product.

The same software, the same rules, the same review queue. Only the location of your files differs.

On your own server

Everything runs on a Mac mini on your network: reading, extraction, search index, review queue. Files never leave the building.

It's silent, roughly the size of a small book, and draws less power than a desk lamp. It sits in a cupboard. We bring it, install it, and it stays yours.

On your SharePoint or Google Drive

Your documents stay in the cloud you already pay for. DocHive connects through the official API and does three things: read, rename, move. Nothing is copied into a second system.

Existing permissions apply unchanged. If a folder is restricted to HR today, it stays restricted to HR.

What leaves the building

The honest list.

  • Your documents

    Never. They are read where they sit and stay where they sit.

  • A licence check

    Once a day. It carries a licence key and the software version. No filenames, no content, no metadata about your documents.

  • Cloud processing

    Only if you switch it on, and only for the difficult documents you send to it, bad handwriting, poor scans. Off by default, and it can stay off forever.

Your documents are never used to train any model, ours or anyone else's.

The data questions, answered one by one in the FAQ

Now that you know how it works, the useful next questions are which of your documents it handles and what it costs.

What it handles Pricing in full