Self-hosted APISIX as the API gateway in sectors with regulated data, partner APIs or restricted networks, and the plugins and controls each sector usually needs.
APISIX for banks, insurers and payment providers: partner and open banking style APIs, mTLS and HMAC for machine clients, PCI DSS and DORA evidence, rate limits per partner and self-hosting in regulated data centers.
APISIX in front of clinical and patient-facing APIs: protecting FHIR servers, OpenID Connect for apps, HIPAA transmission security and audit logging, and keeping PHI out of gateway logs.
APISIX for agencies exposing citizen and inter-agency APIs: sovereign or air-gapped hosting, open-source licensing for procurement, strong authentication, WAF inspection and data exchange with other public bodies.
APISIX as the public API edge of a SaaS product: API keys and OAuth for customers, per-plan rate limits and usage billing, AI gateway features for LLM-powered products, and SOC 2 evidence.
APISIX for plants and connected products: MQTT proxying for devices, TCP stream routes for industrial protocols, mTLS device identity, and separating OT networks from cloud and partner APIs.
APISIX for grid operators and utilities: APIs for meter data and market partners, segmentation from control systems, NIS2 cryptography and access requirements, and resilient gateways across regions.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.