Enterprise buyers ask "where does my data live?" The answer is: exactly where it already lives. Sageion routes requests and returns results. Nothing leaves your system.
We don't save API requests. We don't save API responses. We don't save conversation history. If a tenant doesn't explicitly opt in, there is nothing on our side to leak.
History is a per-API setting, disabled on create.Your users live in your identity server. Tokens are minted by you. We never see a password. We receive an encrypted JWT and never store the plaintext.
RSA-2048 wrapped AES-256-GCM. Plaintext JWTs are rejected.Every tenant's OAuth tokens live in their own Secrets Manager namespace. Rotation is scoped. Revocation is scoped. A compromise in one tenant cannot touch another.
{Prefix}/sageion/oauth-token/{tenant}/{app}/* — isolated per app.The AI agent calls your APIs with your credentials and returns the result to your product. Your customer's data stays in your backend, always.
We are the routing layer, not the data layer.If you stop using Sageion tomorrow, your users still exist. Your data still exists. There is no migration because there was nothing to move.
The product returns to your APIs. Not to ours.Every tenant has its own secret namespace. Every execution carries app_name and user_id. A compliance auditor sees the separation without reading code.
Two isolated stacks: AutoBot and Connector. Separate IAM.AutoBot (control plane) and Connector (execution plane) deploy independently. No shared Lambda, no shared IAM role.
Secrets Manager paths are {Prefix}/sageion/oauth-token/{tenant}/*. A wildcard scan shows exactly which secrets belong to which tenant.
Tenant resources are invisible to apps until explicitly attached. Fail-hard guards prevent accidental cross-tenant access.
Plaintext JWTs are rejected outright. Only RSA-OAEP + AES-256-GCM ciphertext is ever accepted by the runtime.
Our architecture documentation covers every stack, IAM role, and secret namespace. Book a call and our team will walk your CISO through it.