# Cloud Run GPUs vs Verda (slim)

> Cloud Run GPUs scores 68.4 (B) to Verda's 53.3 (D) for compute serverless. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.md (~4,750 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.json · canonical https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Cloud Run GPUs scores 68.4 (B) on agent readiness against Verda's 53.3 (D), and leads in 5 of 7 scored categories. Both do compute serverless.

- Cloud Run GPUs: B 68.4, rank #288 of 1486 · https://www.anchorterminal.com/tools/cloud-run-gpus.min.md
- Verda: D 53.3, rank #946 of 1486 · https://www.anchorterminal.com/tools/verda.min.md
- Cloud Run GPUs, good for Serving small and mid-size open models, or batch jobs, from a container that should scale to zero. Ahead on Reliability, 70 against 60; Schema & documentation, 81 against 72; Security & auth, 78 against 68; Transparency & trust, 84 against 76. Also No incidents deducted, where Verda loses 9 points for them.
- Verda, good for Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP. Also Runs on your own machine.

| Category | Cloud Run GPUs | Verda |
| --- | --- | --- |
| Reliability (16%) | 70 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 72 |
| Agent ergonomics (13%) | 66 | 63 |
| Security & auth (14%) | 78 | 68 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 83 |
| Transparency & trust (7%) | 84 | 76 |

| Fact (where they differ) | Cloud Run GPUs | Verda |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Verda |
| Hosted endpoint | `https://run.googleapis.com` | `https://api.verda.com/v1` |
| Transports |  | HTTP, stdio |
| Price for compute serverless | not published | $5.33 per GPU-hour |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0 |
| Tools exposed | none | 18 |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-10-28 |
| Terms last updated | 2026-09-02 | 2025-09-30 |
| Privacy policy last updated | 2026-09-28 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 10k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Reliability, Cloud Run GPUs +10: Cloud Run GPUs 70 (Hosted reading. Google Cloud's status page with a JSON incident feed (20). In the 90 days from 8 August 2026 the feed names Cloud Run in three multi-product incidents, a service outage on 20 August (15:40 to 19:20 UTC, 27 products, global and us-west1), a network degradation in us-central1-b on 1 September and a europe-west2 disruption on 20 October. One major (10). Resource limits and GPU quota are published with numbers (3 GPUs a region by default), but no request rate for the Admin API was found on the quotas page (10). Google's client libraries retry with backoff and the Admin API takes etags, while no GPU-specific retry guidance was found (10). An SLA for GPU services, 99.95% with zonal redundancy and 99.5% without (10). GPU services generally available since 7 April 2025 (10). 20+10+10+10+10+10 = 70.); Verda 60 (Graded on the hosted lines for the REST API. BetterStack page at status.verda.com with 21 components, 180-day bars and an RSS feed (20). The feed lists eight incidents from 4 August to 2 November 2026, none posted against the API component and each limited to one product, one location or some customers. Serverless Containers were slow or unavailable for about 9.5 hours on 13 August, the container gateway returned intermittent 500s on 4 September, container uploads failed for about 2 hours on 20 September, a small number of instances, volumes and billing records were affected on 25 September, Serverless Containers degraded during a security update on 9 October, FIN03 services and Google SSO sign-in failed during maintenance on 11 October, the container registry vccr.io was down on 19 October, and FIN-02 lost network connectivity on 23 October. This run reads all of them as partial, minor only (20). api.verda.com, which hosts the API reference with the rate limits, answered robots.txt with 401 on 2 November 2026, so the 8 October readings from its OpenAPI document are struck. The docs' changelog says rate limits apply since 11 March 2026 and points to that reference, with no numbers on a page we can read (0). The official Go SDK's retry middleware backs off on 429 and 5xx, instance actions already in the requested state answer 204 and volume deletion is idempotent per the docs' changelog, and serverless job request IDs answer 409 on a repeat, but instance creation has no idempotency key and Retry-After is documented only on the refused host (10 of 15). No SLA found, and the terms give no warranty of uninterrupted availability (0). The REST API is generally available, while the CLI's MCP server is marked beta (10).)
- Security & auth, Cloud Run GPUs +10: Cloud Run GPUs 78 (OAuth 2.0 tokens from service accounts under IAM. Google's APIs accept `access_token` as a query parameter, the 10-point deduction other Google API listings take (20). IAM roles separate viewing, deploying and invoking, and services can require IAM authentication for every call (16). The platform runs your own container and returns its output (10). Cloud Audit Logs record Admin API calls, and request logs go to Cloud Logging (15). Google's vulnerability reward programme, security.txt and certifications (17). 20+16+10+15+17 = 78.); Verda 68 (OAuth 2.0 client credentials. Access tokens expire after 3,600 seconds, credentials are deleted when their creator leaves the project, and every token carries the single scope `cloud-api-v1`. No secret travels in a URL (20 of 30). Credentials follow their creator's role of owner, admin or developer, and no read-only credential was found. The MCP server and the CLI's `--agent` mode require explicit confirmation for billed and destructive actions, and deleted volumes sit in trash for 96 hours (10 of 20). Responses are infrastructure metadata, apart from container logs (10). Audit log in the console and at `GET /v1/audit/log`, 90 days in CloudEvents format with IP address and origin, marked beta (14 of 15). security.txt is valid until 31 December 2026 and names a disclosure policy at vdp.verda.com. The home page states SOC 2 Type II and ISO 27001, 27017, 27018 and 27701. The trust centre and the policy page are drawn by script and we couldn't read them, and no bug bounty was found (14 of 20).)
- Schema & documentation, Cloud Run GPUs +9: Cloud Run GPUs 81 (API reading. A public Discovery document for the Cloud Run Admin API v2 (25). No llms.txt; Google's docs answer Markdown only at an unlinked `.md.txt` address, read as half, as for the Document AI listing (5). The GPU page says when to turn zonal redundancy on or off and the best-practices page when to bake models into images or load them from Cloud Storage (16). The GPU type is a free string in a node selector, with CPU and memory minimums stated in prose (9). gcloud, YAML, Terraform and console steps on each page, and errors follow Google's status model with no Cloud Run GPU error list (11). Versioned API (v1 and v2) and dated release notes (15). 25+5+16+9+11+15 = 81.); Verda 72 (api.verda.com's robots.txt answered 401 on 2 November 2026, so the OpenAPI document and the API reference there weren't read and the 8 October counts taken from them (112 operations, 156 schemas, 104 enums, 756 examples) are struck. The docs' changelog names the OpenAPI specification and its schemas (oneOf for UUID-or-array fields, the 19 March 2026 auth fix), and the Go and Python SDKs carry typed models, but no per-operation reference is readable on an allowed host (20 of 25). `llms.txt` on verda.com and docs.verda.com, every docs page as Markdown and the corpus in `llms-full.txt` (10). Docs guides and changelog entries describe what endpoints do and their billing effects, for example that `shutdown` keeps charging, while the reference descriptions are unread (10 of 20). Required fields and enums are visible only through the SDKs' typed models and validation, such as the Go SDK's limits added in v1.7.0, and the docs ask clients to treat enums as open (8 of 15). The docs corpus carries 62 curl examples and the Python SDK lists seven error codes, while per-operation error responses sit in the unread reference (9 of 15). Versioned in the path, with a dated changelog of 24 entries in 2026, the newest on 7 October (15).)
- Transparency & trust, Cloud Run GPUs +8: Cloud Run GPUs 84 (Closed service under the Google Cloud terms, with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum and the privacy notice cover customer data, per the Document AI listing's 1 November reading; no Cloud Run statement on GPU instance data after shutdown was found (22). The Cloud terms promise 12 months' notice before a backwards-incompatible API change, and driver versions are announced in the release notes (16). Regions per GPU type listed, with Google's subprocessor list and data-location terms (16). 15+22+16+16 = 69.); Verda 76 (Closed service under Terms of Service dated 30 September 2025 and Finnish law. The CLI and SDKs are Apache-2.0 (15 of 30). The terms include data processing terms, and the privacy policy has a retention table. Deleted customer data is removed within 96 hours per the privacy policy and clause 10.9.2, while Schedule 3 of the same terms says 72 hours. The privacy policy shows no readable date (20 of 30). No deprecation policy with a notice period. HDD volumes were announced as deprecated in April 2026 before creation was blocked on 21 September (10 of 20). The docs name three data centres in Helsinki, the terms promise 15 days' notice of a new sub-processor, and the privacy policy names Front and Stripe. The sub-processor list is drawn by script and we couldn't read it (12 of 20).)