---
title: "WebAssembly Plugins for API Gateways: Portability, Isolation, and APISIX Boundaries - API7.ai"
description: "Evaluate Proxy-Wasm extensions by host compatibility, execution phase, isolation boundary, supply chain, and safe rollout in Apache APISIX."
url: "https://api7.ai/learning-center/api-gateway-guide/api-gateway-webassembly-plugins"
---

[Skip to article](#column-content)

Column contentsAPI Gateway Guide

[API Gateway Guide](https://api7.ai/learning-center/api-gateway-guide)

Search this column

01 Gateway Fundamentals

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=fundamentals)[1. What Is an API Gateway? API Gateway Software and Use Cases](https://api7.ai/learning-center/api-gateway-guide/what-is-an-api-gateway)[2. Why Do Modern Architectures Need an API Gateway?](https://api7.ai/learning-center/api-gateway-guide/why-do-modern-architectures-need-api-gateway)[3. Reverse Proxy vs Load Balancer vs API Gateway](https://api7.ai/learning-center/api-gateway-guide/api-gateway-vs-reverse-proxy-vs-load-balancer)[4. API Gateway and Microservices: Decoupling and Traffic Management](https://api7.ai/learning-center/api-gateway-guide/api-gateway-and-microservices)[5. Understanding Core API Gateway Features](https://api7.ai/learning-center/api-gateway-guide/core-api-gateway-features)[6. Open Source vs. Commercial API Gateways: How to Choose the Right One?](https://api7.ai/learning-center/api-gateway-guide/open-source-vs-commercial-api-gateway)[7. API Gateway vs Service Mesh: How to Choose?](https://api7.ai/learning-center/api-gateway-guide/api-gateway-vs-service-mesh)[8. Envoy vs NGINX, Java, and Go for API Gateways](https://api7.ai/learning-center/api-gateway-guide/nginx-vs-envoy-vs-java-vs-go)[9. Core Concepts of API Gateway: Service, Route, Upstream, Plugin, and Consumer](https://api7.ai/learning-center/api-gateway-guide/core-concepts-of-api-gateway)[10. API Gateway Comparison: Apache APISIX vs. Kong vs. Traefik vs. KrakenD vs. Tyk](https://api7.ai/learning-center/api-gateway-guide/api-gateway-comparison-apisix-kong-traefik-krakend-tyk)

02 Gateway Architecture and Design

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=architecture)[11. Deep Dive into API Gateway Architecture: Core Components and Design Principles](https://api7.ai/learning-center/api-gateway-guide/api-gateway-architecture)[12. Choosing the Right API Gateway for Your Architecture](https://api7.ai/learning-center/api-gateway-guide/api-gateway-monolithic-vs-microservices)[13. How to Architect an API Gateway for High Availability (HA)?](https://api7.ai/learning-center/api-gateway-guide/api-gateway-high-availability)[14. API Gateway Plugin Architecture: How to Extend and Customize Your API Gateway](https://api7.ai/learning-center/api-gateway-guide/api-gateway-plugin-system)[15. How Event-Driven Architecture (EDA) Works with API Gateway?](https://api7.ai/learning-center/api-gateway-guide/api-gateway-event-driven-architecture)[16. API Gateway Request Lifecycle Explained](https://api7.ai/learning-center/api-gateway-guide/api-gateway-request-lifecycle-explained)[17. Cloud-Native API Gateway on Kubernetes](https://api7.ai/learning-center/api-gateway-guide/cloud-native-api-gateway-kubernetes)[18. API Gateway Control Plane vs. Data Plane](https://api7.ai/learning-center/api-gateway-guide/api-gateway-control-plane-vs-data-plane)[19. How API Gateways Work with GitOps: Automating API Management](https://api7.ai/learning-center/api-gateway-guide/api-gateway-gitops-integration)[20. How to Perform A/B Testing and Canary Releases with an API Gateway](https://api7.ai/learning-center/api-gateway-guide/ab-testing-canary-release-api-gateway)

03 Gateway Setup and Traffic Handling

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=traffic-protocols)[21. How to Deploy an API Gateway on Kubernetes: Step-by-Step Guide for Engineers](https://api7.ai/learning-center/api-gateway-guide/deploy-api-gateway-on-kubernetes)[22. Hands-on Setup with Apache APISIX API Gateway](https://api7.ai/learning-center/api-gateway-guide/api-gateway-getting-started-guide)[23. API Gateway Auth: OAuth 2.0, JWT & OIDC with APISIX](https://api7.ai/learning-center/api-gateway-guide/api-gateway-authentication-apache-apisix-oauth-jwt-oidc)[24. Mastering Traffic Control: Efficiently Managing API Requests with Gateways](https://api7.ai/learning-center/api-gateway-guide/api-gateway-traffic-control-strategies)[25. Building Reliable API Gateways with Logging and Monitoring](https://api7.ai/learning-center/api-gateway-guide/api-gateway-logging-monitoring-best-practices)[26. Dynamic Routing in API Gateways: Best Practices for Flexible Traffic Management](https://api7.ai/learning-center/api-gateway-guide/api-gateway-dynamic-routing-management)[27. How API Gateways Support WebSocket](https://api7.ai/learning-center/api-gateway-guide/how-api-gateways-support-websocket)[28. API Gateway for GraphQL: Security, Cost, and Caching](https://api7.ai/learning-center/api-gateway-guide/api-gateway-handle-graphql)[29. How API Gateways Handle HTTP/3 QUIC Requests](https://api7.ai/learning-center/api-gateway-guide/api-gateway-http3-quic)[30. How API Gateways Handle MQTT Requests](https://api7.ai/learning-center/api-gateway-guide/api-gateway-mqtt)

04 Gateway Integrations, AI, and MCP

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=ai-mcp)[31. How API Gateways Handle gRPC Requests](https://api7.ai/learning-center/api-gateway-guide/api-gateway-grpc-support)[32. How API Gateways Implement Custom Plugins](https://api7.ai/learning-center/api-gateway-guide/api-gateway-custom-plugins)[33. How API Gateways Integrate with Kafka](https://api7.ai/learning-center/api-gateway-guide/api-gateway-kafka-integration)[34. How to Implement API Aggregation in API Gateways](https://api7.ai/learning-center/api-gateway-guide/api-gateway-api-aggregation)[35. How API Gateways Enable Serverless Architecture](https://api7.ai/learning-center/api-gateway-guide/api-gateway-serverless-architecture)[36. How API Gateways Proxy LLM Requests](https://api7.ai/learning-center/api-gateway-guide/api-gateway-proxy-llm-requests)[37. How API Gateways Enhance MCP Servers](https://api7.ai/learning-center/api-gateway-guide/api-gateway-enhance-mcp-server)[38. MCP Gateway vs MCP Proxy vs AI Gateway vs API Gateway](https://api7.ai/learning-center/api-gateway-guide/ai-gateway-vs-mcp-gateway-vs-api-gateway)[39. What Is an AI Gateway? Architecture and Benefits](https://api7.ai/learning-center/api-gateway-guide/what-is-an-ai-gateway)[40. What Is an MCP Gateway? Architecture, Use Cases & How It Works (2026 Guide)](https://api7.ai/learning-center/api-gateway-guide/what-is-mcp-gateway)

05 Gateway Performance

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=performance)[41. How API Gateway Reduces Latency: Performance Optimization Strategies](https://api7.ai/learning-center/api-gateway-guide/how-api-gateway-reduces-latency)[42. API Gateway Caching Strategy: Comprehensive Analysis and Implementation Guide](https://api7.ai/learning-center/api-gateway-guide/api-gateway-caching-strategy-analysis)[43. How to Optimize API Gateway Load Balancing: Advanced Strategies and Best Practices](https://api7.ai/learning-center/api-gateway-guide/how-to-optimize-api-gateway-load-balancing)[44. How API Gateway Efficiently Handles Large-Scale Traffic: Architecture and Strategies](https://api7.ai/learning-center/api-gateway-guide/how-api-gateway-handles-large-scale-traffic)[45. How to Improve API Gateway QoS: Traffic Classes, Capacity Protection, and SLOs](https://api7.ai/learning-center/api-gateway-guide/api-gateway-quality-of-service)[46. API Gateway Log Storage: Pipelines, Retention, Security, and Cost](https://api7.ai/learning-center/api-gateway-guide/api-gateway-log-storage)[47. API Gateway Timeouts and Retries: Safe Policies and APISIX Configuration](https://api7.ai/learning-center/api-gateway-guide/api-gateway-timeouts-retries)[48. API Gateway Concurrency Control: Capacity Budgets, Backpressure, and Load Shedding](https://api7.ai/learning-center/api-gateway-guide/api-gateway-concurrency-control)[49. Asynchronous API Gateway Patterns: Queues, Callbacks, and Performance Boundaries](https://api7.ai/learning-center/api-gateway-guide/asynchronous-api-gateway-patterns)[50. API Gateway TLS Performance: Handshakes, Session Reuse, and Measurement](https://api7.ai/learning-center/api-gateway-guide/api-gateway-tls-performance)

06 Gateway Security

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=security)[51. DDoS Defense at the API Gateway: Layered Controls and Failure Planning](https://api7.ai/learning-center/api-gateway-guide/api-gateway-ddos-defense)[52. Distributed API Gateway Rate Limiting: Local vs Redis Counters and Accuracy Trade-offs](https://api7.ai/learning-center/api-gateway-guide/distributed-api-gateway-rate-limiting)[53. API Gateway IP Allowlist and Denylist Management: Trust, Proxies, and Operations](https://api7.ai/learning-center/api-gateway-guide/api-gateway-ip-allowlist-denylist-management)[54. API Gateway Security Scanning: What to Test and How to Operationalize Findings](https://api7.ai/learning-center/api-gateway-guide/api-gateway-security-scanning)[55. SQL Injection and XSS at the API Gateway: Detection Limits and Defense in Depth](https://api7.ai/learning-center/api-gateway-guide/sql-injection-xss-api-gateway)[56. API Access Log Auditing: Evidence, Integrity, Retention, and Review](https://api7.ai/learning-center/api-gateway-guide/api-access-log-auditing)[57. Preventing API Scraping and Abuse: Identity, Behavioral Signals, and Rate Controls](https://api7.ai/learning-center/api-gateway-guide/prevent-api-scraping-abuse)[58. API Gateway mTLS: Client Identity, Certificate Rotation, and APISIX Configuration](https://api7.ai/learning-center/api-gateway-guide/api-gateway-mtls)[59. Fine-Grained API Gateway Authorization: RBAC, ABAC, and External Policy Decisions](https://api7.ai/learning-center/api-gateway-guide/fine-grained-api-gateway-authorization)[60. API Gateway and WAF Reference Architecture: Ownership, Header Trust, and Failure Modes](https://api7.ai/learning-center/api-gateway-guide/api-gateway-waf-reference-architecture)

07 Gateway Ecosystem and Comparisons

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=ecosystem)[61. Apache APISIX vs Kong: Migration, Operations, and Team Fit](https://api7.ai/learning-center/api-gateway-guide/apache-apisix-vs-kong)[62. Traefik vs Kong vs APISIX: A Reproducible API Gateway Benchmark Method](https://api7.ai/learning-center/api-gateway-guide/traefik-kong-apisix-benchmark-method)[63. Amazon API Gateway Explained: Deployment Models, Trade-offs, and Use Cases](https://api7.ai/learning-center/api-gateway-guide/amazon-api-gateway-explained)[64. API Gateway and Istio: Clear North-South and East-West Boundaries](https://api7.ai/learning-center/api-gateway-guide/api-gateway-istio)[65. API Gateway with NGINX: Layering, Ownership, and Migration Patterns](https://api7.ai/learning-center/api-gateway-guide/api-gateway-nginx)[66. API Gateway with Envoy: Deployment Patterns and Policy Ownership](https://api7.ai/learning-center/api-gateway-guide/api-gateway-envoy)[67. API Gateway with Cloudflare API Shield: Edge and Origin Security Boundaries](https://api7.ai/learning-center/api-gateway-guide/api-gateway-cloudflare-api-shield)[68. Apigee vs MuleSoft vs Amazon API Gateway: A Decision Framework](https://api7.ai/learning-center/api-gateway-guide/apigee-mulesoft-amazon-api-gateway)[69. Should an API Gateway Connect Directly to a Database? Patterns and Risks](https://api7.ai/learning-center/api-gateway-guide/api-gateway-database-access-patterns)[70. API Gateway Architecture for Large-Scale SaaS Platforms](https://api7.ai/learning-center/api-gateway-guide/api-gateway-large-scale-saas-architecture)

08 Industry Applications and Integrations

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=applications)[71. API Gateway CI/CD: Validation, Promotion, and Safe Rollback](https://api7.ai/learning-center/api-gateway-guide/api-gateway-ci-cd)[72. API Gateways for AI and ML Inference: Traffic, Security, and Observability](https://api7.ai/learning-center/api-gateway-guide/api-gateways-ai-ml-inference)[73. API Gateway Architecture for Financial Services: Controls and Failure Boundaries](https://api7.ai/learning-center/api-gateway-guide/api-gateway-financial-services)[74. API Gateway Architecture for E-Commerce: Checkout Reliability and Traffic Peaks](https://api7.ai/learning-center/api-gateway-guide/api-gateway-ecommerce)[75. API Gateways for Mobile Applications: Authentication, Payloads, and Versioning](https://api7.ai/learning-center/api-gateway-guide/api-gateways-mobile-applications)[76. API Gateways for Web3 Applications: RPC Traffic, Identity, and Abuse Controls](https://api7.ai/learning-center/api-gateway-guide/api-gateways-web3-applications)[77. OpenAPI-Driven API Gateway Operations: Import, Validation, and Drift Control](https://api7.ai/learning-center/api-gateway-guide/openapi-driven-api-gateway-operations)[78. gRPC-Web and gRPC Transcoding Through an API Gateway](https://api7.ai/learning-center/api-gateway-guide/grpc-web-grpc-transcoding-api-gateway)[79. API Gateway Pricing and Cost Optimization: A Workload-Based Model](https://api7.ai/learning-center/api-gateway-guide/api-gateway-pricing-cost-optimization)[80. Evaluating API Gateway Directions: Evidence and Architectural Impact](https://api7.ai/learning-center/api-gateway-guide/api-gateway-trends)

09 Advanced Gateway Applications

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=operations)[81. API Gateways in Zero Trust Architecture: Identity, Policy, and Limits](https://api7.ai/learning-center/api-gateway-guide/api-gateways-zero-trust-architecture)[82. API Gateway Log Analytics: Correlation, Queries, and Operational Signals](https://api7.ai/learning-center/api-gateway-guide/api-gateway-log-analytics)[83. From API Sprawl to Governed Delivery: The Gateway's Role in Modernization](https://api7.ai/learning-center/api-gateway-guide/api-gateway-modernization)[84. API Monetization at the Gateway: Plans, Metering, Entitlements, and Billing Boundaries](https://api7.ai/learning-center/api-gateway-guide/api-monetization-gateway)[85. Safe AI-Assisted API Gateway Optimization: Recommendations, Guardrails, and Approval](https://api7.ai/learning-center/api-gateway-guide/ai-assisted-api-gateway-optimization)[86. API Gateways for Low-Code and No-Code Integration: Governance and Safety](https://api7.ai/learning-center/api-gateway-guide/api-gateways-low-code-no-code-integration)[87. API Gateway and CIAM Integration: Token Validation, Consent, and Identity Context](https://api7.ai/learning-center/api-gateway-guide/api-gateway-ciam-integration)[88. Elastic API Gateway Scaling: Signals, Capacity, and Safe Scale-In](https://api7.ai/learning-center/api-gateway-guide/elastic-api-gateway-scaling)[89. Multi-Tenant SaaS API Gateways: Isolation, Quotas, and Tenant-Aware Policy](https://api7.ai/learning-center/api-gateway-guide/multi-tenant-saas-api-gateway-policy)[90. API Gateway DevSecOps: Policy as Code, Testing, and Runtime Feedback](https://api7.ai/learning-center/api-gateway-guide/api-gateway-devsecops)

10 Platform Engineering and Planning

[View this topic · 10](https://api7.ai/learning-center/api-gateway-guide?topic=platform-governance)[91. API Discovery and Documentation at the Gateway: Inventory, Ownership, and Drift](https://api7.ai/learning-center/api-gateway-guide/api-discovery-documentation-gateway)[92. WebAssembly Plugins for API Gateways: Portability, Isolation, and APISIX Boundaries](https://api7.ai/learning-center/api-gateway-guide/api-gateway-webassembly-plugins)[93. Monitoring API Gateways with Prometheus and Grafana: Metrics, Dashboards, and Alerts](https://api7.ai/learning-center/api-gateway-guide/monitor-api-gateways-prometheus-grafana)[94. API Gateway Reliability Engineering: SLOs, Failure Isolation, and Incident Response](https://api7.ai/learning-center/api-gateway-guide/api-gateway-reliability-engineering)[95. API Gateways for Edge AI Inference: Routing, Constraints, and Observability](https://api7.ai/learning-center/api-gateway-guide/api-gateways-edge-ai-inference)[96. Reducing Cloud Cost with API Gateway Controls: Measurement Before Optimization](https://api7.ai/learning-center/api-gateway-guide/reducing-cloud-cost-api-gateway-controls)[97. Improving API Developer Experience with Gateway Standards and Self-Service](https://api7.ai/learning-center/api-gateway-guide/improving-api-developer-experience-gateway-self-service)[98. API Gateway Change Management: Compatibility, Progressive Delivery, and Rollback](https://api7.ai/learning-center/api-gateway-guide/api-gateway-change-management-rollback)[99. Operating Serverless APIs: Cold Starts, Idempotency, and Asynchronous Handoffs](https://api7.ai/learning-center/api-gateway-guide/operating-serverless-apis-gateway)[100. Planning an API Gateway Roadmap for the Next Five Years](https://api7.ai/learning-center/api-gateway-guide/planning-api-gateway-roadmap-next-five-years)

[API Gateway Guide](https://api7.ai/learning-center/api-gateway-guide)[Platform Engineering and Planning](https://api7.ai/learning-center/api-gateway-guide?topic=platform-governance)

On this page

On this page

- [Key Takeaways](#key-takeaways)

- [Define the Portability Contract](#define-the-portability-contract)

- [Place the Extension in the Request Lifecycle](#place-the-extension-in-the-request-lifecycle)

- [Understand the APISIX 3.19 Boundary](#understand-the-apisix-319-boundary)

- [Separate Four Kinds of Isolation](#separate-four-kinds-of-isolation)

- [Build a Release Unit, Not a Loose Binary](#build-a-release-unit-not-a-loose-binary)

- [Test Failure and Rollback Paths](#test-failure-and-rollback-paths)

- [Roll Out with an Explicit Blast Radius](#roll-out-with-an-explicit-blast-radius)

- [WebAssembly Plugin Checklist](#webassembly-plugin-checklist)

- [FAQ](#faq)

  - [Is a Proxy-Wasm plugin portable across all API gateways?](#is-a-proxy-wasm-plugin-portable-across-all-api-gateways)
  - [Does Wasm make third-party plugins safe to run in production?](#does-wasm-make-third-party-plugins-safe-to-run-in-production)
  - [Should every custom gateway plugin use Wasm?](#should-every-custom-gateway-plugin-use-wasm)

- [Next Steps](#next-steps)

Article 92

# WebAssembly Plugins for API Gateways: Portability, Isolation, and APISIX Boundaries

API7.ai

October 29, 2026

WebAssembly (Wasm) can let a platform team distribute a gateway extension as a portable binary instead of rebuilding the gateway for every change. The useful contract, however, is not “compile once and run everywhere.” It is: compile to a supported Proxy-Wasm ABI, use only host calls implemented by the target gateway, and validate the module against that exact gateway version and execution phase.

Wasm also narrows the interface between an extension and its host, but it does not make an untrusted module harmless. Supply-chain controls, resource limits, rollout isolation, and recovery behavior remain platform responsibilities.

## Key Takeaways

- Treat Proxy-Wasm compatibility as an ABI-plus-host-capabilities contract, not only a `.wasm` file format.
- Confirm callback phase, request/response body access, and failure behavior before choosing Wasm for a plugin.
- Separate memory sandboxing from process, tenant, resource, and supply-chain isolation.
- In Apache APISIX 3.19.0, only part of the Proxy-Wasm API is implemented and all Wasm plugins run in the same Wasm VM.
- Pin the module digest, SDK and ABI, test fixtures, gateway release, configuration, and rollback artifact as one release unit.
- Canary by gateway instance or traffic slice so a faulty extension cannot consume the whole fleet's error budget.

## Define the Portability Contract

[Proxy-Wasm](https://github.com/proxy-wasm/spec) specifies an ABI and conventions between L4/L7 proxy hosts and Wasm extensions. A language SDK turns higher-level plugin code into calls across that ABI. A gateway host decides which ABI version, callbacks, properties, and host functions it implements.

That produces four compatibility layers:

| Layer               | Question to answer                                                                    |
| ------------------- | ------------------------------------------------------------------------------------- |
| Wasm binary         | Can the selected runtime validate and instantiate the module?                         |
| Proxy-Wasm ABI      | Which ABI version did the SDK target?                                                 |
| Host implementation | Which callbacks, properties, and host calls does this gateway release implement?      |
| Gateway semantics   | In which phase does the callback run, and what can still be changed or rejected then? |

A module can be valid Wasm and still fail because the host does not implement a required Proxy-Wasm call. It can also load successfully but behave differently because two gateways expose different properties, buffering rules, or lifecycle behavior. Maintain a per-host compatibility suite instead of inferring support from the file extension.

## Place the Extension in the Request Lifecycle

```
flowchart LR
    C[Client] --> R[Gateway rewrite phase]
    R --> A[Gateway access phase]
    A --> U[Upstream service]
    U --> H[Response header filter]
    H --> B[Response body filter]
    B --> C
    W[Proxy-Wasm module] -. host calls within supported callbacks .-> R
    W -. host calls within supported callbacks .-> A
    W -. host calls within supported callbacks .-> H
    W -. host calls within supported callbacks .-> B
```

Phase changes meaning. A request rewrite can normalize routing inputs before access policy runs. An access callback can reject a request before proxying. A response-body callback runs after the upstream has responded and may be too late to change an already committed status. Body inspection can also require buffering and copying that header-only logic avoids.

For each callback, record:

- the input the module can read and who supplied it;
- the fields it can mutate;
- whether the response has begun;
- the maximum body and execution cost;
- what the client receives on a trap, timeout, or invalid result;
- whether the platform fails open, fails closed, or removes the extension from service.

Do not call a header, property, or context value trusted identity merely because the host exposes it. Authentication status and the origin of a value still determine whether downstream policy may rely on it.

## Understand the APISIX 3.19 Boundary

Apache APISIX 3.19.0 [supports plugins written with a Proxy-Wasm SDK](https://apisix.apache.org/docs/apisix/3.19/wasm/), but its documentation also states that only a few APIs are currently implemented. Compatibility must therefore be proven against APISIX, not inferred from another Proxy-Wasm host.

Its documented programming model has several scopes:

- all Wasm plugins run in the same Wasm VM;
- each plugin has its own `VMContext`;
- each configured Route or Global Rule has a `PluginContext`;
- each matching HTTP request has an `HttpContext`.

These contexts organize lifecycle and state. They are not separate operating-system processes or tenant sandboxes. A Wasm module still executes inside the gateway data-plane process and can consume latency, CPU, memory, or host-call capacity on the request path.

APISIX maps request-header callbacks to either `access` or `rewrite`. The default is `access`; selecting `rewrite` moves the callback earlier. Those two paths can observe different gateway state and affect which later policies see a mutation. Request-body and response-body callbacks are not automatic: the plugin must request them by setting the documented `wasm_process_req_body` or `wasm_process_resp_body` property from the corresponding header callback.

The following is an APISIX 3.19.0 `config.yaml` excerpt, not a complete deployment:

```
wasm:
  plugins:
    - name: request_guard
      priority: 7999
      file: /opt/apisix/wasm/request-guard.wasm
      http_request_phase: access
```

With `http_request_phase: access`—the default—the request-header callback runs in access. With `http_request_phase: rewrite`, it runs in rewrite. Changing the setting does not merely optimize timing; it changes the policy sequence and must be regression-tested with every plugin that reads or modifies the same request.

The Route supplies plugin context through `conf`:

```
{
  "uri": "/orders/*",
  "plugins": {
    "request_guard": {
      "conf": {
        "policy": "orders-read-v3"
      }
    }
  },
  "upstream_id": "orders"
}
```

This is a configuration excerpt. The module, upstream, Admin API authentication, and test service are omitted. Treat `conf` as untrusted until the module validates its shape and bounds; a control-plane write is not proof that every field is safe to use.

## Separate Four Kinds of Isolation

The [WebAssembly security model](https://webassembly.org/docs/security/) isolates module memory from the host and requires interaction through the embedding's APIs. That is valuable fault containment, but production isolation has more dimensions:

| Boundary                   | What it addresses                           | What still needs an operator control                                 |
| -------------------------- | ------------------------------------------- | -------------------------------------------------------------------- |
| Memory sandbox             | Direct arbitrary access to host memory      | Runtime vulnerabilities and unsafe host functions                    |
| Capability boundary        | Which host calls and properties are exposed | Least-privilege host API design and compatibility review             |
| Resource boundary          | CPU, memory, body buffering, side calls     | Enforced limits, load tests, and overload behavior                   |
| Process or tenant boundary | Blast radius across plugins and tenants     | Separate gateway pools or out-of-process execution where required    |
| Supply-chain boundary      | Which binary was built and approved         | Reproducible build, signature/digest, SBOM, scanning, and provenance |

APISIX's shared-VM design makes the last-mile test especially important: do not claim per-plugin VM isolation that the documented host model does not provide. For mutually untrusted tenants or strict fault-containment requirements, separate data-plane pools may be a more appropriate boundary.

## Build a Release Unit, Not a Loose Binary

Version these artifacts together:

1. source commit and locked dependencies;
2. language SDK and Proxy-Wasm ABI version;
3. compiler and build flags;
4. module digest and signature or attestation;
5. required host calls and properties;
6. APISIX release and runtime build;
7. static module registration and Route/Global Rule configuration;
8. conformance, load, fault, and rollback tests.

Load modules from an operator-controlled, read-only path. Verify the digest before rollout. A Route should reference an approved plugin name and bounded configuration; it should not let a tenant provide an arbitrary filesystem path or downloadable module.

## Test Failure and Rollback Paths

Use fixtures that cover more than the successful request:

- missing or malformed plugin configuration;
- callback trap and invalid host-call result;
- maximum allowed header and body sizes;
- slow or failing side calls, if the host supports them;
- first request after configuration activation;
- concurrent requests using distinct `HttpContext` instances;
- Route plus Global Rule activation on the same request;
- response already started before a body-phase failure;
- worker restart, configuration reload, canary removal, and rollback.

Measure gateway latency and error rate with the extension disabled and enabled under the same workload. A module that is functionally correct but consumes the request-path budget is still unsafe to promote.

## Roll Out with an Explicit Blast Radius

Prefer a dedicated canary gateway pool or a controlled traffic slice. Promotion gates should include request success, latency, traps, worker restarts, memory growth, body-buffer pressure, and application correctness. Keep the prior module and configuration together so rollback cannot pair an old binary with an incompatible new `conf` shape.

If the extension enforces security policy, define what happens when it cannot run. Failing open preserves availability but may bypass the control; failing closed preserves the control but can cause an outage. Make that decision visible in the threat model, alerting, and incident runbook rather than relying on an accidental runtime default.

## WebAssembly Plugin Checklist

- Which Proxy-Wasm ABI and SDK version produced the module?
- Does APISIX 3.19 implement every required callback, property, and host call?
- Is the request callback intentionally in `access` or `rewrite`?
- Are body callbacks necessary, bounded, and explicitly enabled?
- Is every identity or routing input traced to a trusted source?
- Are module digest, provenance, and dependencies verified before loading?
- Are CPU, memory, body, and side-call costs tested under concurrency?
- Does the required tenant boundary exceed APISIX's documented shared-VM model?
- Are trap, overload, first-request, response-started, and rollback paths tested?
- Can operators remove the module without rebuilding or corrupting Route configuration?

## FAQ

### Is a Proxy-Wasm plugin portable across all API gateways?

No. The ABI improves portability, but the target host must implement the callbacks, properties, and host calls the module uses. Test each gateway product and version.

### Does Wasm make third-party plugins safe to run in production?

Not by itself. The memory sandbox reduces one class of risk. The module still needs provenance, capability, resource, tenant, rollout, and recovery controls.

### Should every custom gateway plugin use Wasm?

No. Use a built-in plugin when it already provides the behavior. Choose Wasm when its language and distribution benefits outweigh host-API gaps and runtime cost. Use an external service or plugin runner when stronger process isolation or broader libraries matter more.

## Next Steps

Map the extension to the [API gateway request lifecycle](https://api7.ai/learning-center/api-gateway-guide/api-gateway-request-lifecycle-explained), then deliver it through [gateway DevSecOps controls](https://api7.ai/learning-center/api-gateway-guide/api-gateway-devsecops) and [safe gateway CI/CD](https://api7.ai/learning-center/api-gateway-guide/api-gateway-ci-cd).

[Previous article**API Discovery and Documentation at the Gateway: Inventory, Ownership, and Drift**](https://api7.ai/learning-center/api-gateway-guide/api-discovery-documentation-gateway)[Next article**Monitoring API Gateways with Prometheus and Grafana: Metrics, Dashboards, and Alerts**](https://api7.ai/learning-center/api-gateway-guide/monitor-api-gateways-prometheus-grafana)

On this page

- [Key Takeaways](#key-takeaways)

- [Define the Portability Contract](#define-the-portability-contract)

- [Place the Extension in the Request Lifecycle](#place-the-extension-in-the-request-lifecycle)

- [Understand the APISIX 3.19 Boundary](#understand-the-apisix-319-boundary)

- [Separate Four Kinds of Isolation](#separate-four-kinds-of-isolation)

- [Build a Release Unit, Not a Loose Binary](#build-a-release-unit-not-a-loose-binary)

- [Test Failure and Rollback Paths](#test-failure-and-rollback-paths)

- [Roll Out with an Explicit Blast Radius](#roll-out-with-an-explicit-blast-radius)

- [WebAssembly Plugin Checklist](#webassembly-plugin-checklist)

- [FAQ](#faq)

  - [Is a Proxy-Wasm plugin portable across all API gateways?](#is-a-proxy-wasm-plugin-portable-across-all-api-gateways)
  - [Does Wasm make third-party plugins safe to run in production?](#does-wasm-make-third-party-plugins-safe-to-run-in-production)
  - [Should every custom gateway plugin use Wasm?](#should-every-custom-gateway-plugin-use-wasm)

- [Next Steps](#next-steps)
