AQENVOR Studio / Private alpha

Security & isolation

Workspace isolation

Each account runs in a separate container with a dedicated persistent volume. Containers are not given host ports, are attached to an internal Docker network, drop Linux capabilities, disallow privilege escalation, run non-root and have CPU, memory and PID limits.

Authentication

Invite-only accounts, scrypt password hashes, HttpOnly SameSite cookies, CSRF tokens, login rate limiting and server-side sessions. The control plane can revoke every session instantly.

Keys

DeepSeek keys are entered inside the user's Studio and stored in that user's volume. The control database does not hold model keys.

Limits

Per-container CPU, memory and PID limits; per-user project cap; chat rate limiting; account cap for the alpha; a global freeze switch.

Previews

Previews are served on subdomains of the same authenticated app domain so the Studio can show them. Generated code should be treated as untrusted: preview it under the account that owns it, never under the operator account, and do not paste production credentials into a generated app.

What is not claimed

This alpha is not a hardened multi-tenant SaaS. The control plane mounts the Docker socket and the runtime executes arbitrary user code inside its container. Do not treat it as suitable for regulated or hostile multi-tenant workloads without an independent security review.