Start
Hosted by Naxis
A managed deployment runs on infrastructure Naxis operates. There is nothing to install and nothing to maintain — you just open it and create your account. This page covers what “managed” actually means day to day: who does what, your address, updates, support, and your data.
Getting in
- Open your welcome email. When your deployment is ready, Naxis emails you its web address.
- Create your administrator account. The first person to open it becomes the admin.
- Follow the setup wizard — name your organisation, connect your first content, invite your team.
Your address
Your assistant is served at a Naxis subdomain (for example
yourcompany.naxistechnologies.com) with HTTPS already in place. If you’d
like it on your own domain instead (for example assistant.yourcompany.com),
attach it yourself from your account area: add the DNS record it shows you, and the
certificate is issued automatically once the record is seen — both addresses keep
working afterwards. The full procedure, including the exact DNS record, is at
Use your own domain.
Who does what
Naxis runs the server, the database, the reverse proxy and the certificates; you run the assistant itself, exactly as an administrator on a self-hosted deployment would — same console, same connectors, same access rules, same audit trail. Nothing about day-to-day administration changes: you connect sources, manage users and groups, and read the audit log yourself. What you never touch is the machine underneath it.
Updates & backups
Updates install themselves. When Naxis publishes a new version, this deployment learns of it at its next check-in and the admin console announces it in Settings; unless you choose otherwise it installs on the coming Sunday at 02:00, in your deployment’s own local time. Update now installs it within a minute or two instead, and you can otherwise move the date earlier but never later than the deadline shown.
- A database backup is taken first — the update doesn’t run if it can’t be.
- The new version starts and must pass its own health check.
- Healthy, and the update is done — usually a minute or two of downtime. Not healthy, and the previous version is put back automatically; your data is untouched.
On top of the backup every update takes, Naxis also keeps its own nightly database backups of every managed deployment, independent of updates — recent nights plus the first of each of the last few months. If a deployment ever needs attention outside an update, Naxis sees it and acts before you have to report it.
Getting help
Open Help inside the assistant and use the support button — a person reads every ticket, there is no bot triage, and replies land in the same thread both in the console and by email. A report is fastest to act on when it carries:
- What you were doing, and on which page.
- What you expected, and what happened instead.
- When it started, and whether it happens every time.
- The exact text of any error message.
If a problem needs someone to actually look inside your assistant, the ticket form asks for that permission explicitly — a checkbox that lets support sign in for this ticket only, with an optional temporary login you provide. Nothing of the kind happens without that recorded consent, and you can withdraw it at any time while the ticket is open.
Your data
From Settings → Security & privacy you can export any one person’s data, or erase any one person or document, at any time — the same controls a self-hosted administrator has, run from the same screen. There is no separate “wipe the whole deployment” button; erase or export person by person, or document by document, from there.
Moving to self-hosted later
The assistant itself is identical between hosting modes, so nothing about how you use it needs to change. There is no self-serve, one-click migration from managed to your own server today — open a ticket from Help and Naxis will talk you through moving your deployment across.
Everything else works the same
Whether hosted by Naxis or on your own server, the assistant itself is identical — same admin console, same permissions, same channels. Continue with Using the assistant.
Last updated 3 Sep 2026