Security & data
Understand the boundaries.
Security depends on what is deployed, how it is configured, and what has been verified. Start with those details.
Preview scope
Kalamos is in preview. This website does not represent a security certification, an independent audit, or a guarantee of production suitability. Enterprise identity, authorization, and operational requirements must be assessed for the specific deployment.
Tool policies and approvals
Kalamos includes configurable tool policies and approval requests. Whether an action requires approval depends on the active policy and execution path. Do not assume that every action is reviewed by a person.
Models and data destinations
Prompts and task material may be sent to the configured model provider. External tools may also transmit data to their destinations. Hosting a workspace privately does not prevent external data transfer when external connections are enabled.
Sessions and execution records
Kalamos retains sessions and execution history. Retention, access, export, deletion, and backup arrangements should be confirmed for the deployment before sensitive information is introduced.
Before a deployment
Discuss identity and access, model and tool destinations, secrets handling, retention, operational recovery, and support responsibilities with Aliion. Preview access does not include an implied service-level agreement.
Report a concern
Email [email protected] with a brief description. Please request a suitable exchange method before sending sensitive evidence or credentials.
For information about this marketing website, see our privacy notice.