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.
Confirm the available services and engagement scope directly with API7.
Choose the operating model that fits
Apache APISIX
Self-operated open source
Commercial support
Help for existing deployments
API7 Enterprise
Gateway governance and API publishing
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.
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.
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.
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.
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 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 |
Evaluating a dedicated gateway for AI traffic?
AISIX AI Gateway is a separate API7 product for model, MCP, and agent traffic. Review it when your requirement extends beyond support for an existing Apache APISIX deployment.
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 storyvivo
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 storyFAQ
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.
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.