Support and evidence matrix
“Implemented,” “supported,” and “release-proven” are different claims. This page separates the configured boundary from the evidence currently available so an operator can decide what still needs local evaluation.
| Capability | Current boundary | Evidence and maturity | Important exclusion |
|---|---|---|---|
| Deployment ownership | One Jiandu process per installation | Enforced topology and installation lock | No active-active replicas or scale-out workers |
| Local evaluation | Loopback HTTP at 127.0.0.1:8077; reviewed local Caddy HTTPS example | Implemented; quickstart supplies an end-to-end path | Source-built only; no published release package |
| Household network access | HTTPS reverse proxy to a private Jiandu listener | Contract and examples exist; composed browser release evidence remains incomplete | No non-loopback plaintext deployment |
| Database | SQLite default; PostgreSQL 17.x and 18.x external database | Guarded backup/restore round trips exist for both backends and both supported PostgreSQL majors | No PostgreSQL 16 or older, PostgreSQL 19 or newer, multi-process use, or cross-backend conversion |
| Document blobs | Local disk; S3/S3-compatible; WebDAV including ownCloud/Nextcloud | Adapters and backend-independent backup verification exist | No supported migration of an existing installation between blob backends |
| Browser document work | Add, review, search, organize, archive, trash, restore, and download | Implemented browser surfaces; verify with representative local files | Scanned-text recognition is not an advertised guarantee |
| Human sign-in | Local password; optional passkey; OIDC; TLS-protected LDAP/AD; protected trusted-proxy assertion | Implemented; full real-provider admission and browser release evidence remains incomplete | No SAML, SCIM, or provider-to-role mapping |
| Access administration | Browser management of members, local accounts, invitations, and delegable direct roles; native API for groups, custom roles, and per-document Viewer/Editor/Manager grants | Implemented browser and API surfaces; People and access describes the split | Group and custom-role administration, PATs, and document grants remain API-only |
| Automation sign-in | Scoped personal access tokens with a 90-day default and 365-day maximum | Native API implemented | PATs are not browser sessions and never bypass household or document access |
| Browser upload | PDF, JPEG, PNG, and plain-text advertised inputs | Resumable intake and component evidence exist | Former-limit-exceeding release matrix remains incomplete |
| Watched folder and scanner capture | Dedicated watched roots, eSCL/AirScan, outbound Linux/SANE agent | Implemented surfaces and component evidence | Real watch-folder and scanner journey release evidence remains incomplete |
| Email capture | Gmail API read-only access; supported PDF attachments | Native connector API implemented | Browser administration absent; loopback consent, message mutation, and non-Gmail providers unsupported |
| Cloud folder capture | Read-only Google Drive, Dropbox, and OneDrive; recursive periodic ingestion | Native adapters, durable capture, and browser management implemented; setup guide | Operator-provisioned OAuth grants; no cloud-native exports or bidirectional sync; live-provider evidence pending |
| Paperless-ngx migration | Extracted supported export directories on SQLite | Candidate, component-tested profile; release evidence incomplete | No drop-in compatibility, ZIP/data-only input, or PostgreSQL importer |
| Recovery backup and portable export | Guarded SQLite and PostgreSQL 17/18 workflows | Live round-trip evidence exists; the promoted Compose topology includes an isolated executable drill | Restore uses the same database backend and PostgreSQL server major plus a new local blob layout; no browser restore workflow or cross-backend restore |
| Saved quick filters | Personal live searches that retain query, filters, shelf, and sort; up to 24 per member | Implemented browser workflow; quick-filter guide provides a verification path | Saved criteria do not grant access or freeze the matching documents |
| Notifications | Durable Activity inbox and optional browser notifications while the page is open | Component-tested; notification guide covers preferences and verification; release evidence incomplete | No background web push |
| Smart filing | Explainable proposals, explicit acceptance, reversible rules | Implemented policy and component behavior | Restricted documents do not train household-global rules |
| Remote telemetry | Off by default; bounded OTLP/HTTP after explicit consent | Configuration and privacy contract implemented | No remote telemetry by default |
| Plugins | Versioned contract, SDK, validators, and authoring harness | Authoring contract exists; reduced-isolation runtime is opt-in and disabled by default | Registry and unreviewed packages are unsupported; only owner-reviewed local packages may run |
| License | No license selected | Public documentation records the blocker | Default copyright applies; do not assume reuse or redistribution rights |
Support means the repository contains an explicit current contract. It is not a blanket production-readiness, performance, security-certification, or compatibility claim. Test the exact database, blob, identity, ingress, capture, and recovery combination you intend to operate.
For a shorter decision guide, read scope and readiness. For current settings, use the configuration contract.