
I built a Paperless-ngx companion for AI metadata and owner assignment — looking for workflow feedback
I have been working on Archivista AI, a self-hosted companion that reads Paperless OCR text and writes back a title, tags, correspondent, document type, date, language, custom fields, and optionally an owner.
The part I most wanted to improve was setup: connect an existing Paperless instance in a browser, choose Ollama or a hosted/OpenAI-compatible provider, then inspect history and manually re-run documents from the UI. It supports OpenAI Flex and OpenAI/Anthropic batch processing for lower-cost, asynchronous workflows.
It runs as one Docker container with SQLite for processing history and retries. The published image is `ghcr.io/arturict/archivista-ai:1.1.0`.
Repo: https://github.com/arturict/archivista-ai (MIT)
Privacy boundary: local Ollama/OpenAI-compatible endpoints keep classification on your network; choosing a hosted provider sends the OCR content needed for classification to that provider.
I am looking for Paperless-specific feedback rather than stars: should generated values be limited to existing tags/correspondents/types, and what would make optional owner assignment feel safe enough for a household installation?
Disclosure: I am the author. AI coding tools assisted with parts of implementation, review, documentation, and testing, and the app itself uses the configured model for classification.