Technical overview

For IT teams.

What an IT team needs to know before Ax0s goes on a server: what it connects to, where it runs, who can see what, which models it uses, and who backs it up.

Revised November 19, 2026

1How it fits together

Where it runs.

The connectors bring in records from your cloud systems. The memory and its storage stay on your server.

2Connections

What it connects to today.

Checked November 19, 2026. A connection we have only tested ourselves is listed as that.

Running today

In daily use on Ax0s’s own accounts. Not yet deployed for a customer.

  • Gmail
  • Google Calendar
  • Google Drive
  • Fathom (call recordings)
  • SignWell (e-signatures)
  • Stripe
  • Mercury (banking)

Built, in pilot testing

The code is written and passes its tests. It has not run on a customer account yet. These connectors only read: they refuse any request that would change your data, and they report ‘unknown’ instead of a wrong zero.

  • HaloPSA: clients, prepaid hour blocks, tickets, time entries, invoices, payments
  • ServiceNow: clients, contracts, tickets, time worked
  • QuickBooks Online: customers, invoices, payments, credit memos
  • Microsoft 365 mail and calendar
  • Microsoft 365 directory: users and licenses
  • OneDrive and SharePoint files

Next

Planned. Some need the vendor’s approval before we can test them.

  • ConnectWise PSA
  • Autotask
  • Microsoft Teams messages

Not planned for now

Several of these vendors restrict API use or can’t limit access to read-only.

  • RMM tools
  • Backup consoles
  • IT documentation tools
  • Distributor portals
  • Slack

Anything else is custom work. Tell us the system and we’ll tell you what it takes.

3Who can see what

Today, everyone who uses an Ax0s installation can see everything connected to it.

Ax0s does not yet carry over each person’s permissions from the systems it reads.

So connect only the records that everyone using that installation may see. Keep payroll and confidential management files out, or put them on a separate installation.

Each client gets its own Ax0s installation. We do not put two clients on one.

In place today

  • Each access token reaches only the memory spaces and tools it was granted: implemented
  • Access tokens expire: implemented
  • Access tokens can be revoked: implemented
  • Rate limits for each person or program that holds a token: implemented
  • A request for a memory space or tool the token was not granted is refused: implemented
  • Access-audit records: best-effort; coverage and exceptions described under Logging
Logging, on the Security page

Not established

  • Permissions on individual records: not established
  • Hardened separation of several clients on one installation: not established
  • Sign-in controls checked by an outside party: not established

4Models

Sensitive work can run on a local model on your server.

If you turn on a model provider’s API, the question and material from connected records go to that provider, under the business’s own account and API key. Nothing goes to anyone’s personal AI account.

5Backup and recovery

Optional backup tooling sends encrypted restic snapshots off the server.

The operator, whoever runs the server, chooses how long to keep them and is responsible for recovery.

Encrypted off-host backups

Optional deployment tooling

Where
Operator-selected S3-compatible storage
Receives
Encrypted restic snapshots of memory, ingest state and selected configuration
Control
Operator and backup provider

Backup and restore

documented

Optional deployment tooling sends encrypted restic snapshots off-host. The operator chooses retention and is responsible for recovery tests; no tested full-restore claim is made here.

Retention and recovery

Ax0s supplies
Optional restic backup and retention tooling
You control
Retention, backups, restoration tests, and disposal
Outside provider receives
Encrypted snapshots when the operator enables off-host backup

Upgrade path

not yet documented

No public compatibility or rollback promise is published.

At-rest encryption

not supported

No established application control is claimed; filesystem and volume protections are operator choices.

Before you start, agree who manages the server, who pays for the server and model use, and who runs and tests backups.

6Support

The MSP’s help desk takes the first call.

Anything it can’t resolve comes to us.

7Independent review

No outside audit, certification or compliance assessment has been done yet.

This page is not one.

What stays, what can leave, and what we don’t claim