On November 17, 2026, WSO2 announced that the company is now Choreo Labs. CEO Harry Ault put it simply: "WSO2 was the right name for the company we started in 2005" (the announcement).
If you run WSO2 API Manager, Identity Server or Integrator today, the software in production did not change overnight. What changes is the set of names in your contracts, runbooks, dashboards and vendor records, and later, when the legal entity changes, your payment and tax records. This post covers what the company has said, what it has not said yet, and what to check this quarter.
What WSO2 announced
WSO2 is now Choreo Labs, at choreolabs.com. The company ties the new name to AI agents moving from pilots into production, and to its role in governing them. "Choreo" comes from choreography: coordinating agents, APIs, integrations, identities and services. "Labs" points to its research and engineering culture and its open source and open standards work.
Choreo is also now the name of the company's platform, which brings API management, integration, identity, agent management and the internal developer platform together in one place.
The company's FAQ is clear that this is a name change, not an acquisition or merger. It reports more than 950 customers in more than 90 countries.
The product names, old and new
Three products have new names so far:
| Former name | New name | What the announcement says |
|---|---|---|
| WSO2 Agent Manager | Choreo Agent Manager | Open source under Apache 2.0. Agent identity, built-in guardrails, and the ability to suspend any agent. |
| WSO2 AI Gateway | Choreo AI Gateway | Applies the same controls to model and MCP traffic. |
| WSO2 Agent ID | Choreo Agent ID | Treats each agent as its own identity, with scoped access, instant revocation and an audit trail. |
The company says the other product names move to the Choreo brand with new releases over the coming months, and that it will tell customers before each change. No product is being discontinued. Until a product is renamed in a release, API Manager, Identity Server, Integrator, Bijira, Devant, OpenChoreo and the rest keep their current names.
Some names had already moved before this week. The internal developer platform once called Choreo had been renamed WSO2 Developer Platform, Asgardeo had been renamed WSO2 Identity Platform, and the support matrix lists Micro Integrator as WSO2 Integrator: MI. If your documents still use the older names, update them in the same pass.
What does not change
According to the announcement and the FAQ:
- Products, contracts, pricing, support and open source licenses continue as they are, with the same teams behind them.
- Support channels, service levels and support engineers stay the same. Existing support links redirect to support.choreolabs.com.
- Package names, repositories, container images, documentation links and downloads stay as they are. If a later release changes any of them, the company says it will share guidance in advance.
- No product is discontinued by the name change.
- Customers have nothing to do at launch.
What to check this quarter
- Support end dates for the versions you run. As of November 17, 2026, the support matrix lists support for Identity Server 5.11.0 ending December 3, 2026, Identity Server 6.1.0 on February 1, 2027, and API Manager 4.2.0 and Integrator: MI 4.2.0 on March 22, 2027. The rename does not change your support, so these dates still drive your upgrade plan.
- Your vendor master, when the legal documents arrive. The company says that once its formal legal entity names are updated, it will send customers a certificate of name change, updated tax documentation and an updated bank confirmation letter, and that customers will then need to update their systems. Plan for accounts payable, procurement and vendor management to update records together.
- Bank detail changes, verified by phone. A legitimate bank confirmation letter is coming, which is exactly what payment fraudsters imitate. Before changing payment details for this vendor, confirm the request with your account manager through a contact you already have, not one supplied in the email.
- Product names in renewals and purchase orders. Procurement will see the new name on future invoices. Tell them before they flag it as an unknown vendor.
- Runbooks, dashboards and alert names. Operations teams search runbooks by product name. Add the new name next to the old one rather than replacing it, so both searches work for the next year. Start with Agent Manager, AI Gateway and Agent ID, which are already renamed.
- Email filters and allow lists. The company's website is now choreolabs.com, and staff email addresses end in @choreolabs.com. Links to wso2.com redirect, and mail to wso2.com addresses still arrives. The company asks customers to add choreolabs.com to their email allowlist. Tell staff to expect the new name, and watch for look-alike domains: a rebrand week is a good week for phishing.
- Your vendor risk records. Banks and health systems keep vendor records, security questionnaires and data agreements by vendor name. Your vendor management team will want the new name on file now, and the legal entity details when they arrive. Give them the announcement link early.
- Pipelines, later. Nothing changes in package or image names at launch. When a future release renames them, update build pipelines and security scanners in the same change. A scanner looking only for old package names can stop matching advisories without raising an error.
Choreo Labs, Choreo, and OpenChoreo
The names overlap, so expect confusion for a while. Choreo Labs is the company, written as two words with no hyphen. On its own, "Choreo" now means the company's platform as a whole. OpenChoreo is the open source community version of its internal developer platform, and a CNCF Sandbox project. Before this week, "Choreo" was the name of WSO2's internal developer platform. When someone in your organization says "Choreo" next year, check which one they mean.
What WSO2 hasn't said yet
We'll keep this list current and date each update as Choreo Labs publishes more.
- New names for API Manager, Identity Server, Integrator and the other products, and which release brings each one.
- When the formal legal entity names change, and when customers will receive the name-change documents.
- Whether package, image and repository names change in a future release, and when.
Last updated: November 17, 2026.
Should you pause upgrades?
No. A rename does not change the code you run, and the company says packages, images and downloads stay as they are. Holding back security updates while names settle is the larger risk. Keep patching.
Where Duczer East fits
Duczer East delivers and supports WSO2 for banks, health systems and other regulated firms, and continues under the new name. For day-to-day operations, upgrades and production support, see our Choreo Labs support and managed services.
