myMeta Orchestra
myMeta S.r.l. · Software Development
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 9 captures on record
What the publisher says
As described on Microsoft Marketplace.
Deploy the Orchestra Player runtime in your Azure tenant
Enterprise teams running AI and automation workflows often must send sensitive data outside their environment for processing. The Orchestra Player removes that constraint by executing workflows inside the customer's own Azure tenant. myMeta Orchestra is a workflow and AI orchestration platform composed of a control-plane Console and a customer-side runtime called the Orchestra Player. This offer deploys the Player as an Azure Managed Application in the customer's Azure tenant. The Player executes authorized workflows configured through the separate myMeta Orchestra Console.
Show the rest of the publisher’s description (16 more lines)
Security by design
The Player runs inside the customer's Azure tenant, so workflow execution happens close to customer data and uses customer-controlled Azure resources. This is especially relevant when workflows process business data, personal data or sensitive operational information.
What this offer deploys
- Azure Functions on Linux for the Node.js/Express Player runtime.
- Azure Cosmos DB for NoSQL for runtime metadata.
- Azure Blob Storage for media assets and workflow-related data.
- Optional AI-ready and vector-enabled components.
Workflow and AI orchestration
The Player can execute backend workflows that connect APIs, databases, storage services, enterprise systems, AI services and knowledge sources from within the customer's Azure environment. Supported scenarios may include workflow automation, API-driven processes, scheduled jobs, LLM-assisted workflows, RAG, semantic search, vector-enabled knowledge flows and LLM agent scenarios.
Part of the myMeta suite
myMeta Orchestra is part of the broader myMeta suite, which can include a browser extension and frontend modules such as Build and Draw. Through these modules, data and results from Orchestra workflows can be surfaced directly inside business web applications as widgets, actions, dashboards, assisted interfaces or AI-enabled experiences. Frontend context, user actions and page events can also trigger Orchestra workflows, turning existing applications into entry points for backend automation and AI orchestration.
Plans and scope
- Orchestra Player Starter: for customers who want a Marketplace-based commercial subscription.
- Orchestra Player (Existing Agreement): for organizations with an active myMeta agreement instructed to deploy the Player.
The Player is the runtime component only. Complete scenarios also require access to the Console and properly configured projects, connectors, workflows, permissions and security settings. This offer does not deploy the Console and does not automatically grant production usage rights, Console access, implementation services, premium support SLAs or additional myMeta modules unless covered by the selected paid plan or by a separate agreement with myMeta. Azure infrastructure, Azure OpenAI, model usage, storage and database costs are charged directly to the customer's Azure subscription. Azure OpenAI availability and quota depend on Microsoft Azure service availability.
For questions, contact support@mymetasoftware.com.
Preview
1 image
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
3 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.