A self-hosted AI document archive for private multi-user deployments.
NeoArchive stores and analyzes your documents on infrastructure you control. It keeps originals encrypted, extracts searchable text, recognizes document metadata, and exposes the same data safely through the app, the REST API, and an authenticated MCP surface.
npm install -g neoarchive
neoarchive install
neoarchive setup
neoarchive startOpen http://localhost:4400, create the first user account, and sign in to the admin area at /admin
with the administrator credentials configured during setup.
- It is self-hosted and privacy-first. Documents, OCR text, metadata, sessions, and backups remain on your server instead of being forwarded through a third-party relay.
- Each user gets isolated storage and encryption. The app uses envelope encryption with a server-held master key, per-user data keys, and per-file wrapped keys.
- AI is assistive, not authoritative. NeoArchive extracts and suggests titles, senders, dates, summaries, and document types, but manual edits remain the final source of truth.
- Search is built for archives, not folders. Full-text search, OCR, labels, authors, document types, and semantic search all work together on the same document index.
- The API and MCP surfaces match the app boundary. The same services power the Flutter client, REST API, and MCP tools, with per-user auth and scope checks enforced consistently.
NeoArchive is intended for trusted self-hosted deployments. Review the security boundaries before exposing it to a network or importing sensitive documents.
- Getting started
- Documents and search
- Security and 2FA
- Architecture
- API and MCP
- Encryption
- Running in production
AGPL-3.0