Self-hosted document management
Self-hosted document management for your household.
Jiandu keeps important PDFs and images in one searchable archive while you control where originals live, who can reach them, and how the installation is recovered.
Remote telemetry off No hosted account Originals preserved
JHousehold archivePrivate
Search titles, senders, tags, and document text…
Archive ready3 documents · 0 need attention
Built around a household archive
Own the document, the boundary, and the recovery plan.
Your archive, your storage
Store originals on local disk, S3-compatible storage, or WebDAV. Jiandu does not require a hosted account.
A practical browser workflow
Add, review, search, organize, archive, restore, and download household documents without turning filing into a second job.
Recovery you can rehearse
Create a guarded recovery backup, verify every referenced object, restore into a new destination, and prove the result before relying on it.
Know where each job lives
A useful browser, an explicit API, and operator-owned infrastructure.
Everyday document work
PDF, JPEG, PNG, and text intake; filing review; search and saved quick filters; Activity notifications; bulk organization; archive, restore, and download.
Access and automation
Local accounts, roles, groups, expiring personal access tokens, per-document grants, API access to capture operations, and Gmail connector administration.
Deployment and recovery
Loopback evaluation or reviewed HTTPS proxying; SQLite or PostgreSQL 17/18; local, S3-compatible, or WebDAV blobs; guarded backup and restore.
Manage members and invitations in Settings. Groups, custom roles, document grants, personal access tokens, and Gmail connector setup use the native API. Watched-folder, scanner, and capture-agent setup is available in the browser and API. Browser uploads can resume across transport or server interruption while the page retains the selected file; closing or reloading the page loses that browser file handle.
A testable first hour
Go from checkout to a verified first document.
The recommended evaluation path states its prerequisites, keeps Jiandu behind local HTTPS, creates the first account without printing the Owner token, and links the separate operator procedure needed for a real recovery drill.
Follow the quickstart →- 01Start the reviewed topology
Build the Caddy-based Compose example, trust its local certificate for evaluation, and create the first human Administrator with the bounded helper.
- 02Prove one document
Add a non-sensitive original, correct its filing data, search for it, and open the downloaded result outside Jiandu.
- 03Plan the recovery drill
Preserve the separate Owner credential, then follow the operator guide to back up, restore into an isolated destination, and record the result.
Reviewed local evaluation
Build it, then create the first human safely.
The current path builds from a source checkout and requires repository access. Start with non-sensitive files; no release package is published yet.
Prerequisites and verification →git clone https://github.com/zhyuri/jiandu.git
cd jiandu
docker compose -f examples/docker-compose/docker-compose.yml up --build
# In a second terminal:
./examples/docker-compose/bootstrap-local-account.shCompare the operating model, not just the feature list.
See where Jiandu fits beside Paperless-ngx, Nextcloud, Mayan EDMS, and a plain file archive—and where another tool is the better choice.
Read the decision guide →Operate it without guessing what “supported” means.
The evidence matrix separates implemented contracts, browser surfaces, component tests, release evidence, and current exclusions.
Open the evidence matrix →Start with evidence
Open the quickstart