Memory you can trust an autonomous system with.
The more an agent can do on its own, the more its memory matters. Here is how Axonio isolates, encrypts and controls access to it, and where you can run it.
What protects your agents’ memory.
A database per workspace
In transit and at rest
Scoped, revocable API keys
Owner, Admin, Developer, Read-only
SAML SSO, or GitHub and Google
Activity you can review
Choose who holds the keys.
The same engine runs in every model, so moving between them is a data migration, not a rewrite.
| Model | Runs compute | Stores data | Holds keys | Best for |
|---|---|---|---|---|
| Axonio Cloud | Axonio | Axonio | Axonio | Most teams. Nothing to operate. |
| Dedicated cloud | Axonio, single-tenant | Axonio, single-tenant | Axonio or yours | Regulated workloads, custom regions. |
| Self-hosted | You | You | You | Data that can’t leave your VPC. |
| Embedded | The device | The device | You | Robots, edge and air-gapped sites. |
Found something? Tell us first.
If you believe you’ve found a vulnerability in Axonio, please report it privately through our contact page with “Security” in the subject. We’ll acknowledge it, keep you updated, and credit you if you’d like.
Security questions.
Is our data ever mixed with another customer’s?
No. Every workspace resolves to its own database instance. Isolation is enforced at the infrastructure level, not only in application logic.
Can we restrict what an API key can do?
Yes. Keys carry scopes, so a key given to a read-only integration cannot write or delete memory. Keys can be revoked instantly.
Do you support single sign-on?
Yes. Workspaces can connect a SAML 2.0 identity provider. Talk to us if you also need SCIM provisioning.
Can we run Axonio with no internet access?
Yes. The open-source engine runs self-hosted or embedded with no external dependencies. It only talks to Axonio Cloud if you configure sync.
What happens to our data if we leave?
Delete a workspace from settings and its databases, branches and objects are removed from active systems, with backups purged on a rolling schedule. The open-source engine means you can also export and keep running it yourself.
Can you complete our security questionnaire?
Yes. Contact us with your questionnaire or requirements and we will respond with our current controls and documentation.