Built for the security review.
What a reviewer asks, and what the platform does today.
- Where the data lives
- One customer, one server, one domain, with its own database and keys. The region is agreed before implementation and EU regions are available. Restricted-network and offline installs are supported.
- Encryption at rest
- Messages, bot instructions, prompts, memory, tickets and files are encrypted before they reach the database, with per-space keys wrapped by a master key you can rotate. Names, timestamps and ids stay readable so the system can search and sort.
- Human oversight
- A person approves first go-live and anything that reaches production. A bot can pause to ask a person, request a takeover or request a secret, and the run waits for the answer.
- Outbound data
- Outside content is treated as untrusted. After a run has read it, new websites and unused connectors need approval. Runs with nobody to ask refuse new sites.
- Access control
- Invitation-only teams with owner, admin and member roles. A member's private chats cannot be read, searched or exported by owners or admins, and there is no override.
- Audit trail
- Admins read the team activity log. Audit logging, SSO and bring-your-own-key are part of the sovereign option.
- Isolation
- Risky code runs in its own Firecracker microVM with its own kernel. Each bot keeps its own browser profile, and secrets are stored encrypted.
- Your model
- You connect the model provider you already use, so you can pick one that fits your data policy. On mobile, data sharing needs consent per account, space and recipient.
- Current limits
- It is in beta. A bot's computer can reach public websites, so network and approval rules are agreed with you before go-live.
Questions.
Can it run on hardware we control?
Yes. The sovereign option runs on hardware you own or control, on-prem or air-gapped, with bring-your-own-key, SSO and audit logging. Anviq can stand it up and operate it, or hand it over.
Can our admins read our staff's chats?
No. Private chats with a person's own bots cannot be listed, read, searched or exported by owners or admins. Admins can read the team activity log and manage company memory.
Is the source code open?
The repository is public on GitHub. It includes upstream code under Apache 2.0, while Anviq's own additions are proprietary and need written agreement for use.
Bring your security questionnaire.
We answer it on the call, against your own policy.
Book the free fit call