Built for data that can't go anywhere else
This is what the product does today: where your data lives, who can reach it, and what gets written down when they do.
Models run on your side
Answers and search embeddings are produced by models running inside your environment. Hosted models are supported as an option, but they stay off until an administrator turns them on and approves the host.
Works without internet
The platform can run on a network with no outside access. It's packaged as an offline release, and the model files are brought in by hand.
Department walls in the database
Every query that touches documents is filtered by department in the data layer, not in the screen you're looking at. We run a cross-department test suite that tries to break this, and it runs with every build.
Six roles
Admin, Department Admin, Analyst, Viewer, Auditor and Executive. A Viewer can't upload. An Auditor can't open documents. An Executive can't change settings. Only Executives and Admins read across departments.
An audit log that stays put
Sign-ins, failed logins, uploads, deletions, user changes and questions are recorded against a named user. The application's database account can add to the log but can't edit or remove entries.
Locked-down service accounts
The application connects with a role that has only the permissions it needs. Migrations run under a separate owner account.
Sign-in protection
Ten wrong passwords within thirty minutes locks an account. Microsoft single sign-on is supported, and a linked account can be set to sign in through SSO only.
Backups, tested
Backups run nightly and the last fourteen are kept. A restore drill runs weekly, because a backup you've never restored is only a hope. Admins get an alert when something looks wrong.
A license tied to your install
The license file is signed, checked offline and bound to your installation. If it expires the platform goes read-only: questions still work, uploads stop.
Try it on your own documents.
Bring a few reports and a question you've had trouble answering. We'll work through it with your files, not ours.