{ "data": { "a": { "slug": "cloud-run-gpus", "name": "Cloud Run GPUs", "vendor": "Google Cloud", "vendorUrl": "https://cloud.google.com/run", "kind": "platform", "category": "gpu-compute", "summary": "Cloud Run GPUs attach one NVIDIA L4 or RTX PRO 6000 Blackwell GPU to a Cloud Run service, job or worker pool, so a container serves models serverlessly, billed per second and able to scale to zero.", "url": "https://www.anchorterminal.com/tools/cloud-run-gpus", "markdownUrl": "https://www.anchorterminal.com/tools/cloud-run-gpus.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cloud-run-gpus.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus.json", "dns": "cloud-run-gpus.grade.anchorterminal.com", "license": "Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0", "transports": [], "remoteUrl": "https://run.googleapis.com", "packages": [ { "registry": "pypi", "name": "google-cloud-run" }, { "registry": "npm", "name": "@google-cloud/run" } ], "auth": "oauth", "authNotes": "Deploys go through the Cloud Run Admin API with OAuth 2.0 bearer tokens from a service account or Application Default Credentials, under IAM roles such as roles/run.developer and roles/run.invoker. A deployed service can require IAM authentication or allow public calls. A project with billing enabled is set up in the console first.", "pricing": "usage", "pricingNotes": "Per second, instance-based billing only. L4 $0.0001867 a second (about $0.67 an hour) without zonal redundancy, $0.0002909 with; RTX PRO 6000 $0.00036522 (about $1.31 an hour) and $0.00056913. CPU and memory extra, with a minimum of 4 vCPU and 16 GiB (L4) or 20 vCPU and 80 GiB (RTX PRO 6000).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Cloud Run pricing, GPU or quotas pages (checked 2026-11-06). Billing runs through a Google Cloud billing account.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.cloud.google.com/run/docs/configuring/services/gpu", "openapi": "https://run.googleapis.com/$discovery/rest?version=v2", "capabilities": [ "compute.serverless", "compute.gpu", "compute.endpoints", "compute.containers", "compute.batch" ], "tags": [ "hosted", "official", "usage", "per-second", "scale-to-zero", "sla", "status-page", "discovery-doc", "l4", "rtx-pro-6000" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 68.4, "grade": "B", "agentReady": false, "rank": 289, "ranked": true, "rankOf": 1510, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 80, "payments": 20, "reliability": 70, "schema": 81, "security": 78, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models.", "bestFor": "Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.", "strengths": [ "Scales to zero, bills per second, and instances with drivers start in about 5 seconds", "SLA of 99.95% with zonal redundancy and 99.5% without, plus Google's status feed", "IAM roles for deploying and invoking, Cloud Audit Logs and services that can require authentication", "Per-second prices public, L4 from about $0.67 a GPU-hour without zonal redundancy", "The same GPU option on services, jobs (up to 12 hours) and worker pools" ], "weaknesses": [ "One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit", "Default quota is 3 GPUs a region; more needs a quota request", "Model load time comes on top of the 5-second start, and minimum instances bill while idle", "No free GPU tier, and the trial credit needs a payment method", "Google's APIs accept OAuth tokens in a URL query parameter" ], "agentNotes": [ "Pass `--gpu 1 --gpu-type nvidia-l4` (or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and `--no-cpu-throttling` for instance-based billing", "Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB", "Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required", "Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate", "Send OAuth tokens in the `Authorization` header, never as `access_token` in the URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 80, "payments": 20, "reliability": 70, "schema": 81, "security": 78, "transparency": 69 }, "provenanceScore": 99, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "headless": { "command": "gcloud run deploy SERVICE --image IMAGE --gpu 1 --gpu-type nvidia-l4 --cpu 4 --memory 16Gi --no-cpu-throttling --region europe-west1" } }, "letme": { "capability": "https://letme.dev/compute.serverless", "tool": "https://letme.dev/cloud-run-gpus" }, "sameCompany": [ "gemini-api", "vertex-ai", "gemini-embedding", "vertex-ai-tuning", "google-model-armor", "google-imagen", "google-veo", "google-lyria", "google-speech-to-text", "google-cloud-tts", "gemini-live", "google-adk", "google-memory-bank", "google-secret-manager", "google-cloud-document-ai", "google-weather-api", "chrome-devtools-mcp", "google-maps-platform", "google-cloud-translation", "google-calendar-api", "firebase-cloud-messaging", "google-cloud-storage", "google-drive-api", "gemini-enterprise", "gemini-cli", "google-search-console", "google-ads-api", "google-forms", "google-sheets-api", "gmail-api", "google-people-api" ], "area": "models", "unitPrices": [ { "item": "NVIDIA L4, no zonal redundancy", "unit": "gpu-hour", "usd": 0.67, "note": "$0.0001867 a second, tier 1 regions; CPU and memory extra" }, { "item": "NVIDIA L4, zonal redundancy", "unit": "gpu-hour", "usd": 1.05, "note": "$0.0002909 a second" }, { "item": "NVIDIA RTX PRO 6000, no zonal redundancy", "unit": "gpu-hour", "usd": 1.31, "note": "$0.00036522 a second" }, { "item": "NVIDIA RTX PRO 6000, zonal redundancy", "unit": "gpu-hour", "usd": 2.05, "note": "$0.00056913 a second" } ], "provenance": { "legalEntity": "Google LLC", "domain": "google.com", "domainRegistered": "1997-09-15", "domainNote": "The endpoints are on googleapis.com, Google's API domain. Docs are on docs.cloud.google.com.", "endpointOnVendorDomain": true, "terms": "https://cloud.google.com/terms", "privacy": "https://cloud.google.com/terms/cloud-privacy-notice", "statusPage": "https://status.cloud.google.com", "changelog": "https://docs.cloud.google.com/run/docs/release-notes", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Legal entity, terms, privacy notice and security.txt as on the Google Cloud Document AI listing, checked 1 November 2026, and not re-read for this listing.", "docs.cloud.google.com/robots.txt and cloud.google.com/robots.txt allow the Cloud Run pages read; status.cloud.google.com/robots.txt allows everything.", "The Cloud Run SLA lists GPU services separately, 99.95% with zonal redundancy and 99.5% without (https://cloud.google.com/run/sla)." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cloud-run-gpus.json", "live": { "slug": "cloud-run-gpus", "probe": { "target": "https://run.googleapis.com", "method": "get", "lastAt": "2026-11-07T22:55:51.650380142Z", "lastOk": true, "lastStatus": 404, "lastMs": 68, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 37, "p95ms24h": 158, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.cloud.google.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:16.629467571Z" }, "versions": [ { "registry": "npm", "name": "@google-cloud/run", "version": "4.2.0", "seenAt": "2026-11-06T23:15:29.275446701Z" }, { "registry": "pypi", "name": "google-cloud-run", "version": "0.16.2", "released": "2026-10-01", "seenAt": "2026-11-06T23:15:27.277547645Z" } ], "npmWeekly": 1706675, "pypiWeekly": 3039289, "securityTxt": { "url": "https://google.com/.well-known/security.txt", "state": "valid", "expires": "2030-04-01T00:00:00z", "checkedAt": "2026-11-07T16:01:22.068349931Z" }, "pages": [ { "url": "https://docs.cloud.google.com/run/docs/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:05:47.69894113Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "924ee0205e11" }, { "url": "https://cloud.google.com/terms/cloud-privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:01:29.495526727Z", "changedAt": "2026-11-03T07:43:24.319773868Z", "fingerprint": "b62369d64ac6" }, { "url": "https://cloud.google.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:01:27.593286996Z", "changedAt": "2026-11-03T07:43:22.480965239Z", "fingerprint": "b9ec671a2caf" } ], "updatedAt": "2026-11-07T22:55:51.650380142Z" } }, "answer": "Cloud Run GPUs scores 68.4 (B) on agent readiness against Verda's 53.3 (D), and leads in 5 of 7 scored categories.", "b": { "slug": "verda", "name": "Verda", "vendor": "Verda", "vendorUrl": "https://verda.com", "kind": "http-api", "category": "gpu-compute", "summary": "Verda, formerly DataCrunch, is a Finnish GPU cloud renting GPU and CPU instances, clusters, serverless containers and storage. Agents use its REST API, Python and Go SDKs, or a CLI with a built-in MCP server in beta.", "url": "https://www.anchorterminal.com/tools/verda", "markdownUrl": "https://www.anchorterminal.com/tools/verda.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/verda.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/verda.json", "dns": "verda.grade.anchorterminal.com", "repo": "https://github.com/verda-cloud/verda-cli", "license": "Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.verda.com/v1", "packages": [ { "registry": "pypi", "name": "verda" }, { "registry": "go", "name": "github.com/verda-cloud/verdacloud-sdk-go" } ], "auth": "oauth", "authNotes": "Self-serve. A signed-in user creates a Client ID and Client Secret on the console's Credentials page, and the secret is shown once. `POST /v1/oauth2/token` with the client credentials grant returns an access token valid for 3,600 seconds and a refresh token, both with the scope `cloud-api-v1`. Credentials belong to the member who created them and are deleted when that member leaves the project. The CLI and its MCP server read the same pair from `~/.verda/credentials` after `verda auth login`. A few catalogue endpoints such as `GET /v1/instance-types` need no token.", "pricing": "usage", "pricingNotes": "No free tier or trial. Accounts are prepaid by card or bank transfer, and Pay As You Go is charged in prepaid 10-minute increments with the unused part refunded. On-demand prices per GPU an hour on 2 November 2026 include H100 80 GB at $4.841, H200 at $6.313, B200 at $8.958, B300 at $11.46 and A100 80 GB at $2.27, with spot at half, up about 19 to 25 per cent in dollars from 8 October with no notice found. Dollar prices follow the euro list price (H100 €4.333) and move with the exchange rate, so part of the rise may be currency. Reserved terms take 2 to 25 per cent off, per the 8 October check. Serverless containers bill per minute of replica use. Free credits are granted only for approved blog posts or videos (https://verda.com/pricing).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 10461, "asOf": "2026-10-08" }, "docsUrl": "https://docs.verda.com", "llmsTxt": "https://docs.verda.com/llms.txt", "openapi": "https://api.verda.com/v1/openapi.json", "capabilities": [ "compute.gpu", "compute.serverless", "compute.endpoints", "compute.batch", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "oauth", "python", "go", "terraform", "status-page", "soc2", "europe" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 53.3, "grade": "D", "agentReady": false, "rank": 952, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 83, "payments": 20, "reliability": 60, "schema": 72, "security": 68, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -9, "negativeNotes": [ "2026-03-23, making `location_code` required on `POST /v1/instances`, `POST /v1/clusters` and `POST /v1/volumes`. Requests that had defaulted to FIN-01 began returning 400. The API changelog heads the change 23 March 2026 and records no advance notice. Documented, so 3 points (https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md).", "Released fixes with no advisory, -3. Python SDK `verda` 1.24.1 (12 August 2026) lists under Security a fixed path traversal in which a resource name containing `../` retargeted a call at another endpoint under the SDK's credentials (`containers.delete_deployment('../../v1/instances')` issued `DELETE /v1/instances`), and the API changelog of 20 March 2026 says API tokens \"could access internal endpoints not intended for external use\" before scopes were added. OSV holds no advisory for PyPI `verda` or the Go SDK on 2 November 2026. One folded term (https://github.com/verda-cloud/sdk-python/blob/master/CHANGELOG.md, https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md).", "Unreleased fix, -3. Commit 42f054d in verda-cloud/sdk-python (29 October 2026, \"security: check the inference request path\") says a path built from untrusted input could add query parameters or a fragment to a request that carries the inference key, and that `..;/` and `..%252f` passed the old check. It sits under `[Unreleased]` in the changelog, after 1.25.0 of 23 October (https://github.com/verda-cloud/sdk-python/commit/42f054d)." ], "verdict": "Verda documents its API changes in a dated changelog, publishes hourly GPU prices, and its CLI's MCP server refuses billed or destructive calls without `confirm: true`. Access needs a browser signup and a prepaid balance, credentials carry one scope, instance creation has no idempotency key, and two SDK security fixes in 2026 came without an advisory or release.", "bestFor": "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.", "strengths": [ "`llms.txt` files on two hosts and the whole docs corpus as Markdown, with a dated API changelog of 24 entries in 2026", "Official Python and Go SDKs, a Terraform provider and a CLI, each released between 22 and 28 October 2026", "Hourly prices for every GPU type published in USD and EUR without a login, with spot at half the on-demand rate", "Audit log endpoint in CloudEvents 1.0 format covering 90 days, with the caller's IP address and origin on resource events", "The 18-tool MCP server refuses `create_vm`, `create_volume` and destructive `vm_action` calls unless `confirm: true` is passed" ], "weaknesses": [ "No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero", "Cloud API credentials carry one scope, `cloud-api-v1`, with no read-only credential found in the reviewed documentation", "`POST /v1/instances` has no idempotency key, so a retried launch can start a second billed instance", "The MCP server is marked beta and its tools carry no read-only or destructive annotations", "No SLA was found, and the terms give no warranty of uninterrupted availability", "The Python SDK fixed a path traversal in 1.24.1 and an inference-path flaw on 29 October 2026 with no advisory, the second in no release yet" ], "agentNotes": [ "Exchange the client ID and secret at `POST /v1/oauth2/token`, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.", "Send `location_code` on every create call. Requests without it have returned 400 since March 2026.", "Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.", "List instances before retrying a failed launch, because create has no idempotency key.", "Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.3 } ], "editorialScores": { "ergonomics": 63, "maintenance": 83, "payments": 20, "reliability": 60, "schema": 72, "security": 68, "transparency": 57 }, "provenanceScore": 95, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "brew install verda-cloud/tap/verda-cli", "http": "curl -X POST https://api.verda.com/v1/oauth2/token -H \"Content-Type: application/json\" -d '{\"grant_type\":\"client_credentials\",\"client_id\":\"\u003cYOUR_CLIENT_ID\u003e\",\"client_secret\":\"\u003cYOUR_CLIENT_SECRET\u003e\"}'", "config": { "mcpServers": { "verda": { "args": [ "mcp", "serve" ], "command": "verda" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/verda" }, "area": "models", "unitPrices": [ { "item": "H100 SXM5 80 GB, on-demand", "unit": "gpu-hour", "usd": 4.841, "note": "Spot $2.421. Billed in prepaid 10-minute increments" }, { "item": "H200 SXM5 141 GB, on-demand", "unit": "gpu-hour", "usd": 6.313, "note": "Spot $3.157" }, { "item": "B200 SXM6 180 GB, on-demand", "unit": "gpu-hour", "usd": 8.958, "note": "Spot $4.479" }, { "item": "B300 SXM6 268 GB, on-demand", "unit": "gpu-hour", "usd": 11.46, "note": "Spot $5.73" }, { "item": "A100 SXM4 80 GB, on-demand", "unit": "gpu-hour", "usd": 2.27, "note": "Spot $1.135" }, { "item": "L40S 48 GB, on-demand", "unit": "gpu-hour", "usd": 1.92, "note": "Spot $0.96" }, { "item": "H100 SXM5 80 GB, serverless container", "unit": "gpu-hour", "usd": 5.33, "note": "Spot $2.66. Billed per minute of replica use" }, { "item": "NVMe block volume or shared filesystem", "unit": "gb-month", "usd": 0.2, "note": "Per GiB" } ], "provenance": { "legalEntity": "DataCrunch Oy", "domain": "verda.com", "domainRegistered": "1998-05-22", "endpointOnVendorDomain": true, "terms": "https://verda.com/terms-and-conditions", "privacy": "https://verda.com/privacy-policy", "statusPage": "https://status.verda.com", "changelog": "https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Terms of Service, last updated 30 September 2025, name the supplier as Verda (DataCrunch Oy), apply Finnish law and set arbitration in Helsinki. They include the data processing terms.", "The CLI source carries the copyright of Verda Cloud Oy.", "The API answers at api.verda.com, a subdomain of the vendor domain.", "security.txt expires on 31 December 2026, lists security@verda.com and a policy at https://vdp.verda.com.", "RDAP for verda.com gives a registration date of 1998-05-22. The company took the Verda name later, and verda.com/llms.txt says it was previously known as DataCrunch.", "The privacy policy covers the website and the services and shows no readable date." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/verda.json", "live": { "slug": "verda", "probe": { "target": "https://api.verda.com/v1", "method": "get", "lastAt": "2026-11-07T22:56:29.544638928Z", "lastOk": true, "lastStatus": 401, "lastMs": 152, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.93, "p50ms24h": 102, "p95ms24h": 189, "samples24h": 244, "samples30d": 7335, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 254 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 249 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 247 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.verda.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:56.698835616Z" }, "versions": [ { "registry": "github", "name": "verda-cloud/verda-cli", "version": "v1.10.0", "released": "2026-11-06", "seenAt": "2026-11-07T00:15:17.154297899Z" }, { "registry": "pypi", "name": "verda", "version": "1.25.0", "released": "2026-10-23", "seenAt": "2026-11-07T00:15:16.973607792Z" } ], "githubStars": 16, "pypiWeekly": 9525, "securityTxt": { "url": "https://verda.com/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T11:59:00Z", "checkedAt": "2026-11-07T16:00:49.972736209Z" }, "llmsTxt": { "url": "https://docs.verda.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:16.894348703Z" }, "domain": { "domain": "verda.com", "registered": "1998-05-22", "source": "https://rdap.verisign.com/com/v1/domain/verda.com", "checkedAt": "2026-11-01T14:13:48.625189825Z" }, "pages": [ { "url": "https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:08:35.488323411Z", "changedAt": "2026-11-05T12:32:20.917395122Z", "fingerprint": "edd04ebbd363" }, { "url": "https://verda.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:23:19.050824521Z", "changedAt": "2026-11-07T14:23:19.050824521Z", "fingerprint": "1777e38584d3" }, { "url": "https://verda.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:23:21.35557714Z", "changedAt": "2026-11-07T14:23:21.35557714Z", "fingerprint": "bcf01daa54c0" }, { "url": "https://verda.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:23:23.638199688Z", "changedAt": "2026-11-07T14:23:23.638199688Z", "fingerprint": "95ec6c6c21ba" } ], "github": { "repo": "verda-cloud/verda-cli", "checkedAt": "2026-11-02T09:35:54.540508327Z", "stars": 16, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-28T16:20:14Z", "openIssues": 1, "openPRs": 0, "issuesOpened90d": 1, "issuesClosed90d": 1, "prsMerged90d": 9, "ci": { "branch": "main", "runs": 50, "success": 48, "failure": 2, "other": 0, "latest": "success", "latestAt": "2026-10-28T16:20:17Z" }, "replies": { "sampled": 4, "unanswered": 1, "medianDays": 2.2 } }, "updatedAt": "2026-11-07T22:56:29.544638928Z" } }, "edges": [ { "by": 10, "category": "reliability", "leads": "cloud-run-gpus", "name": "Reliability", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 70, "b": 60 } }, { "by": 10, "category": "security", "leads": "cloud-run-gpus", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 78, "b": 68 } }, { "by": 9, "category": "schema", "leads": "cloud-run-gpus", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 81, "b": 72 } }, { "by": 8, "category": "transparency", "leads": "cloud-run-gpus", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 84, "b": 76 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Google Cloud", "b": "Verda", "name": "Vendor" }, { "a": "https://run.googleapis.com", "b": "https://api.verda.com/v1", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$5.33 per GPU-hour", "name": "Price for compute serverless" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0", "b": "Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0", "name": "Licence" }, { "a": "none", "b": "18", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-10-28", "name": "Last release" }, { "a": "2026-09-02", "b": "2025-09-30", "name": "Terms last updated" }, { "a": "2026-09-28", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "10k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Cloud Run GPUs scores 68.4 (B) on agent readiness against Verda's 53.3 (D), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Cloud Run GPUs or Verda?" }, { "answer": "Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Verda at https://api.verda.com/v1.", "question": "Can an agent call Cloud Run GPUs and Verda without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 60", "Schema \u0026 documentation, 81 against 72", "Security \u0026 auth, 78 against 68", "Transparency \u0026 trust, 84 against 76" ], "also": [ "No incidents deducted, where Verda loses 9 points for them" ], "goodFor": "Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.", "slug": "cloud-run-gpus", "watchFor": "One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit" }, { "aheadOn": null, "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "verda", "watchFor": "No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero" } ], "history": { "cloud-run-gpus": null, "verda": [ { "causes": [ "security", "evidence" ], "date": "2026-11-02", "delta": -9, "from": 62.3, "fromGrade": "B", "to": 53.3, "toGrade": "D" } ] }, "job": { "capability": "compute.serverless", "name": "Compute serverless" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.json", "title": "Baseten vs Cloud Run GPUs", "url": "https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus" }, { "json": "https://www.anchorterminal.com/compare/baseten-vs-verda.json", "title": "Baseten vs Verda", "url": "https://www.anchorterminal.com/compare/baseten-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.json", "title": "Beam vs Cloud Run GPUs", "url": "https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-verda.json", "title": "Beam vs Verda", "url": "https://www.anchorterminal.com/compare/beam-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.json", "title": "Cerebrium vs Cloud Run GPUs", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-verda.json", "title": "Cerebrium vs Verda", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.json", "title": "Cloud Run GPUs vs CoreWeave", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.json", "title": "Cloud Run GPUs vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.json", "title": "Cloud Run GPUs vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints.json", "title": "Cloud Run GPUs vs Hugging Face Inference Endpoints", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.json", "title": "Cloud Run GPUs vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.json", "title": "Cloud Run GPUs vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.json", "title": "Cloud Run GPUs vs Massed Compute", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.json", "title": "Cloud Run GPUs vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.json", "title": "Cloud Run GPUs vs Northflank", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.json", "title": "Cloud Run GPUs vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.json", "title": "Cloud Run GPUs vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-verda.json", "title": "CoreWeave vs Verda", "url": "https://www.anchorterminal.com/compare/coreweave-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.json", "title": "Crusoe Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda.json", "title": "GPUsMarket vs Verda", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.json", "title": "Hugging Face Inference Endpoints vs Verda", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda.json", "title": "Hyperbolic vs Verda", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-verda.json", "title": "Koyeb vs Verda", "url": "https://www.anchorterminal.com/compare/koyeb-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-verda.json", "title": "Lambda Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/lambda-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.json", "title": "Massed Compute vs Verda", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-verda.json", "title": "Modal vs Verda", "url": "https://www.anchorterminal.com/compare/modal-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.json", "title": "Nebius AI Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-verda.json", "title": "Northflank vs Verda", "url": "https://www.anchorterminal.com/compare/northflank-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.json", "title": "Replicate Deployments vs Verda", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-verda.json", "title": "Runpod vs Verda", "url": "https://www.anchorterminal.com/compare/runpod-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.json", "title": "Thunder Compute vs Verda", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.json", "title": "Together GPU Clusters vs Verda", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/vast-ai-vs-verda.json", "title": "Vast.ai vs Verda", "url": "https://www.anchorterminal.com/compare/vast-ai-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.json", "title": "Cloud Run GPUs vs Koyeb", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal.json", "title": "Cloud Run GPUs vs Modal", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy.json", "title": "Cloud Run GPUs vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.json", "title": "Cloud Run GPUs vs Runpod", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai.json", "title": "Cloud Run GPUs vs Vast.ai", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai" } ], "panel": null, "scores": [ { "by": 10, "cloud-run-gpus": 70, "edge": "cloud-run-gpus", "key": "reliability", "name": "Reliability", "verda": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "cloud-run-gpus": 81, "edge": "cloud-run-gpus", "key": "schema", "name": "Schema \u0026 documentation", "verda": 72, "weight": 13 }, { "by": 3, "cloud-run-gpus": 66, "edge": "cloud-run-gpus", "key": "ergonomics", "name": "Agent ergonomics", "verda": 63, "weight": 13 }, { "by": 10, "cloud-run-gpus": 78, "edge": "cloud-run-gpus", "key": "security", "name": "Security \u0026 auth", "verda": 68, "weight": 14 }, { "by": 0, "cloud-run-gpus": 20, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "verda": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "cloud-run-gpus": 80, "edge": "verda", "key": "maintenance", "name": "Maintenance \u0026 community", "verda": 83, "weight": 7 }, { "by": 8, "cloud-run-gpus": 84, "edge": "cloud-run-gpus", "key": "transparency", "name": "Transparency \u0026 trust", "verda": 76, "weight": 7 } ], "summary": "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.", "tasks": null, "tutorials": [], "verdicts": { "cloud-run-gpus": "Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models.", "verda": "Verda documents its API changes in a dated changelog, publishes hourly GPU prices, and its CLI's MCP server refuses billed or destructive calls without `confirm: true`. Access needs a browser signup and a prepaid balance, credentials carry one scope, instance creation has no idempotency key, and two SDK security fixes in 2026 came without an advisory or release." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda", "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.min.md" }, "markdown": "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.\n\n- Cloud Run GPUs: grade B, 68.4/100, rank #289 of 1510. Markdown https://www.anchorterminal.com/tools/cloud-run-gpus.md · JSON https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus.json\n- Verda: grade D, 53.3/100, rank #952 of 1510. Markdown https://www.anchorterminal.com/tools/verda.md · JSON https://www.anchorterminal.com/api/v1/tools/verda.json\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### Cloud Run GPUs (B)\n\nGood for: Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.\n\nAhead on:\n- Reliability, 70 against 60\n- Schema \u0026 documentation, 81 against 72\n- Security \u0026 auth, 78 against 68\n- Transparency \u0026 trust, 84 against 76\n\nAlso in its favour:\n- No incidents deducted, where Verda loses 9 points for them\n\nWatch for: One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit\n\n### Verda (D)\n\nGood 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.\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero\n\n\n## Why the edge\n\n### Reliability: Cloud Run GPUs +10\n\n- 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.\n- 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).\n\n### Security \u0026 auth: Cloud Run GPUs +10\n\n- 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.\n- 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).\n\n### Schema \u0026 documentation: Cloud Run GPUs +9\n\n- 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.\n- 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).\n\n### Transparency \u0026 trust: Cloud Run GPUs +8\n\n- 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.\n- 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).\n\n## Score by category\n\n| Category | Weight | Cloud Run GPUs | Verda | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 60 | Cloud Run GPUs +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 72 | Cloud Run GPUs +9 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 63 | Cloud Run GPUs +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 78 | 68 | Cloud Run GPUs +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 83 | Verda +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 84 | 76 | Cloud Run GPUs +8 |\n| Negative events | ≤15 | 0 | -9 | |\n| **Total** | | **68.4 · B** | **53.3 · D** | |\n\n## Facts side by side\n\n| Fact | Cloud Run GPUs | Verda |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Google Cloud | Verda |\n| Hosted endpoint | `https://run.googleapis.com` | `https://api.verda.com/v1` |\n| Transports | | HTTP, stdio |\n| Auth | OAuth | OAuth |\n| Pricing | Pay per use | Pay per use |\n| Price for compute serverless | not published | $5.33 per GPU-hour |\n| x402 | no | no |\n| 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 |\n| Tools exposed | none | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-30 | 2026-10-28 |\n| Terms last updated | 2026-09-02 | 2025-09-30 |\n| Privacy policy last updated | 2026-09-28 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | none | 10k PyPI/wk |\n| Agent reviews | none | 3.3/5 (4) |\n\n## How the scores have moved\n\n### Cloud Run GPUs\n\nNo score change since it was listed.\n\n### Verda\n\n- -9.0 on 2 November 2026 (B to D): security, new evidence\n\n## Verdicts\n\n**Cloud Run GPUs.** Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models.\n\n**Verda.** Verda documents its API changes in a dated changelog, publishes hourly GPU prices, and its CLI's MCP server refuses billed or destructive calls without `confirm: true`. Access needs a browser signup and a prepaid balance, credentials carry one scope, instance creation has no idempotency key, and two SDK security fixes in 2026 came without an advisory or release.\n\n## Before you call either\n\n### Cloud Run GPUs\n\n1. Pass `--gpu 1 --gpu-type nvidia-l4` (or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and `--no-cpu-throttling` for instance-based billing\n2. Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB\n3. Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required\n4. Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate\n5. Send OAuth tokens in the `Authorization` header, never as `access_token` in the URL\n\n### Verda\n\n1. Exchange the client ID and secret at `POST /v1/oauth2/token`, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.\n2. Send `location_code` on every create call. Requests without it have returned 400 since March 2026.\n3. Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.\n4. List instances before retrying a failed launch, because create has no idempotency key.\n5. Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set.\n\n## Questions\n\n### Which is better for AI agents, Cloud Run GPUs or Verda?\n\nCloud Run GPUs scores 68.4 (B) on agent readiness against Verda's 53.3 (D), and leads in 5 of 7 scored categories.\n\n### Can an agent call Cloud Run GPUs and Verda without installing anything?\n\nYes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Verda at https://api.verda.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cloud-run-gpus\", \"b\": \"verda\"}`. From a terminal: `anchor compare cloud-run-gpus verda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus.json and https://www.anchorterminal.com/api/v1/tools/verda.json\n\n## Other comparisons with Cloud Run GPUs or Verda\n\n- [Baseten vs Cloud Run GPUs](https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.md)\n- [Baseten vs Verda](https://www.anchorterminal.com/compare/baseten-vs-verda.md)\n- [Beam vs Cloud Run GPUs](https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.md)\n- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md)\n- [Cerebrium vs Cloud Run GPUs](https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.md)\n- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md)\n- [Cloud Run GPUs vs CoreWeave](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.md)\n- [Cloud Run GPUs vs Crusoe Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.md)\n- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)\n- [Cloud Run GPUs vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints.md)\n- [Cloud Run GPUs vs Hyperbolic](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.md)\n- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md)\n- [Cloud Run GPUs vs Massed Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md)\n- [Cloud Run GPUs vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.md)\n- [Cloud Run GPUs vs Northflank](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.md)\n- [Cloud Run GPUs vs Thunder Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.md)\n- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)\n- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md)\n- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.md)\n- [GPUsMarket vs Verda](https://www.anchorterminal.com/compare/gpusmarket-vs-verda.md)\n- [Hugging Face Inference Endpoints vs Verda](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.md)\n- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md)\n- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md)\n- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)\n- [Massed Compute vs Verda](https://www.anchorterminal.com/compare/massed-compute-vs-verda.md)\n- [Modal vs Verda](https://www.anchorterminal.com/compare/modal-vs-verda.md)\n- [Nebius AI Cloud vs Verda](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.md)\n- [Northflank vs Verda](https://www.anchorterminal.com/compare/northflank-vs-verda.md)\n- [Replicate Deployments vs Verda](https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.md)\n- [Runpod vs Verda](https://www.anchorterminal.com/compare/runpod-vs-verda.md)\n- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.md)\n- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)\n- [Vast.ai vs Verda](https://www.anchorterminal.com/compare/vast-ai-vs-verda.md)\n- [Cloud Run GPUs vs Koyeb](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.md)\n- [Cloud Run GPUs vs Modal](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal.md)\n- [Cloud Run GPUs vs Replicate Deployments](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy.md)\n- [Cloud Run GPUs vs Runpod](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.md)\n- [Cloud Run GPUs vs Vast.ai](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Cloud Run GPUs vs Verda", "url": "" } ], "description": "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.", "facts": [ "Cloud Run GPUs B 68.4", "Verda D 53.3", "scores" ], "h1": "Cloud Run GPUs vs Verda", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cloud-run-gpus-vs-verda", "published": "2026-10-01", "section": "tools", "title": "Cloud Run GPUs vs Verda for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda" }, "tokens": { "markdown": 4750, "slim": 2580 }, "version": 1 }