Skip to main content

Jiandu documentation

Install a private document library, find your household's records, or build an integration. Start with the task you need to complete, then use the reference pages for exact settings and API fields.

Start here​

Your goalStart withFirst result
Evaluate or install JianduDocker Compose quickstartA running installation and one verified sample
Use an existing household libraryJoin your household's JianduYour own sign-in and a document you can open
Connect an automation clientNative API quickstartAn authenticated request with a scoped token
Move from Paperless-ngxMigration guideA checked sample import with exceptions reconciled
Current maturity

Jiandu is evolving software, publishes source-built deployments, and does not yet have a project license. Evaluate with non-critical samples and read scope and readiness before relying on it for important records.

Repository access required

The source repository is not anonymously accessible at the time of writing. A 404 from the clone URL means this source-built evaluation path is unavailable; Jiandu currently has no public package fallback.

Work with documents​

See Using Jiandu for a suggested learning order and checks for each task.

Set up and operate the household​

TaskGuide
Choose an installation methodInstallation
Set up HTTPS, storage, a database, or sign-inConfiguration
Create accounts or invitationsPeople and access
Add a watched folder, scanner, or Gmail connectorCapture and email
Back up and rehearse recoveryBackup and restore
Check readiness before wider useDeployment checklist
Investigate a failed operationTroubleshooting and error messages

Jiandu runs one process per installation. A complete backup protects the database and every referenced blob together. Read how Jiandu works for the relationship between originals, filing data, processing, search, and access; use the support matrix to check your intended combination before adding integrations.

Build and look up details​

Choose the matching documentation version​

The Latest (main) docs describe the current main branch. A major release tag publishes a durable N.x snapshot, which remains selectable from the version menu after main moves on.

Use the version selector before copying a setting or API example into an older installation. Generated API pages and release-pinned JSON contracts are authoritative for their matching version.

For text-oriented tools, use the Latest documentation index. Its Markdown pages describe Latest (main); use the versioned HTML and matching JSON contracts for an older installation. To propose a correction, authorized repository members can follow Writing documentation.