Why Jiandu

Important papers tend to arrive through many channels: downloads, scans, email attachments, and physical mail. Jiandu gives them one private home without asking you to hand control to a hosted document service.

Jiandu is designed around a few practical promises:

• You retain the originals. A filing or processing problem should not take the source document away from you.
• The default is private. A new installation listens only on the local machine and does not send telemetry to a remote service.
• The normal path is understandable. Members can add, find, tag, and correct documents without learning the storage or database layout.
• Power remains available. Administrators can choose storage, authentication, capture methods, monitoring, and recovery procedures.
• Automation stays accountable. Suggested filing rules remain visible and reversible, and manual corrections win.

These promises describe design intent and implemented boundaries, not a blanket maturity claim. For exact current combinations and exclusions, use the support matrix.

What it feels like to use

A member opens Jiandu in a browser, adds a document, checks its title and filing information, and can later find it by browsing or search. Shared documents are visible to the household by default. Exceptional documents can be restricted to named people or groups.

An administrator looks after the installation: deciding how it is reached, where data lives, how people sign in, and how backups are tested. Jiandu deliberately makes those boundaries explicit instead of guessing.

Is Jiandu a fit?

Jiandu may fit if you are comfortable operating a small self-hosted service and want a household-first document library. Read scope and readiness before treating it as the only home for important records.

If you are comparing products, choosing self-hosted document management provides a vendor-neutral trial based on retrieval, access, export, and restore evidence.

Next: Choose an installation path.