Security and compliance
Built to be SOC 2 and ISO 27001 ready.
Agents handle real data and real money. Ahura OS is designed from the start around the controls auditors ask for: isolation, encryption, least privilege, audit trails and provable deletion.
“Ready” is not “certified”. Find out what “ready” means
SOC 2
Five criteria. One design.
The SOC 2 Trust Services Criteria describe what a trustworthy service provider does. This is how the platform approaches each.
Security
Protect systems and data against unauthorised access. Isolation, least privilege, encrypted keys that are never handed to agents, and full audit logging.
Availability
Run on managed, multi-zone cloud services with recovery built in, so one failure does not take agents offline.
Confidentiality
Keep each customer’s data in its own partition, encrypted, with defined retention and deletion.
Processing integrity
Every call is validated, metered and written to a ledger, so what ran and what it cost are on record.
Privacy
Collect and keep only what a partition needs, for only as long as you choose, and delete it on request.
Controls
What is in place.
Nine areas of control, each one built into how the platform runs rather than added on top.
Data isolation
- Every agent works in its own partition. Memory, files, records, graphs and workflows are scoped to it.
- Requests are checked against the partition that owns the data before anything is read or written.
- No shared tables of customer content that a bug in one agent could cross.
Encryption
- Data is encrypted in transit with TLS on every endpoint.
- Data is encrypted at rest in every storage service the platform uses.
- Frozen archives are encrypted the same way as live data.
Keys and identity
- Each agent and each partition has its own key pair, so actions are attributable.
- Private keys are encrypted at rest, used only inside the signing service and never returned by any call or written to a log.
- Signing is a service. Agents ask for a signature and never hold the secret. Anyone can verify one.
Access control
- Least-privilege roles for every component, scoped to the exact resources it needs.
- Staff access runs through single sign-on with role-based permissions, with separate roles per environment.
- Production is reached only through a controlled, scripted deployment path.
Environment separation
- Development, test and production run in separate cloud accounts, not separate folders.
- Shared services such as DNS and email sit in their own account.
- Identical, version-controlled infrastructure definitions are used for every environment.
Change management
- All code and infrastructure is in version control and every feature is documented as a numbered change request.
- Deployments are scripted and repeatable. There are no hand-edited servers.
- Changes are tied to a branch, a record and a reviewer.
Logging and audit
- Every call is validated, metered and recorded in a ledger with its cost and result.
- Agent actions are signed with the agent’s identity.
- Platform logs are retained for a defined period and alarms fire on errors.
Billing controls
- Per-agent spending limits are enforced by the platform, not by the agent’s instructions.
- Every call is priced up front and recorded in a ledger.
- Usage is metered against your account and card, and stops at the cap you set.
Availability and recovery
- Core data uses managed storage with point-in-time recovery.
- Compute is serverless and spreads across zones, so there is no single server to lose.
- Frozen partitions carry a manifest, so a restore is predictable.
Privacy partition mode
The LLM directs the work. It never sees the data.
Most connectors move your data to the model. In a Privacy partition the model is kept out of the data path entirely. Ahura OS separates LLM orchestration from the partition and its workflows, so the model gives instructions and the platform does the work next to the data.
- 01
LLM and agent
Decides what to do and sends instructions: read, parse, index, search, summarise. It never receives the payload.
- 02
Ahura OS orchestration
Workflows and tools run the instruction inside the partition, with the keys and data held there.
- 03
Privacy partition
Files, records and indexes stay put. Nothing moves to another partition, an outside system or the model’s context.
- 04
Answers and references
Only results and references go back, subject to a result policy. Held results wait for a person to approve them.
The LLM never sees the payload
Raw content is not placed in the model’s context. Tools that would return it are blocked or limited to references.
Orchestration stays inside
The model plans, Ahura Workflows and the partition do the work. Processing, search and GPU jobs run on the data in place, so it never has to travel.
Closed in both directions
A Privacy partition is never a source or destination for data moving to or from another partition.
Set at creation, fixed after
Choose Privacy when the partition is created, from the UI or by an agent. It cannot be changed afterwards.
People hold the controls
Uploading data, changing roles, changing the result policy and approving held results are done by a signed-in person in the UI. An agent cannot do them for itself.
Audited without exposing content
A metadata-only log records every instruction and every release, so you can see what was asked without the content being copied into a log.
Good for contracts, medical records and customer data. Results returned to the agent are answers and references, so what you ask for still shapes what the model learns. Use the result policy to control it.
ISO/IEC 27001
Mapped to the four control themes.
ISO 27001 Annex A groups controls into four themes. Here is how each is addressed.
- Organisational controls
- Documented change requests, defined environments and roles, supplier reliance on audited cloud infrastructure, and an incident and recovery approach built into the platform.
- People controls
- Role-based staff access through single sign-on, least privilege, and separation between development and production duties.
- Physical controls
- Inherited from the cloud provider’s audited data centres. Ahura OS does not operate its own facilities.
- Technological controls
- Encryption, protected signing keys, network and identity controls, logging and monitoring, secure configuration through code, and tested backup and recovery.
Data retention
You decide how long data lives. Then it goes.
Keeping data forever is a liability. Every partition has a lifetime, and everything in it follows that lifetime from creation to deletion.
TTL on everything
Every record, object and index entry can carry a time to live, and expiry is automatic.
Partition lifetimes
A partition has a lifetime and a retention window. At expiry it is destroyed, including everything inside it.
Freeze, don’t keep running
When work pauses the partition freezes to encrypted archive, so data is retained without being exposed to live access.
Destroy means destroy
Destroying a partition removes its data and returns any permanent-storage credit still owed.
No data held hostage
Running out of credits locks a partition read-only. A 7-day grace period follows, and state is archived before any teardown.
Retention you can show
The retention period, the freeze and the deletion are recorded, which helps with deletion requests and audits.
Shared responsibility
Ahura OS runs on audited cloud infrastructure and inherits its physical, hardware and network protections. On top of that we secure the platform itself. You remain responsible for what your agents are told to do, the limits you set, and the data you choose to store.
Keep going
See how partitions keep data isolated and retained, or connect an agent and try it.
What “ready” means
The platform is designed and operated to align with the SOC 2 Trust Services Criteria and the ISO/IEC 27001 controls. It is not a certificate or an attestation report, and we will say so plainly when an independent audit is complete.
SOC 2 is a trademark of the AICPA and ISO is a trademark of the International Organization for Standardization. This site is not endorsed by either, and the badges on this page are our own artwork.