Updated 22 minutes ago

Share this article

Related News

SAP phases in Joule tools with Enterprise AI Gateway planned for 2027

Oct 27, 2026

SAP phases in Joule tools with Enterprise AI Gateway planned for 2027

SAP’s TechEd guide separates phased Joule rollouts from planned Enterprise AI Gateway, offline-evaluation and n8n releases, with different access and timing limits for each.

SAPJoule WorkJoule Studio

IBM ties agent identities to short-lived credentials, with discovery still in preview

Oct 27, 2026

IBM ties agent identities to short-lived credentials, with discovery still in preview

IBM’s TechXchange announcement separates generally available Agent Identity, Vault 2.2 and Orchestrate evaluation from preview discovery and containment. The identity product’s earlier availability notice is dated October 26.

IBMHashiCorp VaultAgent Identity

Cato AI Endpoint brings AI traffic and local-agent controls alongside existing security tools

Oct 27, 2026

Cato AI Endpoint brings AI traffic and local-agent controls alongside existing security tools

Cato says its new endpoint client discovers AI use and applies policy across browsers, desktop apps and supported local agents, while routing only AI application traffic to its platform.

Cato NetworksAI securityEnterprise AI

IDZ Enterprise separates desktop-local, managed-cloud and customer-endpoint AI routes — Source: OpenTools Team · AI-generated conceptual illustrationSource image

IDZ Enterprise separates desktop-local, managed-cloud and customer-endpoint AI routes

By OpenTools Team

IDZ Enterprise is available by agreement, with organization‑managed files, chats and AI policies. Private mode needs a supported desktop and active local model; external processing has separate routes.

Files, conversations and AI share an organization‑managed workspace

IDZ has launched IDZ Enterprise, bringing its MetaCortex AI features, ZCloud file storage and ZChat messaging into an organization‑managed workspace. The October 27 announcement says the service is available now by agreement, with processing routes and access policies controlled by the organization.

The described workflow begins with information already in files or team conversations. A member can find relevant material, compare or summarize it, prepare an artifact, and save or share the result. IDZ says MetaCortex cites the underlying file, page or message so a professional can check its sources. Those are the company’s descriptions of the product, rather than an independent evaluation of its outputs or encryption.

The distinctive choice for a team is how that work is processed. IDZ Enterprise separates a desktop‑local route, IDZ‑managed cloud processing and an organization‑approved customer‑hosted endpoint. Their prerequisites and approval steps differ, even when the member starts from the same files and chats.

Private, Boost and Company AI have different processing boundaries

Private processes a request locally on a supported desktop device with an active local model, according to IDZ’s release. Member access through iOS, Android or the web does not establish that this local processing mode runs on those clients. The announcement specifically keeps Private mode tied to supported desktops.

Boost uses IDZ‑managed cloud AI. The company says users can preview the proposed sanitized context, remove sources or passages and approve what is sent for processing. The description establishes a review‑and‑consent step; it does not independently demonstrate that every sensitive detail will be removed from every input.

Company AI routes requests through a customer‑hosted endpoint approved by the organization, subject to Enterprise policy and technical safeguards. That is a separate route from IDZ’s managed cloud. The announcement does not provide a complete endpoint‑provider or model‑compatibility matrix.

IDZ says a Private request is not silently moved to external processing: if a different route is needed, the user is asked before data is sent. That is a reported product behavior, not the result of an OpenTools test of routing or approval controls.

Administrators set policy; receipts describe the reported processing path

The new Enterprise Admin Console is described as managing members, roles, organizational file access, AI and sharing policies, approved processing routes, usage and seats. IDZ says members can see the policies governing their workspace but cannot override organization‑managed settings. That makes the administrator’s permitted routes and file‑access choices part of the workflow a member encounters.

The company also describes a signed receipt for each result, recording the processing mode, sources accessed, actions performed, whether web search was used and what material was approved for external processing. Those fields are intended to document the path behind an output. Their presence does not establish a security certification, complete audit coverage or compliance with a particular organization’s obligations.

IDZ says AI outputs remain subject to professional judgment and human review. Enterprise agreements may specify usage allowances, service levels and approved infrastructure configurations; the announcement does not establish one public price or an identical configuration for every customer. For a team evaluating the service, the concrete scope is therefore the agreed configuration, the member’s access and the processing route selected for the task.

AI‑generated conceptual illustration by OpenTools Team: files and chat cards, a desktop‑local processing unit and a passage‑selection step beside separate external endpoints. This is illustrative artwork, not IDZ’s interface, a tested implementation or evidence of encryption, security or successful sanitization.

Sources

1.IDZ’s release (prnewswire.com)
2.imagedelivery.net (imagedelivery.net)

Tags

IDZMetaCortexPrivate AIEnterprise AIAI workspaces