# Verda

> 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.

- Canonical: https://www.anchorterminal.com/tools/verda
- Markdown: https://www.anchorterminal.com/tools/verda.md (~7,600 tokens)
- Slim: https://www.anchorterminal.com/tools/verda.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/verda.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

## Overview

**Grade B · 62.3/100 · rank #396 of 842 · #7 in GPU & serverless compute · not agent-ready · confidence medium**


## Assessment

The REST API has a public OpenAPI 3.1 document, a dated changelog, published rate limits with `Retry-After`, and an audit log endpoint. The 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, and instance creation has no idempotency key.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Verda (https://verda.com) |
| Kind | HTTP API |
| Category | GPU & serverless compute (https://www.anchorterminal.com/categories/gpu-compute) |
| Transport | HTTP, stdio |
| Endpoint | `https://api.verda.com/v1` |
| Auth | OAuth · 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 | Pay per use (Pay per use) · 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 8 October 2026 include H100 80 GB at $3.89, H200 at $5.07, B200 at $7.34 and A100 80 GB at $1.87, with spot at about half. Reserved terms take 2 to 25 per cent off. Serverless containers bill per minute of replica use. Free credits are granted only for approved blog posts or videos (https://verda.com/pricing). |
| x402 | No · No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-08). |
| Licence | 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 | 18 |
| Packages | pypi: `verda`; go: `github.com/verda-cloud/verdacloud-sdk-go` |
| Source | https://github.com/verda-cloud/verda-cli |
| Docs | https://docs.verda.com |
| llms.txt | https://docs.verda.com/llms.txt |
| Last release | 2026-10-07 |
| PyPI downloads / week | 10,461 |
| Surface graded | The REST API at https://api.verda.com/v1 (OpenAPI 3.1, 112 operations, 10 of them deprecated aliases). The CLI's MCP server is noted alongside and is in beta |
| MCP server | Local, stdio, started with `verda mcp serve`. 18 tools. `list_locations`, `list_instance_types`, `check_availability`, `list_images`, `list_vms`, `describe_vm`, `create_vm`, `vm_availability`, `vm_action`, `estimate_cost`, `get_balance`, `get_running_costs`, `add_ssh_key`, `list_ssh_keys`, `get_ssh_command`, `create_volume`, `list_volumes`, `list_volumes_in_trash` |
| Free tier | None. Prepaid balance, with credits only for approved content |
| GPUs | GB300, B300, B200, H200, H100, A100 40 and 80 GB, RTX PRO 6000, L40S, RTX 6000 Ada, RTX A6000 and Tesla V100, in 1, 2, 4 or 8 GPU shapes per the pricing page |
| Scale to zero | Serverless containers scale to zero with `min_replica_count` 0. Instances bill until deleted, and `shutdown` keeps charging |
| Cold start | No figure published. The docs say the first request after idle waits for a cold start |
| Billing basis | Instances in prepaid 10-minute increments with unused time refunded. Serverless containers per minute of replica use. Storage per GiB a month |
| Rate limits | 500 requests a minute per project and 60 a minute per project, method and path, with `RateLimit-Policy`, `RateLimit` and `Retry-After` headers |
| Errors | `code` and `message`. Codes are `invalid_request`, `unauthorized_request`, `insufficient_funds`, `forbidden_action`, `not_found`, `rate_limit_exceeded`, `server_error` and `service_unavailable` |
| Regions | FIN-01, FIN-02 and FIN-03, all in Helsinki, Finland, per the docs |
| SDKs | Python `verda` 1.24.1 (12 August 2026), Go `verdacloud-sdk-go`, Terraform and OpenTofu provider, CLI v1.8.2 (18 August 2026), all Apache-2.0 |
| Audit | `GET /v1/audit/log` and a JSON export, 90 days, CloudEvents 1.0, owners and admins only, beta |
| Roles | Owner, Admin and Developer per project. Credentials act with their creator's role |
| Status | status.verda.com on BetterStack, 21 components with 180-day history and RSS, JSON and webhook subscriptions |
| 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 |
| JSON | https://www.anchorterminal.com/api/v1/tools/verda.json |

## Score breakdown (methodology v0.4, October 2026 research run)

Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 67 | 13.4 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 82 | 13.3 |
| Agent ergonomics | 13% | 16.2 | 63 | 10.2 |
| Security & auth | 14% | 17.5 | 68 | 11.9 |
| Payments & pricing | 10% | 12.5 | 20 | 2.5 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 83 | 7.3 |
| Transparency & trust (editorial 57, provenance 95) | 7% | 8.8 | 76 | 6.7 |
| Negative events | up to −15 | up to −15 | 2026-03-19, 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 dates the change 19 March and the docs 23 March, and neither records advance notice. Documented, so 3 points (https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md).  | -3 |
| **Total** | | | | **62.3 → B** |

### Why each score

- Reliability 67: 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). Four incidents between 10 July and 8 October 2026, none posted against the API component. Serverless Containers were slow or unavailable for about 9.5 hours on 13 August, the container gateway returned intermittent 500s for about 50 minutes on 4 September, container uploads failed for about 2 hours on 20 September, and some instances, volumes and billing records were affected for about 3 hours on 25 September (10). Rate limits published, 500 requests a minute per project and 60 per endpoint (15). A 429 carries `Retry-After` and `RateLimit` headers, instance actions and volume deletion are idempotent, but instance creation has no idempotency key (12 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).
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 82: Public OpenAPI 3.1 document at api.verda.com/v1/openapi.json with 112 operations and 156 schemas (25). `llms.txt` on verda.com, docs.verda.com and api.verda.com, every docs page as Markdown and the corpus in `llms-full.txt` (10). Only 27 of 112 operations have a description. Those that do state billing effects, for example that `shutdown` keeps charging (10 of 20). Required fields, 104 enums and UUID formats, but several fields accept a string or an array, and the docs ask clients to treat enums as open (11 of 15). 756 examples and an error table of eight codes. 60 of 112 operations document an error response and none lists 429 (11 of 15). Versioned in the path, with a dated changelog of 24 entries in 2026 (15).
- Agent ergonomics 63: No field selection, and instance and volume lists return whole arrays (12 of 25). `page` and `pageSize` with totals in `X-Total-Count` on scripts and journals, a cursor on the audit log, and status, tag and location filters on other lists, but no pagination on instances or volumes (12 of 20). Errors carry a stable `code` and a `message`, and bulk actions return per-item results with 207 (16). Actions that are already in the requested state return 204 and volume deletion is idempotent, but create calls have no idempotency key. The MCP tools require `confirm: true` for billed and destructive calls and carry no read-only or destructive annotations (10 of 20). Official SDKs for Python and Go, a Terraform provider and a CLI. A launch needs an instance type, image, hostname, SSH key and location (13 of 15).
- Security & auth 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).
- Payments & pricing 20: No x402, MPP or L402 in the docs, the OpenAPI document or the pricing page (0). Hourly prices for every instance type are public at verda.com/pricing and from `GET /v1/instance-types` without a token (20). No free tier or trial. Accounts are prepaid, and credits are granted only for approved blog posts or videos (0). Signup and credential creation happen in the browser console (0).
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 83: The newest API changelog entry is dated 7 October 2026 (30). 11 dated API entries since 11 September 2026 (20). A public changelog, monthly release notes, email and chat support and a forum. GitHub issues were not read (10 of 15). Current official clients. `verda` 1.24.1 on PyPI from 12 August 2026, CLI v1.8.2 from 18 August 2026, a Go SDK and a Terraform provider (15). The CLI repository runs lint, test and security workflows, and v1.8.2 raised a vulnerable Go version (8 of 10).
- Transparency & trust 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. Deprecated endpoints are flagged in the spec, and 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).

Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/verda.md (JSON https://www.anchorterminal.com/fixes/verda.json)

### What we couldn't check

- The lead was right about the rename and the 18 MCP tools. verda.com/llms.txt says Verda was previously known as DataCrunch, and the terms still name the supplier as Verda (DataCrunch Oy).
- unchecked: trust.verda.com and trust.verda.com/subprocessors are drawn by script (Vanta), so the certificates and the sub-processor list were not read. The SOC 2 Type II and ISO claims come from the home page.
- unchecked: vdp.verda.com is drawn by script, so the scope and safe-harbour wording of the disclosure policy were not read.
- unchecked: GitHub stars and open issues. The GitHub API answered with a rate limit for our address.
- The privacy policy shows a Last updated label with no date we could read.
- The API changelog mentions `GET /v1/inference/models`, which is not in the OpenAPI document. The docs source hides the inference section.
- The CLI source carries the copyright of Verda Cloud Oy, while the terms name DataCrunch Oy. We recorded the entity the terms name.
- The 30 December 2025 data loss on a shared filesystem is recorded as a weakness. It is not one of the deduction types in the brief, so no points were taken.
- Whether customers were warned by email before `location_code` became required is unknown.

### Sources

- MCP server docs: <https://docs.verda.com/cli/mcp/index.md> (seen 2026-10-08)
- docs index for agents: <https://docs.verda.com/llms.txt> (seen 2026-10-08)
- whole docs corpus (billing, roles, credentials, quotas, audit logs, release notes, credits): <https://docs.verda.com/llms-full.txt> (seen 2026-10-08)
- site llms.txt, stating the DataCrunch rename: <https://verda.com/llms.txt> (seen 2026-10-08)
- OpenAPI document with rate limits, errors and changelog: <https://api.verda.com/v1/openapi.json> (seen 2026-10-08)
- API changes: <https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md> (seen 2026-10-08)
- pricing: <https://verda.com/pricing> (seen 2026-10-08)
- public instance types and prices: <https://api.verda.com/v1/instance-types> (seen 2026-10-08)
- status page: <https://status.verda.com/> (seen 2026-10-08)
- status feed: <https://status.verda.com/feed.rss> (seen 2026-10-08)
- Terms of Service with data processing terms: <https://verda.com/terms-and-conditions> (seen 2026-10-08)
- privacy policy: <https://verda.com/privacy-policy> (seen 2026-10-08)
- security.txt: <https://verda.com/.well-known/security.txt> (seen 2026-10-08)
- home page, certification claims: <https://verda.com/> (seen 2026-10-08)
- CLI repository, MCP tool definitions and changelog: <https://github.com/verda-cloud/verda-cli> (seen 2026-10-08)
- Python SDK repository: <https://github.com/verda-cloud/sdk-python> (seen 2026-10-08)
- PyPI package: <https://pypi.org/pypi/verda/json> (seen 2026-10-08)
- RDAP for verda.com: <https://rdap.verisign.com/com/v1/domain/verda.com> (seen 2026-10-08)

## Who's behind it (provenance 95/100, checked 2026-10-08)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | DataCrunch Oy | 20/20 |
| Domain age | verda.com, registered 1998-05-22 (28 years) | 15/15 |
| Endpoint on the vendor's domain | api.verda.com | 15/15 |
| Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 |
| Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 |
| Status page | status.verda.com | 10/10 |
| Changelog | published | 10/10 |
| security.txt | valid | 10/10 |

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.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://verda.com/terms-and-conditions), read 2026-10-08, dated 2025-09-30, states 5 of the 7 things a reader expects.

- To know. Restricts benchmarking or competitive use (costs points). "6.1.5. access, develop, supply or market all or any part of the Service in order to build a product or service which replicates, competes with or is"
- To know. Requires arbitration or waives class actions. "Any disputes will be settled by arbitration in Helsinki, Finland."
- Gives the date it was last updated. Last updated 2025-09-30.
- Names the governing law or courts. The law of Finland.
- Not found in the text. Says how changes to the terms are announced.
- Not found in the text. Refers to a service level or uptime commitment.
- Also in the text (2026-10-08). Total liability of either party is capped at 20 per cent of the service fees paid or payable by the customer. "or contemplated performance of this Agreement in respect of any and all causes of action shall in no event exceed 20% of the value of the Service Fees"
- Also in the text (2026-10-08). The customer must ensure that each user of the service is an individual natural person aged at least 18, and clause 7.1.3 limits each user account to one individual. "7.1.4. the Customer shall ensure that each Customer User is an individual natural person who is at least 18 years of age; and"
- Also in the text (2026-10-08). If the customer does not pay on time and gives no further instructions, uploaded customer data is automatically deleted within 96 hours after several notices from the supplier. "uploaded to the Service shall be automatically deleted within ninety-six (96) hours following the issuance of several notices by the Supplier."

**Privacy policy** (https://verda.com/privacy-policy), read 2026-10-08, gives no date, states 6 of the 8 things a reader expects.

- Not found in the text. Gives the date it was last updated.
- Says how long data is kept. Names a period of 30 days.
- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.
- Gives a privacy contact. Names a data protection officer.
- Not found in the text. Says where data is transferred or stored.
- Also in the text (2026-10-08). The policy says data customers upload or process on the platform is not used for the vendor's own purposes and is processed only under the customer's instructions. "personal or sensitive information of third parties. We do not use this data for our own purposes. We only process it under your instructions so you"

## Live (updated 2026-10-09 10:14 UTC)

- Right now: up, HTTP 401, 105 ms, checked 2026-10-09 10:14 UTC (get on `https://api.verda.com/v1`, asks for auth)
- Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 86 ms · p95 177 ms
- Vendor status page: unknown, no machine-readable status found
- Always current: https://www.anchorterminal.com/api/v1/live/verda.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Prices

| Item | Price | Unit | Note |
| --- | --- | --- | --- |
| H100 SXM5 80 GB, on-demand | $3.89 | per GPU-hour | Spot $1.95. Billed in prepaid 10-minute increments |
| H200 SXM5 141 GB, on-demand | $5.07 | per GPU-hour | Spot $2.54 |
| B200 SXM6 180 GB, on-demand | $7.34 | per GPU-hour | Spot $3.67 |
| B300 SXM6 268 GB, on-demand | $9.24 | per GPU-hour | Spot $4.62 |
| A100 SXM4 80 GB, on-demand | $1.87 | per GPU-hour | Spot $0.935 |
| L40S 48 GB, on-demand | $1.61 | per GPU-hour | Spot $0.803 |
| H100 SXM5 80 GB, serverless container | $4.28 | per GPU-hour | Spot $2.14. Billed per minute of replica use |
| NVMe block volume or shared filesystem | $0.20 | per GB per month | Per GiB |

Across all listings: https://www.anchorterminal.com/prices/index.md

## Strengths

- OpenAPI 3.1 document with 112 operations and 156 schemas, plus `llms.txt` files on three hosts and the whole docs corpus as Markdown
- Rate limits of 500 requests a minute per project and 60 per endpoint, with `RateLimit` headers and `Retry-After` on 429
- API changelog with 11 dated entries between 11 September and 7 October 2026
- 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
- On 30 December 2025 a storage migration overwrote part of a shared filesystem in FIN-03, and Verda reported irreversible data loss for some customers
- No SLA was found, and the terms give no warranty of uninterrupted availability

## Before you call it (notes for agents)

1. 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.
2. Send `location_code` on every create call. Requests without it have returned 400 since March 2026.
3. Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.
4. List instances before retrying a failed launch, because create has no idempotency key.
5. Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set.

## Connect

Install:

```bash
brew install verda-cloud/tap/verda-cli
```

First request:

```bash
curl -X POST https://api.verda.com/v1/oauth2/token -H "Content-Type: application/json" -d '{"grant_type":"client_credentials","client_id":"<YOUR_CLIENT_ID>","client_secret":"<YOUR_CLIENT_SECRET>"}'
```

MCP client configuration:

```json
{
  "mcpServers": {
    "verda": {
      "args": [
        "mcp",
        "serve"
      ],
      "command": "verda"
    }
  }
}
```

Through letme (picks today, calling later): https://letme.dev/verda. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Modal | B | 63.6 | 346 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/modal.md |
| Beam | C | 55.5 | 588 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/beam.md |
| Cerebrium | C | 55.3 | 593 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/cerebrium.md |
| Runpod | D | 53.5 | 629 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/runpod.md |
| Nebius AI Cloud | B | 67.2 | 240 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/nebius-ai-cloud.md |
| Baseten | B | 66.5 | 264 | compute.gpu, compute.endpoints, compute.serverless, compute.containers | no | https://www.anchorterminal.com/tools/baseten.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- verda.com/llms.txt states that Verda was previously known as DataCrunch and that older SDKs, URLs and examples may still use that name (source: <https://verda.com/llms.txt>)
- The CLI's MCP server runs over stdio with `verda mcp serve`, has 18 tools for discovery, VMs, cost, SSH keys and volumes, and is marked beta (source: <https://docs.verda.com/cli/mcp/index.md>)
- `create_vm`, `create_volume` and destructive `vm_action` calls fail with `CONFIRMATION_REQUIRED` unless `confirm: true` is passed (source: <https://github.com/verda-cloud/verda-cli>)
- Rate limits are 500 requests a minute per project and 60 per endpoint, reported in `RateLimit` headers, with `Retry-After` on 429 (source: <https://api.verda.com/v1/openapi.json>)
- Pay As You Go is billed in prepaid 10-minute increments. When the balance reaches zero, instances are discontinued and volumes deleted, restorable for 96 hours (source: <https://docs.verda.com/welcome-to-verda/pricing-and-billing/index.md>)
- The audit log covers 90 days in CloudEvents 1.0 format and is limited to project owners and admins. It is marked beta (source: <https://docs.verda.com/resources/audit-logs/index.md>)
- The status feed lists four incidents between 13 August and 25 September 2026, and a 30 December 2025 storage migration that caused irreversible data loss for some customers (source: <https://status.verda.com/feed.rss>)
- The home page states SOC 2 Type II and ISO 27001, 27017, 27018 and 27701 certification (source: <https://verda.com/>)

## Compare

- [Baseten vs Verda](https://www.anchorterminal.com/compare/baseten-vs-verda.md): B 66.5 vs B 62.3
- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md): C 55.5 vs B 62.3
- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md): C 55.3 vs B 62.3
- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md): C 61.5 vs B 62.3
- [Hugging Face Inference Endpoints vs Verda](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.md): B 64.5 vs B 62.3
- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md): D 48 vs B 62.3
- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md): D 46.5 vs B 62.3
- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md): D 50 vs B 62.3
- [Modal vs Verda](https://www.anchorterminal.com/compare/modal-vs-verda.md): B 63.6 vs B 62.3
- [Nebius AI Cloud vs Verda](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.md): B 67.2 vs B 62.3
- [Northflank vs Verda](https://www.anchorterminal.com/compare/northflank-vs-verda.md): C 61.3 vs B 62.3
- [Replicate Deployments vs Verda](https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.md): B 63.6 vs B 62.3
- [Runpod vs Verda](https://www.anchorterminal.com/compare/runpod-vs-verda.md): D 53.5 vs B 62.3
- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.md): C 56.1 vs B 62.3
- [Vast.ai vs Verda](https://www.anchorterminal.com/compare/vast-ai-vs-verda.md): B 62.6 vs B 62.3

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on verda.com or one of its subdomains, or the README of github.com/verda-cloud/verda-cli. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "verda", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/verda"><img src="https://www.anchorterminal.com/badges/verda.svg" alt="Verda on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Verda on Anchor Terminal](https://www.anchorterminal.com/badges/verda.svg)](https://www.anchorterminal.com/tools/verda)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/verda">Verda on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Verda is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/verda-dark.png
- Light: https://www.anchorterminal.com/assets/share/verda-light.png