> ## Documentation Index > Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt > Use this file to discover all available pages before exploring further. # Cloud Security Architecture > xpander cloud, the fully hosted deployment: control plane and data plane operated by xpander, with the same controls enforced in the runtime In the **Cloud** edition, xpander operates both planes: the control plane (Xpander Chat, identity, agent registry, skills catalog, deployment manager) and the data plane where agents execute. There is no customer cluster, no PrivateLink endpoint to configure, and no installer - you sign in and your agents run. The controls enforced in the runtime are identical across deployments and are described on the [Security Architecture](/resources/security-compliance/security-architecture) page: agents are bounded by their operation surface, credentials never reach the model, and safety controls sit at the skill-call boundary. ## Architecture Cloud architecture. Users and AI Engineers reach xpander Cloud over TLS. Inside, a control plane holds Xpander Chat, identity with SSO, the agent registry, and the skills catalog; a data plane holds the execution tier, the agent-controller's skill relay (drawn as AI Gateway), PostgreSQL, and Redis with vectors, hosting threads, memory, and knowledge bases. Model calls go out to LLM providers and skill calls go out to the systems your skills reach. Captions state TLS at xpander's ingress, encryption at rest with cloud-provider managed keys, and that skill credentials are injected by the skill relay and never visible to the model. How to read the diagram: * **Users and AI Engineers** reach xpander at `chat.xpander.ai` over TLS; enterprise plans add [SSO over OIDC](/resources/security-compliance/access-control#single-sign-on). * **Control plane** - Xpander Chat, identity, the agent registry, and the skills catalog. Agents and skills are configured here. * **Data plane** - the execution tier runs agents, the agent-controller's skill relay (`agent-controller`) brokers skill calls, and PostgreSQL / Redis host threads, memory, and knowledge bases. * **Model and skill calls** leave the data plane toward the LLM providers you configure and the systems your skills reach. Skill credentials are injected by the skill relay at invocation - the model never sees them. * There is no customer VPC, no PrivateLink endpoint, and no separate control-plane sync - this *is* xpander Cloud. ## What runs where | Plane | Components | Operated by | | - | - | - | | Control plane | Xpander Chat, identity, agent registry, skills catalog, deployment manager | xpander | | Data plane | Agent execution (serverless), threads, memory, knowledge bases | xpander | | Your systems | LLM provider accounts you configure, the APIs your skills reach | You | Agents you create in Xpander Chat run on Claude Code, Codex or OpenCode on xpander's executor fleet in xpander Cloud (the `deployment_type` field in the [List Agents](/api-reference/v1/agents/list-agents) API still reads `serverless`). Skill calls go from xpander to the systems you connected, using credentials scoped per skill and injected at the moment of use. ## Identity and access * Sign-in at `chat.xpander.ai`, with [SSO over OIDC](/resources/security-compliance/access-control#single-sign-on) on enterprise plans. Xpander Chat is `chat.xpander.ai`; every control on [Govern](/run/govern) lives under its Settings. * [RBAC](/resources/security-compliance/access-control) governs who may assemble, deploy and use agents; API keys are scoped and revocable. * Audit logs record skill calls, data access, and configuration changes. See [Access Control](/resources/security-compliance/access-control#the-record). ## Encryption and data handling * All xpander traffic is TLS in transit, terminated at xpander's ingress. * Data at rest is encrypted with cloud-provider managed keys. * Under GDPR, xpander is the **data processor** and you are the controller for Managed Runtime (Cloud) workloads; a DPA is available with enterprise contracts. Region-specific deployment for your workspace can be requested. See [Certifications & Compliance](/resources/security-compliance/certifications-compliance#gdpr). * Right to erasure and portability are exposed through the API and Xpander Chat: conversation history, knowledge-base documents, and user memories can be deleted on request; agent configurations and task history can be exported. ## Compliance xpander.ai is **SOC 2 Type II** certified (Security, Availability, Confidentiality); the report is available under NDA. ISO 27001, HIPAA, and FedRAMP are in progress. See [Certifications & Compliance](/resources/security-compliance/certifications-compliance) for the current status and how to request documentation. ## When to choose a different deployment If your requirements include data residency inside your own network, or zero egress to xpander, use a self-hosted deployment: Your VPC runs the data plane; xpander Cloud syncs configuration over PrivateLink Every component in your environment; zero egress to xpander *** ## Related Permission model, credential isolation, encryption, and safety controls SOC 2 Type II, GDPR, and documentation requests This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.