Pluto7

The vendor's own pages document both a named catalog and write-back. The named systems are SAP ECC, S/4HANA and IBP, Salesforce, Oracle EBS, Oracle NetSuite, Informatica, Google AdTech and Excel, each with its own integration page in the site footer, ingested through SAP connectors and Cortex-enabled ingestion into the Master Ledger, with structured and unstructured sources including PDFs and emails. On the action side, the platform deploys strategies automatically across ERP, TMS and CRM and moves from planning to execution in the connected systems rather than stopping at recommendation.

SourcePluto7, pluto7.com SAP platform post 2025-06-16, CPG post 2025-06-04 and the integrations indexread 2026-09-08

Pi Agent is a central orchestrator under which specialized agents work in harmony on distinct planning domains, fragmenting a problem and delegating to the agent that owns it, then automating workflows end to end and moving from planning to execution across enterprise systems.

The agents are built on Google's Agent Development Kit and communicate over A2A, and the vendor describes the result as a network of specialized agents forming an orchestrated decision layer rather than a chatbot or a single model. That is multi-step, multi-agent execution under a named runtime. The sixty-second planning-to-execution figure is a marketing claim, not a documented mechanism.

SourcePluto7, pluto7.com scenario planning post 2025-06-03, enterprise planning post 2025-05-28 and business value framework 2026-01-27read 2026-09-08

The Master Ledger is a maintained single-table view built on Google BigQuery that unifies structured ERP data with unstructured sources such as PDFs and emails into one governed, real-time dataset spanning inventory, production, planning, fulfillment, finance and external signals, and every agent reads from it, with Pi.Semantic named as the semantic layer over it. That is a persistent, maintained, queryable structure over the customer's own operations that outlives any single run. No retrieval or index mechanism is described beyond the semantic layer's name.

SourcePluto7, pluto7.com ride-share post 2025-08-11, SAP platform post 2025-06-16 and business value framework 2026-01-27read 2026-09-08

The Glassbox line is a posture, not a mechanism. The vendor states that AI augments planners rather than replacing them, preserving accountability, and that planners become curators of intelligent decisions, which is oversight asserted.

No approval gate, review-and-approve surface, autonomy setting or escalation step between an agent recommendation and its execution is documented, and the same site says the platform moves from planning to execution across enterprise systems in under sixty seconds and deploys strategies automatically into ERP, TMS and CRM, which is the opposite direction from a human gate.

SourcePluto7, pluto7.com business value framework post 2026-01-27 and pi-agent pageread 2026-09-08

Pi Shield, on the vendor's Security and Governance page, is a managed security practice built on Google's tooling (Cloud DLP, KMS, Confidential Computing, Secret Manager, Cloud VPN, IAM, VPC Service Controls, Cloud Identity, Identity-Aware Proxy and Cloud Armor), sold alongside SOC services, managed detection and response and DevSecOps engagements, and the page says plainly that this is the intelligence layer sitting on top of the cloud rather than a replacement for it. Google Cloud's certifications are the host's, not Pluto7's, and the delivery services are engagements rather than platform controls.

The access side is real: the product runs inside the customer's own Google Cloud tenant, so the buyer operates real IAM and Cloud Identity over it, and the page documents agent identities defined with the same rigor as human identities, an inherited but operative access surface on a named host platform. No SOC 2, ISO 27001 or other attestation held by Pluto7 itself is named anywhere on the site, and the audit-ready and uptime figures on the page render as empty counters.

SourcePluto7, pluto7.com/security-and-governanceread 2026-09-08

Explainability is documented; an audit record is not. Under the Glassbox methodology planners can see why a recommendation was made rather than just the outcome, alongside ROI metrics tied to the business value framework. That is a reason shown at the point of decision.

No run trace, decision log, retention period or reconstruction surface is documented for what an agent did after the fact, the "continuous evaluation of decisions" phrase is an architectural property with no mechanism attached, and the auditing named on the Security and Governance page is Google Cloud compliance auditing of the tenant, not a record of agent activity.

SourcePluto7, pluto7.com business value framework post 2026-01-27 and /security-and-governanceread 2026-09-08

No agent-level state with a stated scope and lifetime is documented, and no distinct per-agent memory store is described. The shared Master Ledger and the persistent digital twin are a unified real-time view of enterprise data on BigQuery, an application data layer that all agents read from, and a customer data store is not agent memory.

SourcePluto7, pluto7.com business value framework post 2026-01-27read 2026-09-08

Under the Glassbox methodology the vendor commits that customers own their data and models and that all intelligence runs inside the customer's own Google Cloud environment, and the platform is delivered into that tenant through a Google Cloud Marketplace private offer. Because the platform runs in the customer's own cloud tenant, the buyer chooses the project, region and controls rather than selecting from a vendor's list. No region list is published, and deployment is Google Cloud only, with no AWS, Azure or on-premises option documented.

SourcePluto7, pluto7.com business value framework post 2026-01-27 and the Cloud Marketplace listingread 2026-09-08

The vendor names discrete units on its own pages: a Demand Agent for forecast accuracy, an Inventory Agent for positioning and safety stock and a Finance Agent for margin and cost-to-serve tradeoffs, referred to elsewhere as Ron, Kassy and Alex, plus Operations in a Box for finance, marketing, HR, IT and sales. Each of the three agents is a unit a buyer could adopt on its own. No catalog, gallery or template library page exists where a buyer browses and selects among agents, and a count of over one hundred specialized prebuilt agents is not supported on any first-party page.

SourcePluto7, pluto7.com business value framework post 2026-01-27 and CPG post 2025-06-04read 2026-09-08

Agents fire on real-time signals rather than on user request. The vendor documents agents sensing real-time external signals (promotions, weather, market trends, demand shifts and surges) and acting on them, real-time demand sensing as a named capability, and a shift from periodic manual planning cycles to always-on adaptive intelligence in which decisions are elevated before the planner asks the question. Delivery is into the platform and the Agentspace surface, with no webhook, schedule or external channel documented.

SourcePluto7, pluto7.com business value framework post 2026-01-27 and enterprise planning post 2025-05-28read 2026-09-08

The vendor names its model stack plainly and repeatedly: Gemini 2.0, Vertex AI and the Cortex framework on Google Cloud, with agents built on Google's Agent Development Kit. That is a single disclosed provider, with no customer or admin selection surface, no routing control and no bring your own model option documented anywhere on the site. The customer-owned-models line in the Glassbox methodology refers to ownership of the trained artifacts inside the customer's tenant, not to choosing which foundation model runs.

SourcePluto7, pluto7.com scenario planning post 2025-06-03 and business value framework 2026-01-27read 2026-09-08

Pluto7 states that its multi-agents are built using Google's Agent Development Kit and follow the A2A and MCP protocols, and Pi Agent is published on Google Agentspace and Gemini Enterprise and listed on Google Cloud Marketplace, so outside callers can in principle reach the agents through Google's agent surfaces. No A2A agent card naming an endpoint and an auth scheme is published, the MCP claim is a protocol assertion with no endpoint, scope or reference behind it, and no API, SDK or developer portal of the vendor's own appears anywhere on the site, which has no docs or developer subdomain, only a Zoho-hosted help center behind sign-in.

SourcePluto7, pluto7.com scenario planning post 2025-06-03 and Gemini Enterprise page, probe recordedread 2026-09-08

No scored result, comparison, holdout or post-deployment tuning loop measuring agent decisions is documented anywhere on the site, and no configuration or readiness gate either.

The thousands of digital twin simulations run before execution to find the optimal path test the customer's supply chain plan (alternates, lead times, tariff shifts, demand scenarios), which is the product's own function; the artifact under test is the plan, not the agents.

"Continuous evaluation of decisions" appears in the vendor's framework post as a property of the Master Ledger architecture with no mechanism attached.

SourcePluto7, pluto7.com business value framework post 2026-01-27 and pi-agent pageread 2026-09-08

No browser, desktop or remote control of an interface the vendor does not own is documented anywhere on the site. The agents reach the customer's systems through SAP connectors, Cortex ingestion and write-back into ERP, TMS and CRM, and act inside the platform and the Agentspace surface.

SourcePluto7, pluto7.com SAP platform post 2025-06-16 and pi-agent pagesread 2026-09-08