Trust · Security & compliance
It comes before everything else, and it is built in, never bolted on: your own instance and your own database, access enforced inside every query, an audit chain that proves itself. Everything on this page is a shipped mechanism, and the trust library puts it in writing, readable right here.
There is no shared platform. Each client runs their own instance with their own database; documents, conversations, permissions and audit records never share storage with anyone else's.
Single-tenant per client, by decision, not a configuration option; there is no multi-tenant mode to misconfigure.
One PostgreSQL carries the index, conversations, audit log and job queue: one backup scope, one encryption scope, one data map.
Connector and channel secrets are accepted, used, and never displayed again.
Each platform's own signature scheme is verified before any processing; unverified calls are rejected.
Under our management in the EU, or self-hosted on your own Linux server, the same product either way.
Indexing runs entirely inside your deployment, always. Self-hosted, answers stay home too, on your own hardware. On the Naxis AI service, only the question and the permission-filtered excerpts travel: zero retention, no training, in writing, and no AI keys on the instance at all.
The safety record, in writing ›
The group filter lives inside every database query the assistant makes, on every channel and API; no surface runs above it. And every consequential event lands in an append-only log where each entry carries the hash of the one before — nothing edits, nothing deletes, verification is one click.
How permissions work ›
One pipeline gates every release: static checks, the full suite, a signed, sealed artifact, and a failed health check rolls itself back. Another watches the fleet continuously — edge defence, throttled sign-ins, signed heartbeats, short-lived leases. Managed and self-hosted install the identical, verified artifact.
Request the architecture record ›
Export is self-service, erasure is deletion — store and index alike, no tombstones — and each deployment generates its Article 30 record from live configuration. Under the EU AI Act the assistant declares itself on every surface, and high-risk uses are contractually excluded: the position, article by article.
The GDPR mapping, article by article ›
GDPR and the EU AI Act are built into the product; the control themes ISO 27001 and SOC 2 expect are shipped mechanisms today. Each framework keeps a status page that answers plainly, station by station — nothing is claimed before it is held; the SOC 2 page carries its current status.
The ISO 27001 track ›
The architecture record, the data-processing agreement, the answered security questionnaire: file a standing request from your account and each lands on your own thread the day it exists. Answers come from the architecture, never a script.
Open the document desk ›
The documents reviewers ask for, frameworks, legal structure, technical record, readable on this page, no request forms in the way. Signed copies are an account request away.
The rights articles as product mechanisms: export, erasure, records of processing, each one built in, none of it paperwork after the fact.
Every Naxis deployment is a single-tenant system processing only the client's own documents, on infrastructure the client chooses. GDPR compliance is implemented as product mechanisms, not policies:
The generated manifest for a specific deployment is available to its administrator at any time; a sample is in Technical documentation below.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
Transparency by construction: AI-interaction disclosure on every surface, an AI-literacy resource in the product, high-risk uses contractually excluded.
The control themes the standard expects, access control, cryptography, operations security, supplier relationships, are shipped mechanisms described in Technical documentation.
The system is built and operated in line with what the standard asks of an information-security management system; the certification itself is what we are waiting on. The control themes, as the mechanisms that ship in every deployment:
Its own page carries the current status. File a standing request from your account, and security questionnaires are answered directly from the architecture in the meantime.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
The trust criteria, security, availability, confidentiality, privacy, run as engineered product mechanisms; the SOC 2 page carries the current status.
The system operates to the trust services criteria as engineered mechanisms, evidenced on its own audit chain; the report itself is what we are waiting on. Criterion by criterion:
Its own page carries the current status. File a standing request from your account, and security questionnaires are answered directly from the architecture in the meantime.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
The DPA every deployment is contracted under, subject matter, duration, sub-processor notice procedure, audit rights, deletion on termination.
The signed DPA is executed per client. Its structure, so your legal team knows what to expect:
Request the full template, or a signed copy for review under NDA, through the contact page; it is provided as a matter of course.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
At most two categories exist, and the fullest configuration, self-hosted with self-hosted AI, has none.
Changes to either category follow the DPA's written notice procedure. There are no analytics, advertising or telemetry processors, the product ships none.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
One client, one deployment, one boundary, what that means concretely: containers, database, credentials, the AI boundary and the audit chain.
Each client runs their own complete instance: application, worker, database and document store in isolated containers on a machine that serves no other client. There is no shared platform, no pooled database, no cross-tenant anything, isolation is the deployment model, not a configuration option.
Indexing (reading and preparing documents for search) runs entirely inside the deployment. Generation follows the deployment's configuration: the fullest posture is a self-hosted deployment that answers entirely on its own hardware, where nothing leaves the boundary at all. Deployments using the Naxis AI service send the question and the permission-filtered excerpts (zero-retention terms, see sub-processors); the model never sees documents the asking person cannot see, because permission filtering happens before the request leaves.
In every configuration: your data is not used to train models, and nothing is retained after the answer returns.
Access is group-based and settled before a question is even considered, everywhere the assistant answers, never in any one surface. Accounts activate by invitation link; administrators never see or set a password. Channel guests receive nothing until groups are explicitly opened to them.
Every consequential event, questions, answers with their citations, administrative actions, syncs, erasures, lands on an append-only, hash-chained log. Verification recomputes the whole chain on demand from the console; a broken link is impossible to hide. Rows cannot be edited or deleted; retention prunes whole aged spans and records that it did.
Releases are versioned images; deployments install them in a quiet window after a safety backup and roll back on their own if the health check fails. What changed in each release is shown in the console in plain language.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
What leaves the deployment, what never does, and where things physically live.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
Every deployment renders one of these from its own live configuration, this is the shape of it.
Generated, not written: the values below come from a deployment's actual configuration at generation time.
Administrators export the real manifest for their deployment from the console at any time.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
Need something that isn't here yet? Name it from your account or ask directly, security questionnaires are answered from the architecture, not a script.
Compliance is implemented as product mechanisms, not policies: self-service data export (Art. 15/20), hard-delete erasure that removes records from store and index alike (Art. 17), a DPA with a sub-processor notice procedure (Art. 28), and a record-of-processing manifest each deployment generates from its own live configuration (Art. 30). The details are readable in the trust library on this page.
Each client runs a single-tenant deployment, own instance, own database, in an EU data centre under our management, or on your own servers. Documents at rest, the index, conversations and the audit log never leave the deployment. Nobody at Naxis reads inside your instance without a consent you grant per support ticket.
Self-hosted install, what it needs Request the architecture record
No, in any configuration. The fullest posture keeps everything home: a self-hosted deployment that answers entirely on your own hardware, where nothing leaves your boundary at all. Deployments that use the Naxis AI service instead send only the question and the permission-filtered excerpts, nothing is retained after the answer returns and nothing trains any model, in writing, under zero-retention terms.
The control work behind both standards is shipped and reviewable on this page, and each keeps its own status page that answers this plainly, station by station. Nothing is claimed before it is held; file a standing request from your account and each artifact reaches you the day it exists.
Yes, from the architecture, not a script. File it as a document request from your account (or send it through the contact page) and the answers come back on your own thread.
Every paste into a consumer chatbot is a question your own systems could not answer fast enough. Security vendors sell detection, which reads the app and never the question. What the 2026 breach data actually shows, how far Microsoft's new Shadow AI controls really reach, and why the only fix that scales is making the company answerable.
Glean is Google for your company: it finds where things are stored. Naxis is the private knowledge engine that knows what is actually true right now. Different machines, different questions, different prices. An honest way to choose, and the Glean alternative for companies of 5 to 200 people.
Lidl wrote off €500 million trying. Birmingham City Council is £144 million in and reinstalling from scratch. Consolidation megaprojects fail for a structural reason: real work is too fluid to hold one shape. The part you actually wanted, one place to ask, never needed the migration.
