KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Our clients
Clients and partners
Qwen enterprise overview
2 news
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Qwen enterprise overview. Odoo →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Qwen enterprise overview. Bitrix: implementation and integrationQwen enterprise overview. Odoo →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
The RC removes the initialize handshake and sessions: state is passed via explicit handles, follow-ups go through InputRequiredResult without SSE. Load balancing over plain HTTP without sticky sessions.
Loose coupling and stateless scaling have long been the norm for brokers; MCP is only arriving at this now. Apache Kafka →Load balancing of stateless calls over HTTP is handled by the ESB/API gateway; MCP moves it into the protocol. MuleSoft →
The RC introduces Extensions (reverse-DNS IDs, capabilities, versioning): MCP Apps serves HTML in a sandbox iframe, Tasks offloads long-running operations. A narrow core, growth through modules.
Long-running jobs, queues and versioned node plugins are the n8n model; MCP cements this in the spec. n8n →
The RC carries W3C Trace Context in _meta for end-to-end trace correlation and introduces a lifecycle policy: at least 12 months between deprecation and removal.
Collecting distributed traces via OTel/APM is a built-in Elastic feature; MCP merely passes the context through. Elasticsearch →
2.4.9 added Symfony 7.4 LTS and PHP 8.5, extended CAPTCHA to REST/GraphQL (closing the API bypass). 581 core improvements; the clearCart mutation is now open to Open Source.
An MCP server was announced at Adobe Summit 2026: AI agents gain access to the catalog, cart, prices, stock and checkout. It depends on the Integration Starter Kit and AppBuilder.
The AI suite analyzes the implementation, builds a migration path to ACCS, and rewrites legacy code into event-driven components. Status is coming soon; it is not publicly available yet.
Studio (React/TypeScript) becomes the only interface, all ExtJS is removed, bundle versions are unified. The 2026.x branch requires Symfony 7.4.
AI agents read and propose changes to objects and assets through MCP under the same permissions and workflows as people. All actions go through the Data Spine layer.
deliveryOptionsCalculate replaces implicit shipping webhooks. Search has been redesigned (prefixes, operators, ranking); gift cards are paid via the Transaction API.
Prefixes, operators and ranking have long been basics in Elasticsearch; Saleor 3.23 does it in PostgreSQL. Elasticsearch →Magento Commerce has had gift cards as native payment for years; Saleor only added it in 3.23. Magento →
The roadmap sets 4 priorities (transport, agents, governance, enterprise) and a shift from a release-centric plan to Working Groups. Enterprise via extensions, not the core.
The enterprise bus was built for audit trails and manageability from the start; MCP is only now building governance through modules. Datareon →
Saleor released Paper — a production-ready storefront with a mobile multi-step checkout. It includes an AGENTS.md with rules for AI tools (Cursor, Claude, Copilot).
Adobe announced support for the open UCP (Google) and ACP (OpenAI/Stripe) protocols, in addition to Agent Payments Protocol, so products can be purchased through ChatGPT and Gemini.
Share groups declared production-ready: consumers read the same partitions with per-record acknowledgment — a classic queue on top of Kafka.
Point-to-point with guaranteed delivery and confirmation is Datareon's standard bus model. Datareon →Queues and point-to-point messaging (JMS/Anypoint MQ) are a long-standing core MuleSoft pattern. MuleSoft →Queues with per-message acknowledgment and dead-letter handling were an ESB standard in Talend ESB long before KIP-932. Talend ESB →
Kafka Streams group management has been moved to the broker side: task assignment, topology storage, and observability are now generally available.
Kafka Streams exception handlers gained built-in routing of failed records to a dedicated queue (DLQ) instead of manual wiring.
Error handling via a separate error workflow is an n8n mechanism; DLQs have long existed in brokers and iPaaS. n8n →Dead-letter routing for failed messages was a standard ESB pattern long before Kafka Streams. Talend ESB →
Akeneo released a native MCP server: the catalog as resources, agent edits as tool calls, and server-side quality rules. The release also includes Digital Showroom and Custom Components
Akeneo is not inventing MCP, but implementing an existing standard on top of PIM; the protocol itself is described separately. MCP →MCP serves the catalog via synchronous tool calls; for event-driven integration an event bus delivers the same effect. Apache Kafka →
In its Winter Release, Akeneo announced a partnership with the Stripe Agentic Commerce Suite: product discovery by AI agents and acceptance of agent payments. The release's MCP server is covered separately
Stripe and the MCP server are separate release components; the value lies in the connector to the payment provider. MCP →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Qwen enterprise overview. Magento →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Qwen enterprise overview. Odoo →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Qwen enterprise overview. Magento →
The last release with Admin UI Classic alongside Studio. An experimental MCP server reads data over Elasticsearch/OpenSearch. Symfony 7 alongside 6.4, with 3-year LTS.
MCP endpoint in Datahub Simple REST — the same LLM access protocol as in the catalog (/instruments/mcp). MCP →MCP access relies on the Elasticsearch/OpenSearch index (/instruments/elasticsearch). Elasticsearch →Reading an LLM catalog on top of an index follows the same grounding pattern as RAG (/instruments/rag). RAG →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Instead of the problematic DCR (SEP-991) — Client ID Metadata Documents (client_id as a URL pointing to JSON). Cross App Access (SEP-990) shifts authorization to the organization's IdP.
Authorization and SSO are the reason teams deploy an LLM/Security Gateway; MCP covers part of it, while policies stay in the gateway. LLM & Security Gateway →
Saleor shipped an official Adyen integration for international payment acceptance and refunds. It is implemented through the App model rather than a built-in core plugin.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
An MCP server launched, giving LLMs access to store data (channels, orders, products, stock) over Streamable HTTP. Read-only, no mutations; Saleor 3.21+ and Saleor Cloud.
MCP as an LLM-to-data access protocol is a separate catalog tool; Saleor MCP is its implementation. MCP →
The app connects a Saleor store to ChatGPT via OpenAI ACP, exporting the catalog to an ACP feed. For now the feed is exported manually; payment and checkout in ChatGPT are the next stage.
GenAI in Akeneo fills numeric and Yes/No attributes, extracts specifications from PDFs with unit conversion, and pulls values from reference entities. AI Configuration has been added
GenAI attribute enrichment is a broader PIM trend; Pimcore's similar features launched at the same time, so this is parity. Pimcore →
The rules engine gained triggered rules — real-time execution on product updates, tied to workflows. Akeneo DAM was re-released with AI asset tagging
The record change-to-action trigger in PIM is convenient, but tied to Akeneo; cross-system, n8n has it. n8n →
Copilot generates text through Chat Completions, so it connects to different LLM providers (OpenAI, Hugging Face, RunPod). Documents appears in Studio for the first time (preview).
Chat Completions uses the same interface that the LLM gateway intercepts (/instruments/llm-gateway). LLM & Security Gateway →LLM-based product content generation overlaps with Akeneo GenAI (/instruments/akeneo). Akeneo →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Qwen enterprise overview. Saleor →
A public catalog and API of MCP servers opened at registry.modelcontextprotocol.io (Anthropic, GitHub, PulseMCP, Microsoft). Preview, with no data guarantees and breaking changes until GA.
Release 4.1.0 brought share groups to preview (not for production) and added early access to the Kafka Streams rebalancing protocol (KIP-1071).
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Akeneo introduced its first AI agent, Data Architect Agent: based on sample product files and context, it drafts a data model. GA for Product Cloud is July 12, 2025
GenAI assistants in PIM are not unique: Pimcore's GenAI/Copilot arrived earlier, and the data model is already there. Pimcore →
PX Insights shows how AI assistants like ChatGPT interpret and recommend products. In Spring 2026 — a closed loop that suggests missing words and attributes
In essence, it simulates how an LLM/search engine retrieves and ranks products — close to a RAG pipeline. RAG →
Over 30 Symfony components now run in version 7 alongside 6, paving the way for migration. Asset metadata select fields pull values from external sources; the Datahub File Exporter writes to the directory tree.
The multi-tenant SaaS edition of Adobe Commerce became generally available (Americas from June 25, 2025, then EMEA and JPAC). Versionless with automatic Adobe updates instead of self-hosted/PaaS.
Cloud-native SaaS and versionless are built into Saleor from the start; for Magento, this means moving away from self-hosted Saleor →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
3.21 added the first OpenTelemetry stream (traces and metrics) for APM tools (Datadog, Grafana, Uptrace). It covers Saleor Core, apps and services.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
2.4.8 fixed ~497 core bugs, added PHP 8.4, MySQL 8.4 and MariaDB 11.4 LTS, extended GraphQL for headless and B2B (negotiable quotes), and strengthened 2FA with Duo Security.
Headless/GraphQL is Saleor's core architecture, while Magento extends GraphQL on top of a monolith Saleor →
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
The first major release entirely without ZooKeeper: metadata is managed by default by the built-in Raft (KRaft), reducing operational complexity.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
KT.Team helps enterprise teams with qwen through discovery, architecture, implementation, integration and support.
Nothing found for this filter.
Overview
Related Cases
AI ingredient recognition by barcode
- Processing sped up from 30 minutes to 2 per batch of 10 images
- Composition recognition accuracy is 80–95%
OSNO-VA: AI accountant
- Built an AI platform
AI analytics of the real estate market
- Designed an assistant
Business value
Articles on the topic
Construction automation for developers: digital construction tech, project management, BIM, IoT and data analytics
Learn more
How to calculate TCO in IT projects: total cost of ownership for CRM, ERP, infrastructure and AI services
Learn more
System integrator: how to choose a reliable IT partner for import substitution, automation, and digital transformation
Learn more
