Enterprise agent platform packs

Why these packs exist

OSuite should not flatten every enterprise agent platform into the same generic compatibility claim. These packs exist to separate the managed runtime or managed workspace a vendor owns from the approval, replay, evidence, and buyer-facing proof OSuite adds on top.

Microsoft Foundry

Use Microsoft Foundry as the managed runtime boundary and let OSuite stay buyer-visible above it.

• Foundry owns hosted execution and managed agent lifecycle.
• OSuite keeps approvals, replay, proof export, and reviewable posture legible to operators and buyers.
• This is already beyond a placeholder lane because OSuite has a real Foundry bridge and hosted runtime path.

Google Gemini Enterprise Agent Platform

Gemini Enterprise Agent Platform should land in OSuite as an enterprise platform lane, not as a thin model adapter.

• Treat enterprise data access and tool governance as first-class buyer controls.
• Keep OSuite focused on approval routing, replay, and proof instead of rebuilding Google-managed orchestration.
• Position the lane as a governance overlay for enterprise agents, not just a Gemini API checkbox.

Amazon Bedrock AgentCore

Amazon Bedrock AgentCore belongs in the inventory as a managed platform substrate.

• AWS owns runtime plumbing, scale, identity, and observability surfaces.
• OSuite adds governed approvals, replay, and exportable proof around that execution path.
• The value is governance over an enterprise agent substrate, not reimplementation of AWS operations.

OpenAI API and Frontier

OpenAI now spans two different product surfaces that should not be collapsed into one runtime story.

• OpenAI API is the direct agent and tool-calling lane.
• Frontier is the enterprise workspace and deployment posture lane.
• OSuite should govern both, while keeping API compatibility separate from enterprise workspace narrative.

ServiceNow AI Agent Fabric

ServiceNow matters because it connects AI agents to governed enterprise work, not just conversations.

• Treat AI Agent Fabric as a workflow and action surface.
• Govern approvals, replay, and buyer-proof on top of ServiceNow-native execution.
• Keep the runtime story tied to system-of-action workflows instead of generic chat automation.

Salesforce Agentforce

Agentforce should be presented as a business-action platform that needs buyer-legible governance.

• Salesforce owns the metadata, workflow, and business-data substrate.
• OSuite governs the action path through approvals, replay, and proof.
• The runtime inventory should show this as a workspace-suite lane, not a generic model endpoint.

LangGraph Platform

LangGraph Platform is useful because it gives OSuite a serious orchestration substrate.

• Durable execution, stateful agents, and human-in-the-loop flows map naturally to governed replay.
• OSuite should treat LangGraph as a bridgeable orchestration platform.
• The product value is control and evidence over complex agent state transitions.

Use these packs when

• A buyer asks how OSuite governs a specific enterprise agent platform.
• You need to separate runtime ownership from OSuite governance ownership.
• A team wants to compare API, managed platform, and managed workspace lanes without flattening the vendor context.