> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Gateway (REST) costs

> Compare API Gateway (REST) backend choices using explicit service-adapter planning assumptions.

Tensor9 Cloud Adapter planning comparisons for `aws::1.0.0::api-gateway::v1`, with backend choices shown together. Read [how Tensor9 estimates service-adapter costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) for price scope and capacity qualification, or return to [additional services](https://docs.tensor9.com/cloud-adapter-early-access/costs/additional-services.md).

## API Gateway REST execution → Envoy

Origin API: `aws::1.0.0::api-gateway::v1`. Target backend: `envoy::1.0.0::proxy`.

### API Gateway REST execution · API execution requests per second

Feature: API Gateway REST execution.

Estimated monthly service charges by API execution requests per second. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![API Gateway REST execution · API execution requests per second: monthly service charges by API execution requests per second. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/adbbd8f31d9afa2c65f839718ac9dcc06bfb6fde0c4df5ebeef9533fb6cc378f-light.svg)

![API Gateway REST execution · API execution requests per second: monthly service charges by API execution requests per second. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/39966ae45ffb332839aeed1029128dcd1a3ea82cc3f6d14ea5c0bece4aea8eda-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| API execution requests per second (requests/s) | API Gateway (REST) | Target scenario | Envoy | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Envoy (one copy) | 80.90 | 80.90 |
| 0 | 0.00 | Envoy (two copies) | 161.79 | 161.79 |
| 1 | 9.20 | Envoy (one copy) | 82.10 | 72.90 |
| 1 | 9.20 | Envoy (two copies) | 163.00 | 153.80 |
| 10 | 91.98 | Envoy (one copy) | 92.93 | 0.95 |
| 10 | 91.98 | Envoy (two copies) | 173.82 | 81.84 |
| 100 | 919.80 | Envoy (one copy) | 201.20 | -718.60 |
| 100 | 919.80 | Envoy (two copies) | 282.09 | -637.71 |
| 1,000 | 9,198.00 | Envoy (one copy) | 1,193.89 | -8,004.11 |
| 1,000 | 9,198.00 | Envoy (two copies) | 1,274.78 | -7,923.22 |
| 10,000 | 91,980.00 | Envoy (one copy) | 8,631.04 | -83,348.96 |
| 10,000 | 91,980.00 | Envoy (two copies) | 8,924.63 | -83,055.37 |
| 100,000 | 919,800.00 | Envoy (one copy) | 83,930.65 | -835,869.35 |
| 100,000 | 919,800.00 | Envoy (two copies) | 87,343.66 | -832,456.34 |

Estimated allocation, not benchmark calibrated: sized from 2 vCPU, 8 GiB memory and 100 GiB SSD at 0 requests/s to 96 vCPU, 384 GiB memory and 100 GiB SSD at 100,000 requests/s.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Envoy (one copy) | Origin list price · API execution requests | 0.0000035 | USD/Requests |
| Envoy (one copy) | Origin list price · API management requests | 0 | USD/Requests |
| Envoy (one copy) | Proxy requests per vCPU-second | 4,000 | requests/vCPU-second |
| Envoy (one copy) | Target proxy CPU utilization | 0.7 | fraction |
| Envoy (one copy) | Peak / average execution requests | 2 | multiplier |
| Envoy (one copy) | Proxy CPU per replica | 0.5 | vCPU |
| Envoy (one copy) | Proxy RAM per replica | 0.375 | GiB |
| Envoy (one copy) | Minimum allocated proxy replicas | 2 | replicas |
| Envoy (one copy) | Billable response bytes per request | 4,096 | bytes |
| Envoy (one copy) | Target price guess · read | 0 | USD/read |
| Envoy (one copy) | Target price guess · write | 0 | USD/write |
| Envoy (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Envoy (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| Envoy (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Envoy (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Envoy (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Envoy (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Envoy (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Envoy (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Envoy (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Envoy (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Envoy (one copy) | Target price guess · input token | 0 | USD/input token |
| Envoy (one copy) | Target price guess · output token | 0 | USD/output token |
| Envoy (one copy) | Target monthly base charge | 0 | USD/month |
| Envoy (one copy) | Approximate target service minimum | 0 | USD/month |
| Envoy (one copy) | Minimum primary CPU | 2 | vCPU |
| Envoy (one copy) | Minimum primary RAM | 8 | GiB |
| Envoy (one copy) | Minimum primary disk | 100 | GiB |
| Envoy (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Envoy (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Envoy (one copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Envoy (one copy) | Planning peak / mean work | 2 | multiplier |
| Envoy (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Envoy (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Envoy (one copy) | Planning disk utilization | 0.8 | fraction |
| Envoy (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Envoy (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Envoy (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Envoy (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Envoy (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Envoy (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Envoy (two copies) | Origin list price · API execution requests | 0.0000035 | USD/Requests |
| Envoy (two copies) | Origin list price · API management requests | 0 | USD/Requests |
| Envoy (two copies) | Proxy requests per vCPU-second | 4,000 | requests/vCPU-second |
| Envoy (two copies) | Target proxy CPU utilization | 0.7 | fraction |
| Envoy (two copies) | Peak / average execution requests | 2 | multiplier |
| Envoy (two copies) | Proxy CPU per replica | 0.5 | vCPU |
| Envoy (two copies) | Proxy RAM per replica | 0.375 | GiB |
| Envoy (two copies) | Minimum allocated proxy replicas | 2 | replicas |
| Envoy (two copies) | Billable response bytes per request | 4,096 | bytes |
| Envoy (two copies) | Target price guess · read | 0 | USD/read |
| Envoy (two copies) | Target price guess · write | 0 | USD/write |
| Envoy (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Envoy (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| Envoy (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Envoy (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Envoy (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Envoy (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Envoy (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Envoy (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Envoy (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Envoy (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Envoy (two copies) | Target price guess · input token | 0 | USD/input token |
| Envoy (two copies) | Target price guess · output token | 0 | USD/output token |
| Envoy (two copies) | Target monthly base charge | 0 | USD/month |
| Envoy (two copies) | Approximate target service minimum | 0 | USD/month |
| Envoy (two copies) | Minimum primary CPU | 2 | vCPU |
| Envoy (two copies) | Minimum primary RAM | 8 | GiB |
| Envoy (two copies) | Minimum primary disk | 100 | GiB |
| Envoy (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Envoy (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Envoy (two copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Envoy (two copies) | Planning peak / mean work | 2 | multiplier |
| Envoy (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Envoy (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Envoy (two copies) | Planning disk utilization | 0.8 | fraction |
| Envoy (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Envoy (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Envoy (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Envoy (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Envoy (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Envoy (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices; capacity coefficients and translation assumptions are editable authored planning guesses, not measured capacity or a provider quote.
* Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
* Whole Envoy replica allocation grows with peak execution requests and selected utilization; the zero-traffic floor remains explicit.
* Native managed gateway backends price execution request meters; Envoy backends price the derived proxy resource-hours. Do not add both execution price paths.
* Self-hosted target: Envoy (Apache-2.0, [https://github.com/envoyproxy/envoy/blob/main/LICENSE](https://github.com/envoyproxy/envoy/blob/main/LICENSE)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor charge: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonApiGateway offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonApiGateway/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonApiGateway/current/us-east-1/index.json)
* Amazon API Gateway pricing: [https://aws.amazon.com/api-gateway/pricing/](https://aws.amazon.com/api-gateway/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Upstream Lambda/integration compute, external load balancer, DNS, certificates, cache, logs, custom authorizers and WebSocket connection minutes.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-2a4f249ddc740ae643c5edabb6cdf0d4390d3045` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonApiGateway offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonApiGateway/current/us-east-1/index.json), [Amazon API Gateway pricing](https://aws.amazon.com/api-gateway/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

See the [service catalog](https://docs.tensor9.com/cloud-adapter-early-access/service-catalog/aws/catalog.md) for operation coverage, supported directions and backend limitations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.