What teams use
Teams use the workspace to manage users, agents, projects, chat, apps, flows, API keys, Brain, models, services, billing, requests, and profile settings without bouncing between disconnected tools.
// open.private_workspace
OpenOrange private AI workspace
OpenOrange gives each team a private workspace for agents, collaborative coding, chat, models, services, requests, usage, and access.
An OpenOrange instance is a private team workspace for AI work: users, agents, apps, chat, OpenOrange Code, models, services, requests, usage, billing, and access in one product surface.
01
Each team gets a dedicated instance and data boundary.
02
Agent chat keeps runtime identity, queue state, approvals, context, and cost together.
03
OpenOrange Code adds shared projects and isolated coding sessions.
04
The product stays focused on the private instance people actually use.
What stays local
Runtime databases, sessions, memories, media, local caches, overlays, raw logs, and secret values stay on the runtime host or in the chosen secret backend. The workspace keeps only the product data and redacted operational context it needs.
Why it matters
Agents become much easier to adopt when chat, coding, access, usage, requests, and everyday controls feel like one coherent product rather than a collection of scripts.
// questions
Is OpenOrange tied to one runtime?
No. OpenClaw is integrated today, while Hermes and IronClaw integrations are on the way. Each runtime keeps its execution model while joining the same workspace.
Does the control plane need raw payloads?
No. Request traces can preserve actor, route, model, token, cost, cache, redaction state, and audit context without exposing raw payloads by default.