One assistant. Two jobs done well.
For your team, Naxis is a colleague who has read everything and always shows their work. For your administrators, it’s a system that runs itself: sources sync on schedule, permissions enforce themselves, and every action is on the record.
Ask like you’d ask a colleague
Plain-language questions, conversational follow-ups, and answers grounded in your organisation’s own documents — with the sources right underneath.
- ✓Numbered citations. Click a source to read the exact passage the answer came from and verify it yourself.
- ✓Honest refusals. When the answer isn’t in the documents a person can access, Naxis says so — it never improvises.
- ✓Real conversations. Follow-ups understand the thread; a new topic is one click away.
- ✓Self-service privacy. Everyone can delete their conversations and export everything tied to their account.
Full-time employees receive 25 days of paid annual leave per year, plus public holidays. Unused days may be carried over until the end of March.[1]
1 HR Handbook § Leave policyNo — the office closure between Christmas and New Year is company-paid and not deducted from annual leave.[1]
Sources that keep themselves current
Connect the places your documents already live. Naxis sweeps each source on a schedule and updates the knowledge base to match — automatically.
- ✓Incremental sync. Each sweep diffs against the source, so only new, changed and removed files are processed. An edited file is re-indexed; an untouched one costs nothing.
- ✓Failure-safe. If a source can’t be reached — expired credentials, an outage — it’s flagged with the reason and its documents stay intact. A blip never empties your knowledge base.
- ✓Guided setup. Each connector is a short form with step-by-step instructions built into the product, plus a Test button before the first sync.
- ✓Readable errors. A document that couldn’t be processed shows a plain-language reason — replace it or remove it, no log-diving.
Groups decide who sees what
A group is a simple label — finance, hr, engineering. Give sources and people their groups, and Naxis enforces the rest at the database level, beneath the AI.
- ✓Enforced at retrieval. Restricted documents are filtered out of the search itself — the model never sees what the asker may not.
- ✓Open by default, restricted by choice. A document with no group is readable by all signed-in users; add groups to narrow it.
- ✓Clean deletes. Removing a group removes it everywhere at once — from every user and every document.
- ✓Permission changes are instant. Changing who can read a document doesn’t re-process it — access updates take effect immediately.
Invitations, not password lists
Add a person with their email and groups — that’s it. They receive a one-time activation link and choose their own password. Administrators never set or see anyone’s credentials.
- ✓Two clear roles. Users chat; system administrators also manage sources, groups, people and settings.
- ✓Full lifecycle. Resend invites, send reset links, disable accounts, or delete them — optionally erasing the person’s conversations for GDPR.
- ✓Works without email. Activation links are always available to copy from the admin page, so SMTP is optional — configure it later in Settings if you like.
- ✓Your name on it. Set your company name once and the assistant appears as “<Your company> Assistant” across sign-in, chat and emails.
The assistant grades itself on your corpus
Trust shouldn’t be a feeling. Naxis generates test questions from your own documents — including questions it should refuse — and reports how it scores.
- ✓Hit rate. How often the right document is retrieved for a question it should answer.
- ✓Refusal accuracy. How often it correctly declines questions it has no source for — measuring honesty, not just recall.
- ✓Runs in the background. Evaluations are background jobs; they measure the system and change nothing.
An audit log that can prove itself
Every sign-in, question, retrieval and admin action is appended to a hash-chained audit log. Each entry is cryptographically linked to the one before it — verify the whole chain with one click.
- ✓Append-only. Entries can’t be edited or removed without breaking the chain — and a broken chain is immediately detectable.
- ✓Pseudonymous. The log records opaque actor IDs and chunk references, not names and document contents.
- ✓GDPR tooling beside it. Retention schedules, per-person export (Art. 15) and erasure (Art. 17) live in the same Compliance area.
What it reads, from where
| Source | Authentication | What syncs |
|---|---|---|
| Google Drive | Service account (share a folder with it — one-time setup) | Files plus native Docs, Sheets and Slides; shared drives supported |
| OneDrive / SharePoint | Entra ID app registration, read-only Graph permissions | A OneDrive or SharePoint document library, optionally one folder |
| Dropbox | App access token or long-lived refresh token | Full Dropbox or a single folder |
| Amazon S3 | Read-only IAM access key, scoped to bucket and prefix | Objects under a bucket/prefix |
| Websites | None — public pages | Listed URLs and/or every page in a sitemap.xml |
| Direct upload | Admin UI | Word, text-layer PDF, Markdown, plain text |
Credentials are write-only once saved — they can be replaced but never read back through the interface. Read-only, minimally-scoped credentials are all every connector needs.
Thirty minutes, your documents
The fastest way to evaluate Naxis is to watch it answer on your own material. We’ll set up a demo corpus from documents you choose.