A complete platform for building, integrating, and exposing digital services as managed APIs in cloud, on-premise, and hybrid architectures.
WSO2 API Manager is a complete API management platform that enables organizations to build, integrate, and expose digital services as managed APIs. It provides tools for designing, publishing, and managing APIs throughout their lifecycle, supporting cloud, on-premise, and hybrid deployment architectures. The platform helps drive digital transformation by allowing API product managers to create API products from multiple APIs.
Enterprise developers, API product managers, and organizations undergoing digital transformation who need comprehensive API lifecycle management. It serves businesses ranging from startups to established enterprises with decades of history.
Developers choose WSO2 API Manager for its interoperability through open standards, extensibility to customize every aspect of the platform, and ability to handle everything from simple scenarios to comprehensive protocol support without vendor lock-in.
Welcome to the WSO2 API Manager source code! For info on working with the WSO2 API Manager repository and contributing code, click the link below.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports REST, GraphQL, and AsyncAPIs using industry standards, ensuring seamless integration without vendor lock-in, as emphasized in the interoperability section.
Enables creation of composite microservices, message routing, transformation, and service orchestration, making it suitable for complex enterprise scenarios highlighted in the integration support.
Offers customizable authenticators, policies, mediations, and workflows through user-friendly extension points, catering to diverse needs as described in the extensibility platform.
Can be deployed in cloud, on-premise, or hybrid architectures without vendor lock-in, providing deployment versatility as stated in the hybrid deployment feature.
Requires JDK installation, environment variable configuration, and manual extraction steps, which can be cumbersome compared to containerized or cloud-native alternatives, as seen in the installation prerequisites.
Relies on Java (JDK v21 or similar), which may not align with teams using other stacks or preferring lighter, language-agnostic tools, as indicated in the system requirements.
As a comprehensive platform, it introduces significant operational complexity and resource demands, potentially excessive for simpler use cases, hinted at by the focus on enterprise customization.