WSO2 API Manager is an open-source, Apache-2.0 licensed Java platform for designing, publishing, and managing the full lifecycle of APIs, aimed at API developers and API product managers who need to expose digital services as managed APIs across cloud, on-premise, or hybrid architectures.

What it is

WSO2 API Manager is a complete platform for building, integrating, and exposing digital services as managed APIs. The repository, product-apim, is the Java source code for that product, and the project lives in the Java ecosystem, with the topics api-gateway, api-management, gateway, microservices, rest, and synapse describing its shape. Two web applications carry the day-to-day work: the API Publisher, where API developers design, publish, and manage the lifecycle of APIs, and the Developer Portal, where those APIs are discovered and consumed. It is distributed as a self-hosted product rather than as a library, and it targets cloud, on-premise, and hybrid deployment architectures.

The concrete problem it solves is the fragmentation that appears when an organization exposes services one at a time without a shared control plane. Instead of stitching together a gateway, a separate catalog, and bespoke lifecycle tooling, WSO2 API Manager provides a single platform that covers design, publication, mediation, security extension, and consumption. It also addresses the modernization gap directly: organizations can adopt REST, GraphQL, and AsyncAPIs without abandoning the legacy systems already in production. API product managers get a further capability that a plain gateway does not offer, which is the ability to compose API products out of one or more existing APIs.

Key capabilities

• API lifecycle management through the API Publisher web application at https://localhost:9443/publisher and the Developer Portal at https://localhost:9443/devportal.
• API product creation, letting API product managers build a product from one or more existing APIs.
• Protocol support for REST, GraphQL, and AsyncAPIs, framed as interoperability with open standards and freedom from vendor lock-in.
• Integration runtime built on the Synapse mediation engine, covering composite microservices, message routing, transformation, message mediation, service orchestration, and consumption and processing of streaming data.
• Extension points for authenticators, policies, mediations, API lifecycles, workflows, portals, and login pages.
• Distribution as wso2am-4.7.0-SNAPSHOT.zip, started with api-manager.sh on Unix-like systems or api-manager.bat on Windows.
• A separate companion offering, WSO2 API Platform for Kubernetes, recommended when workloads run on Kubernetes.

Who uses it and how

• API developers design, publish, and manage API lifecycles in the API Publisher, then expose and iterate on those APIs for consuming applications.
• API product managers compose API products from one or more APIs, treating a bundle of services as a single sellable or governable unit.
• Enterprises of any size, from startups to organizations with decades of history, adopt modern service delivery paradigms while keeping legacy systems running.
• Teams running workloads on Kubernetes are directed to the dedicated WSO2 API Platform for Kubernetes rather than this distribution.
• Operators self-host the product, extracting the zip and launching it with the platform script, and get support through the wso2-am tag on Stack Overflow, the project Discord, and the WSO2 documentation site.

Getting started

Install by extracting wso2am-4.7.0-SNAPSHOT.zip, setting JAVA_HOME to point at a supported JDK (JDK 21 is supported), and running api-manager.sh or api-manager.bat from the bin directory. The Product and Developer Portal interfaces then come up on port 9443, with default administrator credentials of admin / admin and a Quick Start guide covering the first API.

How it compares

The facts provided name no paid products that this project replaces, and no directly comparable open-source alternatives either, so it stands alone in this registry. The nearest named relationship is internal to WSO2: when workloads run on Kubernetes, the documentation recommends the separate WSO2 API Platform for Kubernetes instead of this distribution. Those making a choice should therefore evaluate it on its own terms rather than against a listed competitor set.

When to use it — and when not to

A self-hoster takes on a Java runtime, a supported JDK with JAVA_HOME configured correctly, and the operational care of a zip-based product distribution, since the facts name no Docker image or compose file. Anyone who wants a lightweight single binary, or who cannot operate a JVM-based product, should look elsewhere. Two facts should also shape expectations: the documentation excerpt is thin and defers to external docs for prerequisites and the quick start, and the build referenced is 4.7.0-SNAPSHOT, a development snapshot, alongside a substantial backlog of 651 open issues. The default admin / admin credentials must be changed before any interface is exposed beyond localhost.