Security & compliance · ISO/IEC 27001
We are working toward ISO/IEC 27001 certification. It is not yet held, and nothing on this page claims it. What you can do today: assess the shipped controls yourself, and file a standing request so the certificate reaches you the day it exists.
No promised dates — a date named before the internal audit closes would be theatre. Here is the track itself, exactly where it stands; the state of the work is shareable at any time from your account.
Done. The ISMS scope is drawn around how the product is built, released and operated; the gap list is the work plan.
Done. Annex A controls implemented and generating evidence — most live in the product and pipeline, documented below.
In progress. The ISMS is audited against its own scope before anyone external looks; findings feed back into the controls.
Then. An accredited body examines the ISMS; the certificate lands on this page, and with everyone whose request is standing.
Scoping and gap analysis are done, the controls are live and generating evidence, and the internal audit is under way. The certification body is named here when the audit is engaged; we do not pre-announce a name we have not contracted. Request the current state any time: which stage is in progress, what evidence exists, what remains — the real state, never a glossy roadmap.
Request the current state ›
Access control lives inside every query. Development security is the release gate: static checks, the full suite, signed artifacts. Cryptography seals secrets server-side and signs releases, heartbeats and leases. Supplier relationships stop at two sub-processor categories, or none. Operations security is one database per client with automatic rollback; incident readiness is signed heartbeats and revocable leases. Each theme is documented in the trust library — no certificate required to verify a mechanism exists.
Read the trust library ›
The ISMS covers how we build, release and operate the product and the managed fleet. A self-hosted deployment runs the identical signed artifact on your infrastructure — your own physical and network controls apply there, and the product controls travel with it. One pipeline gates every release, and a failed health check rolls itself back.
Self-hosted install, what it needs ›
The track’s papers, readable right here — the ISO 27001 status, the architecture record, the data-flow note and the sub-processor notice. The certificate joins them the day it is held.
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.
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.
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.
File a standing request from your account and the certificate reaches you the day it exists; security questionnaires are answered from the architecture, not a script.
Not yet. We are working toward ISO/IEC 27001 certification and say so plainly, no certificate is claimed anywhere on this site until one is held. The control themes the standard expects are shipped, assessable mechanisms today.
Many organisations do exactly that: assess the controls directly, the architecture overview, the trust library, your own questionnaire answered from the architecture, sign the DPA, and file a standing request so the certificate reaches you the day it exists.
Yes. Request it from your account and you get the current preparation state on your own thread, which track stage is in progress, what evidence exists, what remains. No glossy roadmap, the real state.
An accredited certification body, named on this page when the audit is engaged. We do not pre-announce a name we have not contracted.
The ISMS covers how we build, release and operate the product and the managed fleet. A self-hosted deployment runs the same signed artifact on your infrastructure, your own physical and network controls apply there, and the product controls travel with it.
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.
