--- title: "Apache APISIX Enterprise Support & Commercial Options - API7.ai" description: "Explore commercial support options for Apache APISIX, including deployment planning, migration assistance, architecture review, performance optimization, security fixes, and training." url: "https://api7.ai/apache-apisix-enterprise-support" --- Open source stays open. Commercial help when you need it. # Apache APISIX Enterprise Support and Commercial Options Apache APISIX is a capable, independent open-source gateway. When your organization needs enterprise governance, migration expertise, architecture review, optimization, security fixes, or training, API7 can discuss commercial options built around APISIX expertise. [Discuss Your APISIX Deployment](https://api7.ai/contact)[Compare APISIX and API7 Enterprise](https://api7.ai/api7-enterprise-vs-apisix) Confirm the available services and engagement scope directly with API7. Choose the operating model that fits 01 Apache APISIX Self-operated open source 02 Commercial support Help for existing deployments 03 API7 Enterprise Gateway governance and API publishing ![Zoom](https://static.api7.ai/uploads/2025/04/15/EcbYj8Bn_Zoom.avif) ![VIVO](https://static.api7.ai/uploads/2025/04/15/U8VvkoLp_VIVO.avif) ![Vodacom](https://static.api7.ai/uploads/2025/04/15/wmtZ535D_vodacom.avif) ![Flipkart](https://static.api7.ai/uploads/2025/04/15/qyiDN6xJ_Flipkart.avif) ![SHEIN](https://static.api7.ai/uploads/2025/04/15/C8oPW9yQ_SHEIN.avif) ![EDB](https://static.api7.ai/uploads/2025/04/15/7sn4jzjd_EDB.avif) ![Haier](https://static.api7.ai/uploads/2025/04/15/A4QnF9k0_Haier.avif) ![Cashfree Payments](https://static.api7.ai/uploads/2025/04/15/XOb1pK94_Cashfree%20Payments.avif) ![GEELY](https://static.api7.ai/uploads/2025/04/15/GtWAVU86_GEELY.avif) ![KFC](https://static.api7.ai/uploads/2025/04/15/1CX8jRil_KFC.avif) ![McDonald](https://static.api7.ai/uploads/2025/04/15/2NuiGsds_McDonald.avif) ![NASA](https://static.api7.ai/uploads/2025/04/15/6xiM2LeZ_NASA.avif) ## Apache APISIX remains an independent Apache project Apache APISIX is a top-level project of the Apache Software Foundation under the Apache 2.0 license. API7 does not own or control the Apache project, and using APISIX does not require an API7 product. API7 originally created and donated APISIX and now offers separate commercial products and services for organizations that want them. [Visit the official APISIX site](https://apisix.apache.org/) Choose a path ## One APISIX foundation, three operating paths Keep operating Apache APISIX, discuss help for your existing deployment, or evaluate API7 Enterprise for multi-team gateway management and API publishing. Open source ### Apache APISIX Run the Apache Software Foundation project on your infrastructure with full control over deployment, configuration, upgrades, and operations. Best fit Teams that want an Apache-2.0 gateway and have the platform capacity to operate it. [Visit Apache APISIX](https://apisix.apache.org/) Commercial support ### Support for Existing APISIX Deployments Discuss deployment planning, migration, architecture review, optimization, integration, security fixes, and training with API7. Best fit Teams that want to keep operating APISIX while evaluating professional assistance for production work. [Review Support Areas](#commercial-support) Enterprise platform ### API7 Enterprise Manage gateway groups, operator access, configuration audits, and API publishing around the APISIX runtime, with support under an agreed plan. Best fit Organizations coordinating gateways across teams, environments, or regulated workloads. [Compare Operating Models](https://api7.ai/api7-enterprise-vs-apisix) Commercial support ## Define the help you need before you engage Start with the work you need: a deployment or integration project, support for a covered product, or an enterprise platform evaluation. Confirm availability, scope, and operating responsibility with API7 before engagement. ### Deployment and migration projects Plan deployment, migration, training, or architecture review around your current gateway and production goals. Agree the project deliverables separately from subscription technical support. - Product onboarding and deployment planning - Migration paths from existing gateway platforms - Architecture discussion and review ### Optimization and integration projects Performance tuning, custom plugins, and integrations require a project scope. Confirm the target versions, technical dependencies, deliverables, and responsibilities before work begins. - Performance optimization - Custom plugin development - Protocol, GitOps, and legacy-system integration ### Subscription technical support Get help with product usage and troubleshooting for covered API7 products and versions. The subscription, agreement, and order form define coverage and response targets; support for an existing open-source APISIX deployment needs explicit agreement. - Product usage questions and issue triage - Covered products and versions - Support channels and severity classification - Response targets in the applicable support plan ### Prepare for a support discussion - Your current APISIX version and target upgrade or migration version - Deployment topology, infrastructure, and who operates the gateway - Plugins, custom extensions, identity integrations, and configuration dependencies - The problem to solve, desired outcome, and rollout or rollback constraints The [API7 Technical Support Policy](https://api7.ai/technical-support-policy) defines subscription support, response targets, and exclusions. Professional services are scoped separately. The applicable agreement and order form determine coverage for your deployment. Open source or enterprise ## Choose based on operating responsibility, not gateway performance Apache APISIX and API7 Enterprise share the APISIX foundation. The commercial value is the operating layer around it: governance, lifecycle, coordination, and support. | Decision area | Apache APISIX | API7 Enterprise | | -------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | Product model | Independent Apache-2.0 open-source project | Commercial API management product built on the APISIX core | | Operations | Your team installs, upgrades, patches, and monitors | Your team operates the deployment; API7 provides the agreed commercial tooling and assistance | | Governance | Community management capabilities and self-built processes | Centralized RBAC, gateway groups, audit, and multi-team controls | | API publishing | API documentation and developer workflows use tools you integrate | API7 Portal for API products, developer subscriptions, and credentials | | Support | Community channels and self-service documentation | Subscription support under an agreed plan; project services scoped separately | [Read the Detailed APISIX vs API7 Enterprise Comparison](https://api7.ai/api7-enterprise-vs-apisix) ## Evaluating a dedicated gateway for AI traffic? AISIX AI Gateway is a separate API7 product suite for model, MCP, and agent traffic. Review it when your requirement extends beyond support for an existing Apache APISIX deployment. [Explore AISIX AI Gateway](https://api7.ai/ai-gateway) Common scenarios ## Where a commercial path can reduce uncertainty Use these scenarios to identify whether you need a support or project engagement for your existing deployment, or API7 Enterprise management capabilities. 01 ### Move an APISIX evaluation into production Define the deployment model, operational ownership, upgrade path, observability, and support model before traffic becomes business-critical. 02 ### Standardize gateway operations across teams Evaluate API7 Enterprise gateway groups, operator RBAC, and configuration audits when coordinating multiple teams or environments. 03 ### Migrate from another API gateway Plan a staged transition for routes, authentication, traffic policies, plugins, and operational tooling with commercial assistance from API7. 04 ### Operate across hybrid or multiple clouds Review API7 Enterprise when you need to manage customer-operated gateway groups across hybrid or multiple-cloud environments. 05 ### Plan upgrades for business-critical gateways Review version compatibility, configuration changes, rollback requirements, and security updates before upgrading a production APISIX deployment. 06 ### Add expert guidance for production operations Plan product training or an architecture-review project before a rollout or upgrade, with deliverables and operational responsibilities agreed in advance. Customer proof ## APISIX technology in demanding production environments These published customer stories show the kinds of scale, data-sovereignty, migration, and operational requirements that can lead teams to evaluate a commercial API7 path. Airwallex ### Dynamic routing for data sovereignty Airwallex's published story describes using an API7 solution based on APISIX for dynamic routing, tenant-level controls, private deployment, and data-sovereignty requirements across global payment operations. [Read the Airwallex story](https://api7.ai/customers/airwallex) vivo ### Gateway standardization at large scale vivo's published story describes APISIX-based cluster management, migration from NGINX, cloud-native adoption, and production traffic approaching one million QPS. [Read the vivo story](https://api7.ai/customers/vivo) FAQ ## Questions teams ask before choosing a commercial path Use these answers to identify the next conversation, then confirm product and service details directly with API7. ### Does Apache APISIX have an enterprise edition? Apache APISIX itself remains a free, independent Apache Software Foundation project. API7 Enterprise is a separate commercial API management product built on the APISIX runtime, with gateway-group management, operator RBAC, configuration audits, API publishing, and agreed support. ### Who provides commercial support for Apache APISIX? API7 can discuss commercial assistance for an existing Apache APISIX deployment. Before purchasing, [contact API7](https://api7.ai/contact) to confirm service availability, covered products and versions, and the engagement scope. Subscription support and professional project services have separate terms. ### Can API7 help with an existing APISIX deployment? Start with the APISIX environment you already run: share its version, topology, plugins, and the problem or migration goal. API7 can assess the available support or project options and confirm coverage before engagement. Adopting API7 Enterprise is a separate decision. ### What is the difference between Apache APISIX and API7 Enterprise? Apache APISIX is the open-source gateway that your team deploys and operates. API7 Enterprise uses the APISIX runtime and adds gateway-group management, operator RBAC, configuration audits, and API7 Portal for publishing APIs to developers. Commercial support follows the selected plan and agreement. ### Can API7 help us migrate from Kong, NGINX, or another gateway? API7 product materials list migration assistance as an available commercial service. A real migration plan should inventory routes, plugins, authentication, traffic policies, observability, and rollout constraints before confirming scope and timing. ### Are migration and consulting included in subscription support? The API7 Technical Support Policy excludes professional services such as consulting, system design, and programming from subscription technical support. Migration, architecture review, training, and customization projects require a separately agreed scope and deliverables. ### Does commercial support mean API7 operates our gateway? In the self-operated APISIX path, your team remains responsible for the gateway and its infrastructure. A support or project-services discussion does not transfer that responsibility. Any additional operational responsibility must be stated in the applicable agreement. ### What should we prepare before contacting API7? Prepare your APISIX version, deployment topology, plugins and custom extensions, the problem or desired outcome, and rollout or rollback constraints. These details help define whether you need technical support, a professional-services project, or an enterprise platform evaluation. ### Should we keep APISIX or move to API7 Enterprise? Keep self-operated APISIX when your team wants open-source control and can own deployment, upgrades, security, and operations. If you only need expert assistance, discuss the scope for your existing deployment. Evaluate API7 Enterprise separately when you need its centralized management, multi-team controls, or API publishing capabilities. ## Tell us how you are using—or evaluating—Apache APISIX Share your deployment, migration, governance, or support requirements. API7 can help you identify which operating path is relevant and what still belongs in your own platform team. [Discuss Your APISIX Deployment](https://api7.ai/contact)[Review API7 Plans](https://api7.ai/pricing)