SaaS
A cloud perimeter with a choice of hosting region. Suits individuals and organizations without strict localization requirements.
SecurityPermissions, confirmations, audit
Authority, confirmation
and proof for every action.
The ecosystem gets access to other people's systems, so security here is not a documentation section but a working condition: without verified authority an action doesn't run, and without a recorded result it doesn't count as done.
8 levelsFrom identity to proof
Hover or focus a level to read its role. Each level acts independently and is never cancelled by the others.
Hosting
Where the data lives
The default hosting region is Russia, with a choice available. The customer picks the delivery format.
Self-hosted
Full deployment in the organization's infrastructure: apps, data, logs and models stay inside the perimeter.
Hybrid
Interfaces and communications in the cloud; sensitive data and models inside the organization's perimeter. Linked via a controlled gateway.
Tenant isolation
Multi-tenant by default; a dedicated perimeter and self-hosted on request.
Privacy
Personal contexts are inaccessible to the employer. Agent memory is bound to a context and never moves without consent.
Export and deletion
Export of documents and legally required data, deletion within the approved policy.
Trust levels
Not every connection is equal
The trust level defines which operations an extension, agent or connection may perform.
A verified Store extension
Passed automated and manual review: contracts, requested permissions, behavior and compatibility. Installed by an administrator with explicit permission confirmation.
A native AiHummer agent
Uses Context, Trust, Proof and Flow directly. Boundaries are set by the organization's policy and the operation type.
A third-party agent or model
Works via the AI Gateway and API. Access to context and actions is limited by a separate policy set and takes extra setup.
The customer's own connector
Built on the Connector SDK by the customer's team or a partner. Passes contract tests before joining the production perimeter.
An external portal party
Sees a permitted slice of the organization's data and gets no access to internal systems. Access is limited to the contract's term.
Compliance
Target profiles, not claimed certificates
Below are the reference points the ecosystem is designed against. No obtained certificates or confirmed compliance are claimed.
152-FZ
Designed with the requirements in mind. Confirming compliance is a separate procedure.
ISO 27001
Designed with the requirements in mind. Confirming compliance is a separate procedure.
OWASP ASVS and SAMM
Designed with the requirements in mind. Confirming compliance is a separate procedure.
SOC 2-ready
Designed with the requirements in mind. Confirming compliance is a separate procedure.
FSTEC and CII
Designed with the requirements in mind. Confirming compliance is a separate procedure.
No certificate has been obtained or is claimed. The wording 'target profile' and 'designed with in mind' is deliberate.
Review
Let's walk the security model on your perimeter
The customer's security team gets a description of data flows, permissions, logs and deployment before the pilot starts.