Skip to main content

Models, credentials and data boundaries

Model choice​

Clawuno can use supported cloud APIs, compatible open-model endpoints and locally hosted models. Evaluate each connection for tool support, context length, image input, reasoning behavior, cost and regional policy.

Use organization-managed credentials for shared deployments. Test a connection before making it the default, and retain at least one administrator path that does not depend on the model being available.

Where data goes​

Clawuno stores its own Workspace metadata, conversations, Agent configuration and credentials in the deployment you control. Data can still leave that boundary when a user or Agent intentionally calls:

  • a cloud model;
  • web search or web fetch;
  • a SaaS/MCP integration;
  • Lark or another external collaboration system;
  • a linked folder hosted by another system.

Review those providers separately. A private Clawuno deployment does not change their data-processing terms.

Minimum controls​

  • expose Clawuno only through HTTPS and approved networks;
  • use distinct user accounts instead of shared administrator credentials;
  • limit linked folders and external integrations to their business need;
  • rotate model and external-service credentials under organization policy;
  • store backups separately and control access to them;
  • do not place release or infrastructure secrets in Workspace files where Agents can read them.

Local-only operation​

A deployment can remain offline when it uses a local model and does not enable web or external-service capabilities. Test the exact workflow offline; do not infer offline behavior from the fact that the Engine itself is locally installed.